Results for “capability-plan”

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Guides CAPA effectiveness assessment with verification methods, SMART criteria, and closure requirements.

Continues deep iteration on an existing planning document: detects explicit file-loading intent, provides status summaries, and supports on-demand in-depth exploration.

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Create concise, actionable plans for coding tasks. Scope work, identify dependencies, and deliver atomic, ordered steps from discovery through validation and rollout.

Turns a mature product plan into a rough implementation plan with high-level steps, maturity and verification marks, and a risks section.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.

Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a module boundary — through a discovery pass, an options document with one recommendation, a question round, and an adversarial validation round, with every element of the contract justified from one stated goal. Use when you want to design, shape, decide, or nail down an interface, contract, signature, or API change for a capability you can already describe, sized for roughly one pull request. Produces a design document and changes no code. Does not specify what a feature should do — use plan-a-feature. Does not plan delivery or sequencing — use plan-implementation. Does not assess the architecture of existing code — use architectural-analysis. Does not write the code — use tdd. Does not restructure existing code — use refactor. Runs its rounds without pausing for review; to review each round as it lands, use pairing.