菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate marketing-quality repository documentation from codebase analysis. Scans 10 signal categories, extracts features with file-level evidence, and produces README, CHANGELOG, ROADMAP, and 15+ more docs. Zero runtime dependencies. For AI context file management, see ContextDocs.
Systematic codebase scanning for features and evidence-based feature-to-benefit translation. Extracts what a project does from its code and translates it into what users gain — generates features and benefits sections, "Why [Project]?" content, and feature audit reports. Use when writing a features table for a README, extracting features from code, auditing feature coverage, or answering "why should someone use this project?".
Orchestrates documentation updates after version bumps, feature additions, or periodic maintenance. Analyses git history since the last release, identifies which docs are affected, and delegates to existing skills (changelog, feature-benefits, docs-verify, llms-txt, user-guides) for selective refresh. Delegates AI context updates to ContextDocs if installed. Use when releasing a new version or refreshing stale docs.
Validates documentation quality and freshness — checks for broken links, stale content, llms.txt sync, image issues, heading hierarchy, and badge URLs. Runs locally or in CI. Use to catch documentation decay before it reaches users.
Generates READMEs with the Daytona/Banesullivan marketing framework — hero section, benefit-driven features, quickstart, comparison tables, and compelling CTAs. Produces docs that sell as well as they inform. Use when creating or overhauling a project README.
Generates task-oriented user guides and how-to documentation for a repository. Creates docs/guides/ with step-by-step instructions for common workflows, integrations, and advanced usage. Links guides into README.md and CONTRIBUTING.md. Use when a project needs user-facing how-to documentation beyond the README quickstart.
| name | roadmap |
| description | 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. |
| version | 1.0.0 |
# 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 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.
# 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.
If the repo uses project boards (GitHub Projects v2, GitLab Boards, or Jira), pull items from there:
git tag --sort=-v:refname | head -20
Map tags to completed milestones. Include completion dates.
# 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