milestone-planning SKILL.md skillA
milestone-planning from harshadmadaye/opm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add harshadmadaye/opm/milestone-planning@git:20261005.53e43d7Pins git:20261005.53e43d7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- harshadmadaye/opm
- Path
skills/milestone-planning/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261005.53e43d7, committed Oct 5, 2026
- First version recorded
- Sep 12, 2026
- Size
- 11,641 bytes
- Repository stars
- 5
- License
- MIT
Structures multi-week work as a milestone with a roadmap, a short always-read STATE digest, phased executable PLAN files with YAML frontmatter and XML task bodies, wave-based parallel execution by fresh subagents, deviation rules, checkpoints, and SUMMARY files for cheap history. Use when scope exceeds about one week or eight tasks, or when starting a greenfield project.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Milestone Planning
`opm:writing-plans` handles a task list that fits in one head and one context window.
When the work is bigger than that (weeks, many tasks, several subsystems, or a blank repo) you
need a structure that survives context resets, lets independent work run in parallel, and leaves
a history the next session can read in under a minute. That structure is a milestone.
## When to use
- Estimated scope is more than about one week or more than about eight tasks.
- Greenfield project, or a feature that touches three or more subsystems.
- The work will span several sessions and someone (or some agent) will need to pick it up cold.
If in doubt, start with `opm:writing-plans`; promote to a milestone when the task list stops fitting.
## Artefacts
```
docs/milestones/<milestone>/
ROADMAP.md phases, goals, status (written once, updated at phase boundaries)
STATE.md under 100 lines, ALWAYS read first, updated after every plan
ISSUES.md deferred enhancements and known gaps, numbered ISS-NNN
phases/
01-<name>/
PLAN-01-01.md executable plan (frontmatter + XML body)
PLAN-01-02.md
…Read the whole file at its exact version.
How to install
mdr add harshadmadaye/opm/milestone-planning@sha256:20a3f7726794270bThe line at the top of this page pins the label git:20261005.53e43d7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_e3oj6azrukeldvpd)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 12, 2026 and Oct 5, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.53e43d7 latest | 2026-10-05 | 53e43d7 | 11,641 B | A | view · diff |
| git:20261005.a666976 | 2026-10-05 | a666976 | 11,598 B | A | view · diff |
| git:20260928.38649c8 | 2026-09-28 | 38649c8 | 11,573 B | A | view · diff |
| git:20260922.ac530a2 | 2026-09-22 | ac530a2 | 11,569 B | A | view · diff |
| git:20260912.a10a790 | 2026-09-12 | a10a790 | 11,492 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11641 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
harshadmadaye/opm · 5 stars · license MIT · pushed 2026-10-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e3oj6azrukeldvpd GET https://markdownregistry.com/api/v1/resolve?ref=harshadmadaye/opm/milestone-planning GET https://markdownregistry.com/api/v1/blob/20a3f7726794270b30fdac1b5bd803332ce1b2bb232ffcc1f16ad693ff26d458
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.