Menu
Generate a sprint status report for the current phase. Default is --table.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create or harden CLIs intended primarily for AI or system consumption and secondarily for humans. Use when designing or implementing a JSON-first CLI with an MCP-ready contract seam, where every command supports machine output, errors are typed and actionable, mutating commands are auditable via corresponding read commands, and external integrations need simulator-backed testing. Do not use for human-first shell utilities, one-off scripts, or text-only CLIs.
Design stateful simulators for AI-facing CLIs that integrate with devices, networks, services, or databases. Use when a CLI needs realistic simulator-backed testing, configurable fault injection, persistent state, and a swappable adapter boundary so the same business logic runs against live and simulated backends. Do not use for shallow mocks, stateless test doubles, or CLIs with no external integration.
Critically review an existing CLI, MCP wrapper, or CLI plan for AI-first contract quality. Use when evaluating whether a CLI is JSON-first, has an MCP-ready contract seam without JSON reshaping, auditably models state changes, uses stateful simulator-backed testing for external integrations, and returns typed actionable errors. Do not use for general style review or human-first shell UX review.
Orchestrate multi-sprint phases where crap (Codex) is the sole developer, with pipelined QA via quality-mgr teammate. Team-lead chooses the review type; quality-mgr chooses the reviewers.
Reusable QA orchestration skill for GitHub PRs. Use for multi-pass QA, CI monitoring with `atm gh monitor`, one-shot PR reporting with `atm gh pr report`, and template-driven findings/final quality reports.
Review Rust architecture plans, crate boundaries, and code for structural design-pattern compliance. Use when the task involves typestate, sealed traits, error contracts, wrapper/newtype design, object safety, interior mutability, or other type-system-driven Rust correctness patterns that go beyond general style guidance.
| name | sprint-report |
| version | 1.0.0 |
| description | Generate a sprint status report for the current phase. Default is --table. |
Build fenced JSON and pipe to the Jinja2 template. mode controls table vs detailed.
/sprint-report [--table | --detailed]
Default: --table
Use standard GitHub CLI data for this repo:
gh pr list --state all --limit 20gh pr checks <PR_NUMBER> when CI detail is neededUse that data to populate sprint_rows and integration_row. Only drill into individual
gh run view calls if you need failure details for a specific job.
The template path is relative โ must run from the main repo root (not a worktree).
cd "${CLAUDE_PROJECT_DIR:-$(git worktree list | head -1 | awk '{print $1}')}"
echo '<json>' > /tmp/sprint-report.json
sc-compose render --root .claude/skills/sprint-report --file report.md.j2 --var-file /tmp/sprint-report.json
{
"mode": "table",
"sprint_rows": "| P1.1 | โ
| โ
| ๐ | #10 |\n| P1.2 | โ
| โ
| ๐ | #11 |",
"integration_row": "| **integrate/phase-1** | | โ | ๐ | โ |"
}
{
"mode": "detailed",
"sprint_rows": "Sprint: P1.1 Description\nPR: #10\nQA: PASS โ\nCI: Merged to integrate/phase-1 โ\nโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ\nSprint: P1.2 Description\nPR: #11\nQA: PASS โ (iter 2)\nCI: Running (1 pending)",
"integration_row": "Integration: integrate/phase-1 โ develop\nCI: Running โ pending P1.3"
}
| State | DEV | QA | CI |
|---|---|---|---|
| Assigned | ๐ฅ | ๐ฅ | |
| In progress | ๐ | ๐ | ๐ |
| Done/Pass | โ | โ | โ |
| Findings | ๐ฉ | ๐ฉ | |
| Fixing | ๐จ | ||
| Blocked | ๐ง | ||
| Fail | โ | ||
| Merged | ๐ | ||
| Ready to merge | ๐ |