sdd-tasks

To generate a task checklist from a design document, the skill parses your design specifications and breaks them down into granular, verifiable implementation steps organized into logical phases like Foundation, Core Implementation, Testing, and Cleanup.

The best way to structure implementation steps is by organizing them into clear action items with a defined dependency order. This approach deconstructs a proposed change into sequential phases such as Foundation, Core Implementation, Testing, and Cleanup.

Yes, you can persist generated task checklists. The skill supports artifact persistence through Engram or standard filesystem conventions, allowing you to save the output as a tasks.md file for future reference.

Yes, the task generation tool works without external dependencies. It independently parses your design specifications to create a structured implementation plan, requiring no additional packages or modules to function.

To create a task breakdown for a user authentication change, provide the design specifications to the skill. It will generate a tasks.md file outlining exactly which files need modification, what code to write, and how to test each component.

When automating task generation from design specs, the limitation is that the output quality depends entirely on the provided design specifications. The skill structures existing design details into phases but does not generate the underlying architectural design itself.