From cm
Runs opinionated sprint pipeline (brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro) via CLI, tracks state/artifacts, maps to skills. Use for structured dev cycles.
npx claudepluginhub tody-agent/codymaster --plugin cmThis skill uses the workspace's default tool permissions.
`brainstorm → plan → design → tdd → build → review → qa → security → ship → monitor → retro`
Orchestrates sprint workflow chaining plan→build→test→review→ship→verify phases using Ultraship skills for full feature lifecycle. Use when starting new features or iterations.
Explains 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.
Orchestrates full development sprint cycles from planning to PR creation using git workflows, sub-skills, and automated orchestration. Use for advancing projects via structured cycles.
Share bugs, ideas, or general feedback.
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.