agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/implementation-roadmap/SKILL.md

implementation-roadmap

Skill1 starsChanged 22 days agoMITView on GitHub

Converts an approved direction into a phased implementation roadmap with workstreams, dependencies, gates and ownership.

2 other projects use a version of this.

Adopted by

Most recently taken up by

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
  1. Distinctive:

    Use after direction is agreed but before detailed delivery planning begins.

    line 9
  2. Distinctive:

    Test the roadmap through dependency mapping and a delivery pre-mortem.

    line 23
  3. Distinctive:

    Every activity links to an intended outcome.

    line 29

≈ “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.

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

Implementation Roadmap

When to use it

Use after direction is agreed but before detailed delivery planning begins.

What Claude needs

  • client-context.md and approved recommendation
  • Target outcomes, scope and constraints
  • Capabilities, dependencies and available owners
  • Known milestones, risks and decision gates

Method

  1. Translate target outcomes into measurable end-state capabilities.
  2. Define workstreams using a MECE breakdown of required change.
  3. Sequence foundations, pilots, rollout and stabilisation by dependency.
  4. Mark milestones, decision gates and critical cross-workstream handoffs.
  5. Assign accountable owners and indicative resource needs.
  6. Test the roadmap through dependency mapping and a delivery pre-mortem.

Output format

Provide Roadmap Principles, Phases, Workstream Table, Milestone Timeline, Dependencies, Decision Gates, Ownership and First Actions.

Quality checks

  • Every activity links to an intended outcome.
  • Dependencies and gates are sequenced logically.
  • Near-term actions are more detailed than later phases.

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.