dev-guided

Iterative development with human checkpoints uses structured documentation to guide each phase. This Skill creates problem_statement.md, decisions.md, runbook.md, and progress.md files that organize requirements, capture approved decisions, define implementation steps, and track completion across sessions—enabling clear handoff points where humans review and approve before proceeding.

Emerging requirements benefit from guided development that documents assumptions upfront, then refines them incrementally. This Skill structures the problem space with an initial problem statement and decisions log, then executes planned sessions (plan-N.md) that surface new requirements, record them with rationale, and update your runbook—keeping work coherent across iterations.

Yes. Multi-session projects need persistent context and clear checkpoints. This Skill maintains problem_statement.md, decisions.md, runbook.md, and progress.md as living documents that preserve your work, decisions, and next steps between sessions—so you resume with full context and avoid duplicating effort or losing decisions.

Decision logging with rationale prevents ambiguity and rework. This Skill records each decision in decisions.md with the reasoning behind it, making it explicit why a choice was made and under what constraints—so future sessions and team members understand the context without repeating debates.

Structured runbooks embed human feedback loops. This Skill generates runbook.md with defined checkpoints where implementation pauses for human input, then orchestrates plan-N.md sessions that prompt you at each step, capture feedback, and log progress—turning ad-hoc reviews into a predictable workflow.

No. This Skill automates template creation. Invoke it with no materials to generate problem_statement.md, decisions.md, runbook.md, and progress.md in docs/development/NNN-<name>/—you fill in content through guided prompts, not by designing the structure yourself.