plan-create-implementation

Implementation plans break down requirements into atomic subtasks organized into logical phases like Setup, Implementation, and Testing. This approach provides clarity by assigning service types and defining verification steps for each actionable task.

To break down requirements into verifiable subtasks, assign service isolation types like frontend, backend, database, and infra. Each atomic task receives defined verification steps to ensure traceability throughout the development workflow.

Yes, automated task generation supports agile workflows after a product spec is approved. The Skill orchestrates the workflow by automatically creating structured roadmaps with actionable subtasks like creating API endpoints and defining verification methods.

Supported verification types for implementation plans include command, API, browser, e2e, and manual checks. These methods ensure that every generated subtask can be validated according to its specific complexity and development best practices.

The best way to organize development tasks into logical phases is to group atomic subtasks into structured categories like Setup, Implementation, and Testing. This automated roadmapping ensures clarity and efficient execution from spec to actionable tasks.