write-milestone-brief

To turn planning discussions into a milestone brief, synthesize the current conversation and repository reality into a PRD-like M###-CONTEXT.md file. This artifact records decisions, open questions, constraints, and acceptance criteria for durable future handoffs.

Documenting project context involves creating an M###-CONTEXT.md milestone brief that captures decisions, open questions, and constraints. This provides a stable PRD-like reference that can be archived or handed off for future work.

You can create a GitHub issue from a milestone brief, but the skill only generates the issue on explicit user confirmation. It first synthesizes repository context and discussions into the M###-CONTEXT.md file, then optionally creates the issue.

Yes, the milestone brief template enforces a specific structure that records acceptance criteria, constraints, open questions, and expected outcomes. This ensures the M###-CONTEXT.md artifact remains durable and consistent for future handoffs.

To generate a milestone brief, the skill synthesizes your current conversation and repository state into an M###-CONTEXT.md file. It automatically extracts and structures planning details into a PRD-like document ready for review and handoff.

You need a milestone brief when you require a durable, PRD-like artifact for handoff or archiving. It synthesizes ongoing planning discussions and repository reality into a stable reference capturing decisions, constraints, and acceptance criteria for future work.