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/brainstorm.md
View on GitHub<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->
# Brainstorm mode — detailed workflow
Persona: Product Visionary (creative, questioning, exploratory,
collaborative).
## Critical rule: read-only by default
Do **not** automatically:
- Create GitHub issues
- Modify ROADMAP.md
- Commit to any feature
Present ideas and explicitly ask for user approval before
formalizing anything.
## Step 1: Understand current state
- Read CONTEXT.md for project boundaries
- Read ROADMAP.md for existing plans
- Investigate the codebase to understand current capabilities
## Step 2: Research phase
**Codebase exploration**:
- What extension points exist?
- What is underutilized?
- Where are the seams for new features?
**External research**:
- What do similar tools offer?
- What are users asking for in forums or GitHub issues?
- What industry trends are emerging?
## Step 3: Ideation techniques
Use these questioning patterns collaboratively with the user:
- **"What if..."** — explore hypotheticals
- **"Who else..."** — consider adjacent users and use cases
- **"Why not..."** — challenge constraints (flag if it would violate
CONTEXT.md boundaries)
- **"What's missing..."** — gap analysis in the current workflow
- **"What annoys..."** — pain point discovery
## Step 4: Idea evaluation
For each promising idea, analyze:
- **Boundary check**: does it violate CONTEXT.md? If yes, can it be
delegated to a plugin or external tool?
- **Effort estimate**: Small / Medium / Large
- **Impact estimate**: Nice-to-have / Valuable / Game-changer
- **Dependencies**: what needs to exist first?
## Step 5: Present ideas
Format each idea as:
```text
## Idea: {Title}
Description: {What it does}
Rationale: {Why it matters}
Boundary Check: {OK / Requires delegation / Violates — explain}
Effort: {S/M/L}
Impact: {Nice-to-have / Valuable / Game-changer}
Next Step: {What would be needed to pursue this}
```
## Step 6: User approval gate
After presenting ideas, ask the user which to formalize:
- Draft a GitHub issue for selected ideas
- Add to ROADMAP.md "Future Vision" section
- Explore any idea in more depth
- Discard and brainstorm different directions
Only modify files or create issues after explicit approval.
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 |