Verwendung
- Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
- Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
- Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/frostney/known-good-route --skill roadmap-reviewVor dem Start
- Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
- Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.
Roadmap review
Produce a source-verified roadmap and throughput-anchored release plan. Analysis is the deliverable; issue, pull-request, milestone, and release changes are optional and confirmation-gated.
Evidence contract
- Pull current issues, releases, milestones, merged PR history, and project
direction documents this run. Record missing sources and lower confidence rather than filling gaps from memory.
- Measure 90-day merged-PR throughput and issue-created-to-PR-merged lead time.
Use PR-opened-to-merged only as a flagged fallback. Exclude closed triage with no implementation.
- When a domain metric exists, measure its slope from spaced historical CI
artifacts. Allocation by label or area describes past effort, not capacity.
- Before proposing or characterizing work, classify it against current code,
tests, or primary specifications as Done, Partial, or Absent with evidence. Propose only Partial or Absent work.
Delegate independent, sizeable evidence areas to context-isolated subagents by default when the host supports it; work directly on small or coupled areas. Synthesize before planning.
Workflow
- Ground the review in the evidence contract and reconcile issue, pull-request,
release, and milestone counts from the Git hosting service.
- Assess release cadence, merged-but-unreleased work, milestone-versus-commit
drift, vision, scope, and non-goals.
- Classify every candidate under the evidence contract and drop work already
delivered.
- Apply measured rates to the counted remaining backlog, with basis and
confidence. Never pad the timeline. When evidence cannot support calendar dates, report ranges and dependencies without a dated Gantt or placeholder dates.
- Plan themed releases across independent tracks, marking dependencies and the
longest pole. Surface genuine human decisions with a recommendation.
- Stop for those decisions and present:
- current state, drift, and release-cadence recommendation;
- measured velocity and confidence;
- versioned, sized tracks;
- throughput-anchored timeline with a Mermaid Gantt when available;
- open decisions.
- Offer a date-stamped
ROADMAP-YYMMDD.md; do not write it without the user's
request.
- Create or modify milestones, issues, due dates, or labels only after explicit
confirmation of the finalized plan. Create each issue through /create-issue and report exactly what changed.
- After the confirmed milestone and its tracked scope exist, offer
/milestone-rush <milestone> as an explicit next action. Never start the rush automatically; selecting it grants that skill's scoped implementation and merge authority.
Keep the report decision-relevant and snapshot-dated. Re-pull before acting on an old report.
