roadmap-refinelisted

Enforces the detail-level invariant on `project/roadmap.md` per `spec/project/roadmap/` §Detail-level convention. Invoke when the user asks to "refine the roadmap", "check roadmap detail levels", "is the roadmap ready for the next sprint", "promote roadmap items to fine", or equivalent German-language requests. Resolves the current and next sprint by reading `project/sprints/`, walks every roadmap item, emits a structured violation record on stderr for every item with `target_sprint` equal to the current or next sprint and `detail` other than `fine`, exits non-zero when any violation is open, and walks per-item fix proposals one at a time. Don't use to add items, retarget sprints, or flip MVP flags (use `roadmap-plan`); don't use to scaffold the roadmap from scratch (use `roadmap-init`). Supports resume on re-invocation per `spec/claude/resumable-work/`.
nolte/claude-shared · ★ 0 · AI & Automation · score 76

Install: claude install-skill nolte/claude-shared

# Roadmap Refine Enforces the detail-level invariant declared in `spec/project/roadmap/<canonical_language>.md` §Detail-level convention and refinement rule: at any point in time, every roadmap item with `target_sprint` set to the **current sprint** or the **next sprint** carries `detail: fine`. Coarse and backlog items two or more sprints out are fine; promotion to `fine` is the trigger for this skill to pull each affected item into shape. ## German trigger phrases This skill also triggers on equivalent German-language requests, including: - "Roadmap verfeinern" - "Roadmap-Detailstufen prüfen" ## Why this is a skill, not an agent - **Mid-flow interactivity is the contract** — fix proposals (promote `coarse → fine`, write the missing body paragraph, expand the feature checklist) are negotiated with the user one item at a time; an agent's structured-report shape would lose that per-item iteration. - **Output flows back into the main conversation** — the violation list and the per-item drafts must be visible in the working context so the user can confirm each fix before it hits disk. - **Orchestrator role** — fixes that exceed simple promotion (re-targeting a sprint, adding a feature checklist) are dispatched into `roadmap-plan`; the orchestrator is always a skill per `skill-vs-agent`. - Counter-dimension considered: the violation-detection step alone (read `project/sprints/`, walk roadmap items, emit records) would suit an agent's isolated context, but the load-bearing d