agentleFS
link7373link7373/agentic-pmo/.claude/skills/build-roadmap/SKILL.md

build-roadmap

Skill1 starsChanged 3 months agoMITView on GitHub

Create or update the product roadmap — outcome/theme-based, defaulting to Now/Next/Later — tied to strategy and goals, with audience-appropriate views. Use to set or communicate direction over time. Dispatches the product-manager with the product-strategist.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start from templates/roadmap.md.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/build-roadmap — Where the product is going

When to use

Creating, updating, or communicating the roadmap; quarterly/periodic planning.

Dispatches

product-manager (lead) + product-strategist (strategy alignment). Consult program-manager for cross-team sequencing; comms-lead for audience views.

Inputs

knowledge/product-context.md (strategy, OKRs), knowledge/backlog.md, discovery findings, prior roadmap.

Steps

  1. Anchor on strategy and current goals/OKRs — every item must ladder up to one.
  2. Gather candidate initiatives; prioritize them (see /prioritize).
  3. Group into outcome-oriented themes; sequence by value, dependency, capacity.
  4. Assign horizon/confidence — default Now / Next / Later (use dates only where truly required).
  5. Annotate the outcome each theme targets and key assumptions; mark committed vs. exploratory.
  6. State the non-goals — what you are deliberately not doing this horizon, and when to revisit. This is the most useful section for anyone deciding what to ask for.
  7. Produce tailored views for the key audiences if requested.

Methods

knowledge/methods/roadmapping.md, knowledge/methods/prioritization-frameworks.md, knowledge/methods/product-strategy.md.

Output

Start from templates/roadmap.md. Update knowledge/roadmap.md (source of truth), including the non-goals and changes-since-last-version sections; log significant roadmap changes and reasons to knowledge/decision-log.md. Follow standards/document-standards.md.


Created by Colin Beck<br> LinkedIn: https://www.linkedin.com/in/beckcolin/<br> GitHub: https://github.com/link7373

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.