dirien/yet-another-agent-harness / .claude/skills/roadmap
roadmap
VerifiedStrategic roadmap management for GitHub repositories. Syncs ROADMAP.md with GitHub Issues and labels, bootstraps roadmap files from scratch, runs brainstorming sessions with boundary checking, and provides quick status summaries. Use when managing project planning, syncing roadmap state, or exploring feature ideas.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.8 KB |
| references/brainstorm.md | markdown | 2.3 KB |
| references/generate.md | markdown | 2.9 KB |
| references/label-config.md | markdown | 3.9 KB |
| references/status.md | markdown | 1.5 KB |
| references/sync.md | markdown | 4.2 KB |
references/generate.md
View on GitHub<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->
# Generate mode — detailed workflow
Persona: Technical Architect + Product Manager hybrid (foundational,
systematic, boundary-setting).
## Pre-flight check
If CONTEXT.md or ROADMAP.md already exists, ask the user:
- **Regenerate**: Analyze fresh and overwrite existing files
- **Merge**: Preserve existing content and add missing elements
- **Abort**: Cancel and keep existing files
## CONTEXT.md generation
### Step 1: Deep codebase analysis
Investigate the codebase to understand:
- Project structure and architecture
- Core dependencies and their purposes
- Entry points and main workflows
- What the tool does (capabilities)
### Step 2: Infer boundaries
Determine what the project explicitly does NOT do:
- What external systems does it avoid calling directly?
- What state does it avoid persisting?
- What operations does it delegate vs implement?
- What domains are out of scope?
### Step 3: Research similar tools
Research externally to find similar tools and understand common
feature expectations, where this tool differs, and industry
terminology.
### Step 4: Draft CONTEXT.md
Use this template:
```markdown
# {Project} Context & Boundaries
## Core Architectural Identity
{One-paragraph description of what the project IS}
## Technical Boundaries ("Hard No's")
{Bulleted list of what the project does NOT do}
## Data Source of Truth
{Where does authoritative data come from?}
## Interaction Model
{Inbound and outbound interfaces}
## Verification
{How to check if a feature violates boundaries}
```
## ROADMAP.md generation
### Step 1: Fetch all GitHub issues
```bash
gh issue list --state all --limit 100 \
--json number,title,body,labels,milestone,state
gh api repos/{owner}/{repo}/milestones
```
### Step 2: Categorize issues
Group by:
- Immediate focus (current milestone or high priority)
- Near-term (next milestone)
- Future vision (backlog, research, unassigned or low priority)
- Completed (closed milestones or done issues, grouped by quarter)
For each open issue, estimate LOE using the heuristics in
`references/label-config.md` and apply `effort/*` labels.
### Step 3: Identify themes
Look for patterns: feature areas, issue types (bug, enhancement,
docs), and cross-cutting concerns.
### Step 4: Draft ROADMAP.md
Use this template:
```markdown
# {Project} Strategic Roadmap
## Vision
{Brief description and link to CONTEXT.md}
## Immediate Focus (vX.Y.Z)
- [ ] #1 Issue title [S]
- [ ] #2 Issue title [M]
## Near-Term Vision (vX.Y+1.0)
- [ ] #3 Issue title [L]
## Future Vision (Long-Term)
- [ ] #4 Issue title [M]
## Completed Milestones
### YYYY-QN
- [x] #5 Issue title [S]
## Boundary Safeguards
{Hard no's from CONTEXT.md}
```
### Step 5: Write files
Write CONTEXT.md first (it constrains ROADMAP.md). Write ROADMAP.md
second. Run markdownlint on both files after creation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |