mirror of
https://github.com/alirezarezvani/claude-skills.git
synced 2026-10-07 02:58:13 +00:00
generate-docs.py learns the agent-launcher domain (5 hardcoded maps extended); regenerated docs tree: 343 skill pages / 96 agent pages / 122 command pages (561 total). mkdocs.yml nav gains the Agent Launcher skill section (7 pages), 4 cs-agent-* agent entries, and 8 /cs:* command entries; all nav targets verified to exist. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012FwXG6TqCXKZQvF4iD69cv
53 lines
2.1 KiB
Markdown
53 lines
2.1 KiB
Markdown
---
|
|
title: "/cs-product — Slash Command for AI Coding Agents"
|
|
description: "Top-level product-team router. Classifies a product inquiry across 16 lanes (prioritization, OKRs, UX, design system, competitive, analytics. Slash command for Claude Code, Codex CLI, Gemini CLI."
|
|
---
|
|
|
|
# /cs-product
|
|
|
|
<div class="page-meta" markdown>
|
|
<span class="meta-badge">:material-console: Slash Command</span>
|
|
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/2-claude-skills/tree/main/product-team/commands/cs-product.md">Source</a></span>
|
|
</div>
|
|
|
|
|
|
Route this inquiry through the `product-skills` orchestrator:
|
|
|
|
**$ARGUMENTS**
|
|
|
|
## Routing (deterministic — run the script, don't eyeball)
|
|
|
|
```bash
|
|
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`, or `features.csv`
|
|
resolves 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-loop` instead.
|
|
|
|
## Distinct from
|
|
|
|
- `project-management` — how to deliver. This domain is what to build.
|
|
- `marketing/landing` — from-scratch marketing pages; `landing-page-generator` here
|
|
scaffolds product Next.js/TSX pages.
|