agentleFS
V-SongbirdV-Songbird/foreman/skills/roadmap/SKILL.md

roadmap

Skill35 starsChanged 52 days agoMITView on GitHub

Picks the next task from a project's ROADMAP.jsonl and crafts its handoff prompt, or adds, corrects, accepts, resumes, defers, archives or restores entries, reviews status, and checks the file's structural health. Ranks candidates deterministically by dependencies and file-touch collisions and shows why each is where it is. Use when the user asks what to work on next, wants to add or fix a roadmap entry, or wants roadmap status. Not for first-time setup (init), checking entries against the code (survey), or a prompt with no roadmap entry (craft-prompt).

51 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sequence, stakeholder-update and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GTMifySkill

    sequence

    Build a multi-channel outreach cadence (email + LinkedIn + phone) for a target persona or named prospect. Use when the user says 'build a sequence', 'outreach cadence', 'multi-touch sequence', 'multi-channel cadence', 'follow-up sequence', or needs a coordinated multi-channel play. Do NOT use for single cold emails — use cold-email instead.

    Also in 3 projects that use this

  • AnthropicSkill

    stakeholder-update

    Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.

    Also in 3 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 3 projects that use this

  • michalattSkill

    challenge

    Pressure-test plans, decisions, and directions by picking and answering the most relevant challenge questions for the current conversation

    Also in 3 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 7 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 0 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    All reads/writes to ROADMAP.jsonl at the project root go through ${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js — never read or edit the file …

    line 13
  2. Very specific:

    Pre-check: if ROADMAP.jsonl doesn't exist at the project root, offer to set the project up with init (/foreman:init in Claude Code) and …

    line 22
  3. Very specific:

    Read pick.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/pick.md) and follow it.

    line 38
  4. Very specific:

    Read add.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/add.md) and follow it.

    line 44
  5. Very specific:

    Read correct.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/correct.md) and follow it.

    line 50
  6. Very specific:

    Read status.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/status.md) and follow it.

    line 56
  7. Very specific:

    Read doctor.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/doctor.md) and follow it.

    line 62

“Common” is measured: kept by at least 6 in 10 of the 44 edited versions of this file we could read. “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

foreman:roadmap — pick, add to, correct, review, or check the project roadmap

Foreman runs in Claude Code, Codex and Antigravity. Every step applies to every host unless it names one. Read the shared runtime first: it covers plugin paths, JSON payloads, questions and authorization for every host.

All reads/writes to ROADMAP.jsonl at the project root go through ${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js — never read or edit the file directly, the script enforces id computation and parse-before/after-write mechanically — run it as roadmap.js <subcommand> --help (for example roadmap.js list --help) for that subcommand's shape. Read the Fields section of roadmap-schema.md (${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md) if you need field semantics beyond what's obvious from the names.

Pre-check: if ROADMAP.jsonl doesn't exist at the project root, offer to set the project up with init (/foreman:init in Claude Code) and stop here. When the user's request already includes setup, run init directly instead.

A request the foreman entrance routed here names its branch: go straight to that branch below. A direct /foreman:roadmap call, or a request handed over without a branch, reads menu.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/menu.md) first: it holds the menu, the phrasings that pick a branch without it, requests to archive or restore finished work, and how its questions are logged.


Branch: Pick the next task

Read pick.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/pick.md) and follow it.


Branch: Add a task

Read add.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/add.md) and follow it.


Branch: Correct a task

Read correct.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/correct.md) and follow it.


Branch: Review status

Read status.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/status.md) and follow it.


Branch: Check the roadmap

Read doctor.md (${CLAUDE_PLUGIN_ROOT}/skills/roadmap/doctor.md) and follow it.

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.