Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Write Milestone Brief · open-gsd | DecimalAI

productivityby open-gsd

Write Milestone Brief

open-gsd/write-milestone-brief

Source open-gsd/gsd-pi ↗License MIT

Synthesize the current conversation into a milestone brief (PRD). Writes to `M###-CONTEXT.md` by default, or files a GitHub issue only with explicit user confirmation.

SkillScore23Maintained

Automatic

Product Management pack

Last verified 9/29/2026

What it changes

Passed 2 of 10 test cases with the skill, and 2 of 10 without it.

Without skill18%

With skill23%

Checks it passed that the model alone missed

Must read .gsd/STATE.md to identify the currently active milestone ID.
Must offer the option to proceed to planning using /gsd dispatch plan.
Must offer options to file a GitHub issue or iterate on the brief using grill-me.

and 4 more in the full report

4 fixed1 passed either way14 still failing3 broke

Pass-rate lift: +5 pp
Tokens: +79%
Agent turns: 0%
Response time: -55%

Model gemini-3.6-flashMeasured 9/29/2026v1 · latest is v25 of 22 cases passed with skill · 10 comparable

Tokens, turns and time describe resource use, not a dollar price.

This benchmark measured an earlier version of the skill.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/open-gsd-write-milestone-brief/SKILL.md https://app.decimal.ai/s/open-gsd-write-milestone-brief/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add open-gsd-write-milestone-brief, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/open-gsd-write-milestone-brief/ and pins it in .decimal/skills.lock

decimalai skills add open-gsd-write-milestone-brief

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/open-gsd-write-milestone-brief/SKILL.md https://app.decimal.ai/s/open-gsd-write-milestone-brief/SKILL.md

Raw file: /s/open-gsd-write-milestone-brief/SKILL.md ↗ · machine-readable summary at /s/open-gsd-write-milestone-brief.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 4

Prompt

We are capturing context for the authentication refactor milestone. The user specified that unit tests, integration tests, and live OAuth flow end-to-end scenarios must pass. Which section in M010-CONTEXT.md captures test coverage expectations and specific required test types?

What was checked, without and with the skill
Checked	Without skill	With skill
Must record test types, coverage expectations, and required test scenarios in the Testing Requirements section.	Missed	Passed
Must distinguish end-to-end acceptance scenarios from unit and integration testing requirements.	Missed	Passed

case-18 · gemini-3.6-flash · 9/29/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md131 linessingle file

Typical invocation points:

User says "capture this" or "write it up" after a planning discussion
End of a discuss phase before moving to plan
User wants to hand the work off to another agent or a human teammate

<core_principle> SYNTHESIZE, DO NOT RE-INTERVIEW. Use what is already in this conversation. If a decision is genuinely missing, note it in Open Questions — do not relitigate.

REAL OUTCOMES, NOT TASKS. M###-CONTEXT.md describes what the user can do when the milestone ships, what scenarios must pass for "done," and what architectural decisions were made. It does NOT list tasks or implementation steps — those belong in M###-ROADMAP.md and S##-PLAN.md.

NO FILE PATHS OR LINE NUMBERS IN THE BRIEF. Those go stale. Describe modules, interfaces, and behaviors. The roadmap and plans can cite code locations; the brief should outlive refactors. </core_principle>

Step 1: Locate the target

Find the active milestone:

Call gsd_project_snapshot — it names the active milestone.
If no milestone is active, ask the user whether this is a new milestone (create directory + files) or appending to an existing one.
For a new milestone, use gsd_milestone_new or the /gsd new-milestone flow — do not create directories by hand.

Step 2: Read the template

Read src/resources/extensions/gsd/templates/context.md (the full path is shown in the templatesDir system-prompt field). Match its structure exactly — parsers and downstream prompts depend on the headings.

Step 3: Sketch the modules

Before filling the template, sketch the major modules the milestone will build or modify. Actively look for opportunities to extract deep modules — ones that encapsulate a lot of functionality in a simple, testable interface that rarely changes. A deep module is more testable, more AI-navigable, and survives refactors.

Track record

Benchmark

2 / 10

test cases passed, vs 2 / 10 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 10/8/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

open-gsd / gsd-pi

src/resources/skills/write-milestone-brief/SKILL.md

View on GitHub ↗

License MITImported 10/8/2026Version v2

Other skills for the same job

Published skills whose descriptions closely match this one, with their headline benchmark lift.

gsd-build/write-milestone-briefSynthesize the current conversation into a milestone brief (PRD). Writes to `M###-CONTEXT.md` by default, or files a GitHub issue only with explicit user confirmation. Use when asked to "turn this into a PRD", "draft a milestone brief", "capture this context", "write it up", or when enough has been discussed to commit the plan to paper. Does not interview — it synthesizes what is already known.Near-identical description

More skills from the same source and nearby in the registry, with their headline benchmark lift.