Skip to content

dirien/yet-another-agent-harness / .claude/skills/roadmap

roadmap

Verified

Strategic 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.

FileKindSize
SKILL.mdskill md6.8 KB
references/brainstorm.mdmarkdown2.3 KB
references/generate.mdmarkdown2.9 KB
references/label-config.mdmarkdown3.9 KB
references/status.mdmarkdown1.5 KB
references/sync.mdmarkdown4.2 KB

references/label-config.md

View on GitHub
<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->
# Label configuration

Shared label definitions and heuristics used by the sync and generate
modes. Create missing labels before syncing.

## Phase labels (mutually exclusive)

An issue should have exactly ONE phase label.

| Label | Color | Description | ROADMAP.md section |
| ----- | ----- | ----------- | ------------------ |
| `roadmap/current` | `#0E8A16` (green) | Active development | Immediate Focus |
| `roadmap/next` | `#1D76DB` (blue) | Next milestone | Near-Term Vision |
| `roadmap/future` | `#5319E7` (purple) | Later milestones | Future Vision |

## Level of effort labels (mutually exclusive)

An issue should have at most ONE effort label.

| Label | Color | Description | Guideline |
| ----- | ----- | ----------- | --------- |
| `effort/small` | `#c5def5` (light blue) | Small effort | 1-2 hours, straightforward |
| `effort/medium` | `#bfd4f2` (blue) | Medium effort | Half day to 1 day |
| `effort/large` | `#0075ca` (dark blue) | Large effort | Multi-day, complex |

## Effort estimation heuristics

When auto-estimating LOE for issues without an `effort/*` label:

| Signal | Points toward |
| ------ | ------------- |
| Single file change, clear scope | Small |
| Bug fix with known root cause | Small |
| New feature touching 2-4 files | Medium |
| Requires new tests + implementation | Medium |
| API/schema changes | Medium-Large |
| Cross-cutting refactor | Large |
| New subsystem or major feature | Large |
| Requires research or spike first | Large |
| Issue body is vague or underspecified | Medium (default) |

## Contribution labels (additive)

These can be added alongside phase labels.

| Label | Color | Description |
| ----- | ----- | ----------- |
| `community` | `#7057FF` (purple) | Suitable for external contributors |
| `cross-repo` | `#FBCA04` (yellow) | Requires changes in multiple repos |
| `spec-first` | `#D93F0B` (orange) | Blocked on spec/upstream changes |

## LOE indicators in ROADMAP.md

Append effort indicators to issue lines in ROADMAP.md:

- Format: `- [ ] #42 Issue title [S]`
- Key: `[S]` = Small, `[M]` = Medium, `[L]` = Large
- Place after the issue title, before any trailing notes
- If an issue already has an indicator, update it if the GitHub
  label differs

## Label sync behavior

During sync mode:

1. Parse ROADMAP.md to build issue-to-section mapping:
   - "Immediate Focus" → `roadmap/current`
   - "Near-Term Vision" → `roadmap/next`
   - "Future Vision" → `roadmap/future`
2. For each open issue in ROADMAP.md:
   - Fetch current labels from GitHub
   - Remove any incorrect `roadmap/*` labels
   - Add the correct `roadmap/*` label if missing
3. For each closed issue moved to "Completed Milestones":
   - Remove all `roadmap/*` labels
   - Keep `effort/*` labels for historical tracking
4. Report all label changes made

## Label creation commands

Run once if `roadmap/*` labels do not exist:

```bash
# Phase labels
gh label create "roadmap/current" --color "0E8A16" \
  --description "Active development - Immediate Focus"
gh label create "roadmap/next" --color "1D76DB" \
  --description "Next milestone - Near-Term Vision"
gh label create "roadmap/future" --color "5319E7" \
  --description "Future milestones - Future Vision"

# Effort labels
gh label create "effort/small" --color "c5def5" \
  --description "Small effort - 1-2 hours"
gh label create "effort/medium" --color "bfd4f2" \
  --description "Medium effort - half day to 1 day"
gh label create "effort/large" --color "0075ca" \
  --description "Large effort - multi-day"

# Contribution labels (optional)
gh label create "community" --color "7057FF" \
  --description "Suitable for external contributors"
gh label create "cross-repo" --color "FBCA04" \
  --description "Requires changes in multiple repos"
gh label create "spec-first" --color "D93F0B" \
  --description "Blocked on spec/upstream changes"
```
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall