project
Manage route-agent project: check status, find next tasks, spawn parallel work. Use when starting work, checking progress, or asking "what's next?"
When & Why to Use This Skill
This Claude skill automates software project orchestration by tracking milestones, identifying ready tasks through dependency analysis, and managing parallel execution. It integrates seamlessly with GitHub and Git worktrees to streamline the development lifecycle, allowing agents to spawn sub-tasks, monitor progress, and maintain project velocity autonomously.
Use Cases
- Automated Status Tracking: Generate instant reports on milestone progress and issue status by fetching real-time data from GitHub repositories.
- Intelligent Task Prioritization: Automatically identify 'Ready' tasks by parsing issue bodies for dependencies, ensuring that agents only work on unblocked items.
- Parallel Development Orchestration: Scale engineering throughput by spawning multiple sub-agents in isolated worktrees to implement features or fixes concurrently.
- Environment Maintenance: Simplify repository management by automatically cleaning up local worktrees once pull requests are merged.
| name | project |
|---|---|
| description | | |
| Manage route-agent project | check status, find next tasks, spawn parallel work. Use when starting work, checking progress, or asking "what's next?" |
| - Bash(gh | *) |
| - Bash(git | *) |
Project Management
Assess project status, find ready tasks, and orchestrate parallel work.
Commands
| Command | Action |
|---|---|
/project |
Show milestone progress and ready tasks |
/project next |
Recommend single next task |
/project work |
Spawn sub-agents for ready tasks (parallel) |
/project work #N |
Work on specific issue |
/project cleanup |
Remove worktrees for merged PRs |
Quick Start
# Milestone progress
gh api repos/bendrucker/route-agent/milestones --jq '.[] | "\(.title): \(.closed_issues)/\(.open_issues + .closed_issues)"'
# Open issues
gh issue list --repo bendrucker/route-agent --state open --json number,title,milestone,body --limit 100
Finding Ready Tasks
Ready = No "Depends On" section, OR all dependencies closed.
Parse from issue body:
## Depends On
- Issue title here
Parallel Work (/project work)
- Find ready tasks - Parse dependencies, filter unblocked
- Create worktrees - One per issue in
./worktrees/<N>/(inside project, sandbox-allowed) - Spawn sub-agents - Each works in background, creates PR
- Report - List spawned agents for monitoring
See references/worktrees.md for details.
Sub-Agent Prompt
Work on issue #N in worktree at <path>.
Issue: <title>
<body>
1. cd to worktree
2. Read CLAUDE.md and relevant docs
3. Implement requirements
4. Commit with descriptive message
5. Push and create PR with "Closes #N"
6. Return PR URL
Milestone Priority
- Foundation
- Eval Setup (parallel)
- Strava Integration
- GraphHopper Integration
- Route Synthesis
- Place Search, Water Stops, Climb Integration, Weather Integration
- Ride Preparation, Narrative Research
- Research Quality, Route Refinement
- Evaluation Framework
Output
Status:
## Project Status
### Foundation (1/2)
- [x] #2 SDK project structure
- [ ] #3 Checkpoint system - READY
### Ready (2)
- #3 Checkpoint system (Foundation)
- #4 Promptfoo setup (Eval Setup)
Work:
## Parallel Work
Spawning:
- #3 Checkpoint system → worktree created, agent launched
- #4 Promptfoo setup → worktree created, agent launched
Monitor with /tasks. PRs appear for review.