scriptoriumadmin/claude-skills
1
0
Fork 0
mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-10-10 03:27:56 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
claude-skills/docs/commands/cs-grill-pm.md
Claude abd9c9d8de
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.8 KiB
Raw Permalink Blame History

title description
/cs-grill-pm — Slash Command for AI Coding Agents Matt Pocock-style interrogation of a delivery plan against the PM canon (Kanban Guide 2025, Vacanti, DORA 2025, EBM, Klein, GitLab async-first). One. Slash command for Claude Code, Codex CLI, Gemini CLI.

/cs-grill-pm

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

Interrogate this plan — do not execute anything yet:

$ARGUMENTS

Five rules (preserved from Matt Pocock, MIT): one question per turn · always give a recommended answer · explore the workspace before asking · walk the decision tree depth-first · track answered questions and their dependencies.

Decision tree

  • Branch 1 — Outcome: "What single observable outcome means DONE, and which command proves it? Recommended: a named artifact + a command that exits 0 against it. Canon: agent-harness verifier's law."
  • Branch 2 — Measurement: "Are you measuring flow before forecasting? Recommended: run jira_snapshot_bridge.py --to flow first — WIP, throughput, cycle time, age. Canon: Kanban Guide (May 2025) four mandatory measures."
  • Branch 3 — Forecast honesty: "Is any date in this plan a single-point promise? Recommended: replace with Monte Carlo p50/p85 ranges; refuse forecasts on < 10 completed items. Canon: Vacanti, When Will It Be Done?"
  • Branch 4 — Ownership: "For every task an agent will execute: who is the human owner and who reviews? Recommended: name both now; delivery_loop_gate.py will refuse the plan otherwise. Canon: Linear agents model; Atlassian Rovo audit discipline."
  • Branch 5 — Risk: "Have you run a pre-mortem on this plan? Recommended: 30 minutes, 'it's six months later and this failed — why?'; convert top clusters to owned risks. Canon: Klein, HBR 2007."
  • Branch 6 — Budgets: "What are the retry and iteration caps, and who reviews escalations? Recommended: 3 attempts/task, 12 iterations/goal, a named human. Canon: loop-library terminal states."

Per-turn output format:

Q[i]/[total]: [precise question]
Recommended: [answer + canon-cited rationale]

(Confirm, or override?)

Stop conditions

  • All branches resolved → invoke /cs:pm (question) or /cs:pm-loop (goal) with the locked decisions inlined.
  • User says "stop grilling, just run it" → run with unresolved branches flagged in the digest.
  • Abandoned → save the partial grill to pm-grill-{timestamp}.md.

Distinct from

  • engineering/grill-me — generic plan interrogation. This grills against the PM canon.
  • /cs:pm — routes; this refuses to route until decisions are locked.