ferrox-milestone-summary

Generate a milestone summary by reading roadmap, requirements, phase summaries, verification notes, research, and retrospective artifacts to produce a structured onboarding document. This consolidates scattered planning files into a single human-friendly project review report.

A milestone summary is used for onboarding new members and stakeholders to understand what was built, how it was built, and what remains after a milestone. It replaces scattered planning files with a single structured narrative for project review.

Yes, you can create onboarding docs from verification and retrospective files by synthesizing them alongside roadmap, requirements, and research artifacts. This produces a structured narrative covering architecture, decisions, tech debt, and getting started guidance.

Resolve milestone versioning by targeting the milestone from user input or project state, then writing the project review report to a consistent planning reports directory. This ensures version-aware reporting across completed software project phases.

Planning artifacts needed to document completed software milestones include roadmap, requirements, context, summary, verification, research, and retrospective files. These are read and resolved to generate a structured milestone summary for onboarding and project review.

No, this milestone summary approach applies to completed software projects needing a single document explaining what was built and what remains. It requires reading and resolving finalized planning, verification, and retrospective artifacts.