doc-design-from-zero

To create an executable development document, provide your feature goals, scope, references, and timing. The skill generates a structured Markdown file containing actionable task lists, milestones, and acceptance criteria to guide implementation.

A Definition of Done (DoD) establishes clear acceptance criteria across project phases. It ensures feature planning produces executable milestones and task lists that align stakeholders before implementation begins.

Defining project scope and non-goals requires inputting your feature's business context and constraints. The skill processes this input to output a structured design document separating in-scope tasks from explicit non-goals and identified risks.

Yes, you can generate a task list with milestones by supplying the project's goals and references. The skill structures these inputs into a Markdown document with selectable task items, phased milestones, and a clear Definition of Done.

Required inputs to generate design documentation include your feature idea, business context, goals, scope, references, and timing. These elements are transformed into a structured Markdown file with constraints, risks, and acceptance criteria.

This approach works for both new feature planning and refactoring tasks. Supplying the refactoring goals and scope as input generates an actionable task list with milestones and a Definition of Done to track the structural changes.