planning

To generate a technical implementation plan, this skill processes feature documentation to create a `plan.md` file. It defines specific development tasks, maps required files, estimates complexity, and structures work into logical batches for execution.

Structuring development tasks from domain to API layers is achieved through bottom-up task structuring. This approach maps domain entities first, progressively moving towards API layers to ensure all dependencies and technical steps are accounted for.

Yes, you can update an existing implementation plan dynamically. The skill modifies the current `plan.md` file to accommodate newly discovered work or scope changes, ensuring your technical documentation reflects current project requirements.

To create an actionable technical plan, you need feature requirements defined in `about.md` and `discovery.md` files. The skill uses these inputs to generate the detailed tasks, file mappings, and complexity estimates needed for development.

Yes, automated implementation planning works without external dependencies. The skill operates independently using its internal scripts and references to parse your feature documentation and output the structured `plan.md` file.

Mapping files and estimating complexity in an implementation plan ensures developers understand the exact scope and technical requirements of each task. This structured batching prevents missed steps from domain entities to frontend components during software development.