roadmap-to-release-plan
Skill0 starsChanged 5 months agoMITView on GitHub
Use when converting roadmap notes, feature lists, planning docs, or backlog themes into a release plan with milestones, scope, dependencies, rollout phases, and validation checks.
In this repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- architecture-rfc-reviewSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- customer-call-to-prdSkill
- database-migration-risk-reviewSkill
- dependency-upgrade-risk-reviewSkill
- incident-log-to-postmortemSkill
- messy-notes-to-decision-logSkill
- privacy-data-flow-mapSkill
- prompt-to-eval-rubricSkill
- repo-launch-readiness-reviewSkill
- security-review-checklistSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use when roadmap intent needs to become milestones, scope, dependencies, and release gates.
- Distinctive: line 15
Do not use when the task is long-term vision strategy with no near-term release decision.
- Distinctive: line 29
Add rollout, monitoring, and rollback considerations.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Roadmap To Release Plan
Purpose
Turn broad roadmap material into a release plan that teams can execute and inspect.
Fit
- Use when roadmap intent needs to become milestones, scope, dependencies, and release gates.
- Do not use when the task is long-term vision strategy with no near-term release decision.
Inputs
- Roadmap notes, backlog themes, feature lists, or planning docs.
- Target users, deadlines, staffing, and known dependencies if available.
- Launch constraints, risk tolerance, and validation expectations.
Workflow
- Group work into coherent release themes.
- Define included scope, deferred scope, and explicit non-goals.
- Identify dependencies, sequencing constraints, and release gates.
- Propose milestones with validation criteria.
- Add rollout, monitoring, and rollback considerations.
Output
Produce Markdown with:
- Release Goal
- Scope And Non-Goals
- Milestones
- Dependencies
- Validation Gates
- Rollout Plan
- Risks
Validation
- Each milestone has a concrete outcome.
- Dependencies are not hidden inside task descriptions.
- Non-goals prevent scope drift.
- Validation gates are testable.
- Risk notes include operational and user-facing concerns.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.