docs(skills): add product-shaping routing seams (roadmapping bets boundary, neckbeard feature path)

- product-roadmapping-and-portfolio: name the bets boundary in "When Not
  to Use" — this skill sequences strategic bets across cycles; shaping a
  single bounded bet routes to product-shaping.
- product-shaping: sharpen the existing roadmapping boundary sentence to
  spell out bet vs. sequences (appetite + circuit breaker vs.
  continue/pause/kill across cycles).
- neckbeard README: route feature-sized work through product-shaping
  between discovery (product-discovery) and specification
  (spec-driven-development).

Docs-only routing seams per #394; no behavioral content changes.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
This commit is contained in:
Magnus Hedemark
2026-08-23 13:08:25 -04:00
co-authored by factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
parent af59c45bd5
commit c0412b51bd
3 changed files with 9 additions and 3 deletions
@@ -89,6 +89,11 @@ Executive narrative, team view, external/customer view — each tailored.
- **For project scheduling, Gantt charts, or milestone tracking:** this skill produces outcome roadmaps, not project plans.
- **For delivery-flow management:** route to `kanban-guru`.
- **For corporate capital allocation and M&A portfolio decisions:** route to `strategy-frameworks`.
- **For shaping a single bet** (setting its appetite, narrowing it into a bounded
problem, writing its pitch): route to `product-shaping`. This skill sequences bets
across cycles at the portfolio level; shaping packages one bet before it enters a
roadmap — "strategic bet" here means a roadmap entry with sequencing criteria, not
the shaped single-project commitment that `product-shaping` produces.
## Evidence, Assumptions, Commitments, and Options