app-build-planner

To convert planning artifacts into a milestone-based implementation plan, you gather upstream planning outputs and reference docs, extract features, map them to packages, sequence them into milestones, and save the final plan as docs/implementation-plan.md.

Sequencing software development features into milestones for an automated coding agent involves extracting a feature backlog, mapping features to available packages, identifying custom implementation gaps, and assigning priorities like must-have or should-have before structuring the delivery sequence.

You map project features to existing packages by analyzing extracted features against available modules, identifying gaps requiring custom implementation, and assigning priorities such as must-have, should-have, or nice-to-have to guide development.

Yes, upstream planning outputs, platform and backend decisions, and reference documents are required as starting inputs to extract the feature backlog and define source-traceability for the implementation plan.

The generated implementation plan uses a markdown document format, specifically saved at the project root as docs/implementation-plan.md, ensuring it is ready for direct handoff to guide an automated coding agent.