Stats
Actions
Tags
From cm
Runs opinionated sprint pipeline from brainstorm to retro, generating Markdown artifacts and JSON handoffs per phase. Includes CLI for init, status, complete, skip, and dry-run.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cm:cm-sprint-busThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Use to** drive the full sprint: brainstorm → ship → retro
brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro
cm sprint init --project .
cm sprint init --from plan --project . # jump in mid-pipeline
cm sprint status --project .
cm sprint complete plan -m "$(cat plan-notes.md)" --project .
cm sprint dry-run --project .
.cm/sprint/state.json.cm/sprint/artifacts/<step>.md.cm/sprint/events.jsonlEach step maps to existing CodyMaster skills (see skillMappingForStep in src/sprint-pipeline.ts). Use cm sprint status for the next recommended skill.
This complements .cm/context-bus.json (skill-chain). Prefer sprint files for linear release trains; use context bus for ad-hoc chains.
npx claudepluginhub tody-agent/codymaster --plugin cmExplains sprint workflow's convergent diffusion model, 6 phases from spec loading to finalization, agent spawning for Python/Next.js/CI-CD, testing/review, and resumption.
Chains plan → build → test → review → ship into a structured feature lifecycle. Use when starting a new feature or project iteration and want a full pipeline from idea to deployment.
Guides developers through the full development pipeline: discover, brainstorm, plan, execute, review, and ship. Invoke when starting work on a bug, feature, improvement, or task.