agentleFS
Sign inStart free
littlebearappslittlebearapps/pitchdocs/.claude/skills/roadmap/SKILL.md

roadmap

Skill8 starsChanged 8 months agoMITView on GitHub

Generates ROADMAP.md from project milestones, issues, and boards (GitHub, GitLab, or Bitbucket). Structures content with mission statement, current milestone progress, upcoming milestones, and community involvement section. Use when creating or updating a project roadmap.

48 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

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    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

  • 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

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 2

    Distinctive

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

    Use milestones to group features into releases.

    line 106
  2. Distinctive:

    If the repo uses project boards (GitHub Projects v2, GitLab Boards, or Jira), pull items from there:

    line 110
  3. Very specific:

    Timeline: Use quarters (Q1/Q2/Q3/Q4), not specific dates (they create pressure and disappointment)

    line 140

“Common” is measured: kept by at least 6 in 10 of the 41 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

Roadmap Generator

ROADMAP.md Structure

# Roadmap

> **Mission**: [One sentence describing the project's north star goal]

This roadmap reflects our current plans and priorities. It's a living document — priorities shift based on community feedback and real-world usage.

**Last updated**: [Date]

## Legend

| Status | Meaning |
|--------|---------|
| :white_check_mark: Done | Shipped and available |
| :construction: In Progress | Actively being worked on |
| :dart: Planned | Committed for this milestone |
| :thought_balloon: Exploring | Under consideration, feedback welcome |

---

## Current Milestone: v1.3 — [Milestone Title]

**Target**: Q1 2026 · **Progress**: 6/10 items complete

| Status | Feature | Issue | Notes |
|--------|---------|-------|-------|
| :white_check_mark: | Marketing-friendly README generation | #42 | Shipped in v1.2 |
| :white_check_mark: | Changelog from conventional commits | #38 | Shipped in v1.2 |
| :construction: | GitHub Projects integration | #45 | PR open |
| :construction: | User-benefit language in changelogs | #44 | In review |
| :dart: | Comparison table generator | #50 | Starting next sprint |
| :dart: | CONTRIBUTING.md generator | #48 | Blocked on #45 |

---

## Upcoming

### v1.4 — [Milestone Title] (Q2 2026)

| Status | Feature | Issue |
|--------|---------|-------|
| :dart: | Full docs suite audit command | #55 |
| :dart: | GitHub issue template generator | #56 |
| :thought_balloon: | Blog post generator from README | #60 |
| :thought_balloon: | Multi-language README support | #62 |

### v2.0 — [Milestone Title] (Q3 2026)

| Status | Feature | Issue |
|--------|---------|-------|
| :thought_balloon: | Interactive README builder | #70 |
| :thought_balloon: | Auto-update on CI | #72 |

---

## Completed Milestones

<details>
<summary>v1.2 — Documentation Foundation (January 2026)</summary>

- :white_check_mark: Basic README generation (#10)
- :white_check_mark: Badge detection and generation (#12)
- :white_check_mark: Package.json/pyproject.toml parsing (#15)
- :white_check_mark: Quick start section generator (#18)

</details>

---

## How to Get Involved

We'd love your input on what to build next:

- **Vote on features**: React with :+1: on issues you want prioritised
- **Propose ideas**: [Open a discussion](link)
- **Contribute**: See [CONTRIBUTING.md](CONTRIBUTING.md) for how to get started
- **Report issues**: [File a bug](link)

Items marked :thought_balloon: are especially open to community feedback.

Data Sources

Data source commands below default to GitHub (gh CLI / mcp__github__*). For GitLab, use glab CLI. For Bitbucket, use REST API or Jira integration. Load the platform-profiles skill for CLI and API equivalents.

Milestones (via platform CLI or MCP)

# GitHub
gh issue list --milestone "v1.3" --state all

# GitLab
glab issue list --milestone "v1.3" --all

Use milestones to group features into releases. Each milestone becomes a section. GitLab also supports Epics for higher-level grouping across milestones.

Project Boards

If the repo uses project boards (GitHub Projects v2, GitLab Boards, or Jira), pull items from there:

  1. Get board items
  2. Map columns/statuses to roadmap legend
  3. Extract issue numbers and titles

Git Tags

git tag --sort=-v:refname | head -20

Map tags to completed milestones. Include completion dates.

Open Issues with Labels

# GitHub
gh issue list --label "enhancement" --state open --limit 50
gh issue list --label "feature" --state open --limit 50

# GitLab
glab issue list --label "enhancement" --all --per-page 50
glab issue list --label "feature" --all --per-page 50

Language Rules

  • Mission statement: One sentence, present tense, aspirational but concrete
  • Feature descriptions: Benefit-focused, not implementation-focused
  • Status updates: Factual, linked to issues/PRs
  • Timeline: Use quarters (Q1/Q2/Q3/Q4), not specific dates (they create pressure and disappointment)
  • Tone: Transparent, inviting, community-oriented

Anti-Patterns

  • Don't promise specific dates — use quarters or "upcoming"
  • Don't list every issue — curate to significant features
  • Don't include internal tasks — roadmaps are for users
  • Don't forget completed milestones — they show momentum
  • Don't make it static — include "last updated" date
  • Don't forget the "get involved" section — roadmaps are conversation starters

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.

Check your setup, free