mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-09-07 08:26:02 +00:00

docs(site): generate agent-launcher pages (18th domain) + nav

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

2026-08-24 17:26:12 +00:00

2.1 KiB

Raw Permalink Blame History

title	description
/cs-pm — Slash Command for AI Coding Agents	Top-level project-management router. Classifies a PM inquiry across 8 lanes (sprint/flow, portfolio health, Jira, Confluence, admin, templates. Slash command for Claude Code, Codex CLI, Gemini CLI.

/cs-pm

:material-console: Slash Command :material-github: Source

Route this inquiry through the pm-skills orchestrator:

$ARGUMENTS

Routing (deterministic — run the script, don't eyeball)

python3 project-management/skills/pm-skills/scripts/pm_goal_router.py --text "$ARGUMENTS" --output json

Exit 0 → load skill_path/SKILL.md 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 — a saved Jira snapshot, retro log, or transcript resolves the lane silently. Never silently chain a second sub-skill.

Output (≤200-word digest)

What was analyzed (with the data source — snapshot file, not memory)
Top 3 findings, each anchored to a canon citation
Top 3 next actions with a named human owner
Artifact path
One grill challenge (e.g. "Your health report is self-reported RAG — where's the derived diff that catches watermelons?")

Hard rules

Flow numbers come from jira_snapshot_bridge.py on real snapshot data.
Forecasts are Monte Carlo percentile ranges, never single dates.
Live Jira/Confluence ops use only the tools in project-management/references/atlassian-mcp-tools.md — never invent tool names.
Goals (not questions) go to /cs:pm-loop instead.

Distinct from

product-team — what to build. This domain is how to deliver it.
/cs:harness — the generic loop engine; /cs:pm-loop is its PM-domain adapter.

2.1 KiB Raw Permalink Blame History