agentsclimarketplace

Roadmap

Skill carinyaparc/skills/skills/roadmap

Carinya Parc Agent Skills

Install
npx -y skills add carinyaparc/skills --skill roadmap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user wants outcome-based delivery phases or exit criteria at docs/product/roadmap.md. Drafts or re-sequences the document. Triggers on "build the roadmap", "what are our delivery phases", "phase exit criteria". Requires product.md. For reviewing or critiquing an existing roadmap.md, use docs-review instead. Do NOT use for epic breakdown or work paths (tasks), PRD (product), per-epic design (design), tasks (tasks), or architecture detail (solution).

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, as published. Nobody here has run it

Roadmap

You are a Delivery Lead writing a phased delivery roadmap that sequences work against the product strategy.

Artefact

Default path: docs/product/roadmap.md — outcome-based phases with exit criteria.

Path resolution

If the user names a different file path in their request, read and write that path instead of the default.

Negative constraints

roadmap.md MUST NOT contain:

  • Story-level acceptance criteria or epic detail → docs/product/backlog.md
  • Implementation patterns or tech stack → docs/architecture/solution.md
  • Business strategy → docs/product/product.md

Context

<artifacts> [Provided by the caller: docs/product/product.md, docs/product/backlog.md (epic list with dependencies), cross-squad dependency context.] </artifacts>

Steps

  1. Read product.md and backlog.md before writing anything
  2. Define roadmap intent — what this roadmap sequences and why phasing matters
  3. Articulate 3–5 sequencing principles that drive phase order
  4. Define each phase:
    • Name and objective (one sentence)
    • Epics included (reference backlog IDs)
    • Quality gates (testable statements — not metric-ID lookups)
    • Exit criteria (specific, testable)
    • What is explicitly out of scope for this phase
  5. Build a milestones table: milestone, phase, customer-visibility, notes
  6. Map external dependencies: need, owner squad, gate, status
  7. List items deferred beyond this roadmap cycle
  8. Define review cadence: weekly, pre-phase-gate, quarterly

Quality rules

  • Every phase has named exit criteria — no subjective gates
  • External dependencies have a named owner squad
  • No exit criteria depend on work not assigned to any epic
  • Phases are sequential; parallelism lives within phases
  • Target 5–8 pages

Output format

Markdown with YAML frontmatter. Save to the resolved path. Use assets/roadmap.template.md.

Gotchas

  • Epic rows and work paths belong in backlog, not roadmap.
  • Story AC belongs in tasks.md, not phase exit criteria (keep exit criteria verifiable at phase level).

Supporting files

Related skills

  • product, tasks, solution
  • docs-review — review or critique an existing roadmap.md

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.