write-milestone-brief

Synthesize planning discussions into a milestone brief with a fixed template.

Updated May 25, 2026
One-click install
npx skills add https://github.com/cmetech/otto-cli --skill write-milestone-brief-cmetech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-milestone-brief
Source: https://github.com/cmetech/otto-cli/tree/main/src/resources/skills/write-milestone-brief
Command: npx skills add https://github.com/cmetech/otto-cli --skill write-milestone-brief-cmetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesizes the current planning discussion and repository reality into a durable milestone brief that future agents can act on with zero additional context.

Core Features & Use Cases

  • Generates a populated M###-CONTEXT.md from the existing conversation using a fixed template.
  • Optionally files a GitHub issue when the user explicitly confirms.
  • Does not re-interview; it relies on the known context to stabilize the plan and hand off to execution.

Quick Start

Ask OTTO to generate the milestone brief once planning has stabilized.

Frequently Asked Questions about write-milestone-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a durable milestone brief from a planning discussion?

To create a durable milestone brief, synthesize the current planning discussion and repository reality into a populated M###-CONTEXT.md file using a fixed template. This captures project description, rationale, outcomes, acceptance criteria, risks, and open questions.

What is a milestone brief and why do I need one for project planning?

A milestone brief is a durable document that stabilizes a planning discussion so future agents can act on it with zero additional context. You need it to capture rationale, outcomes, acceptance criteria, risks, and open questions before handing off to execution.

Can I automatically file a GitHub issue from a milestone brief?

Yes, you can optionally file a GitHub issue from the milestone brief, but it requires explicit user confirmation. The Skill generates the M###-CONTEXT.md file first and only files the issue when explicitly confirmed.

Does the milestone brief generation re-interview or ask for additional context?

No, the milestone brief generation does not re-interview or ask for additional context. It relies entirely on the known context from the existing conversation to stabilize the plan and hand off to execution.

When should I generate a milestone brief during the product planning workflow?

You should generate a milestone brief once your planning discussion has stabilized. This ensures the synthesize process captures the finalized project description, rationale, outcomes, acceptance criteria, risks, and open questions accurately.