/cs-product¶
Route this inquiry through the product-skills orchestrator:
$ARGUMENTS
Routing (deterministic — run the script, don't eyeball)¶
python3 product-team/skills/product-skills/scripts/product_goal_router.py --text "$ARGUMENTS" --output json
- Exit 0 → load
skill_path/SKILL.md (covers the 4 standalone plugins too) and follow that skill's own workflow in a fork. - Exit 2 → ask ONE clarifying question naming the listed candidates, recommended answer first.
- Exit 3 → ask the user to restate the goal with the deliverable named. Never guess.
- Explore the workspace first — an
ost.json,discovery_log.json, orfeatures.csvresolves the lane silently. Never silently chain a second sub-skill.
Output (≤200-word digest)¶
- What was analyzed
- Top 3 findings, each anchored to a canon citation
- Top 3 next actions with a named owner
- Artifact path
- One grill challenge (e.g. "This roadmap cites an OST that fails the linter — which opportunity backs item 3?")
Hard rules¶
- Insights carry participant counts; singletons are anecdotes.
- Experiments carry computed sample size + MDE, never gut feel.
- Prioritization names its framework (RICE / WSJF / opportunity score) and why.
- AI features get an eval spec (golden set + rubric + guardrails) in the PRD.
- Recurring discovery work goes to
/cs:product-loopinstead.
Distinct from¶
project-management— how to deliver. This domain is what to build.marketing/landing— from-scratch marketing pages;landing-page-generatorhere scaffolds product Next.js/TSX pages.