---
name: project-management
source: botcore
description: >
  Orchestrate GitHub Projects, issues, specs, and parallel Claude agent waves.
  Use when creating issues, managing features, launching agent waves, or tracking
  STATUS.md files.
version: "1.1.0"
triggers:
  - project management
  - create issue
  - launch agents
  - wave orchestration
  - STATUS.md
  - feature lifecycle
  - parallel development
---

# Project Management

Expert guidance for orchestrating GitHub-based development with parallel Claude agents.

## Capabilities

1. **Feature Lifecycle** — Manage features from proposed → active → complete
2. **Issue Orchestration** — Create parent issues with sub-issue waves
3. **Agent Waves** — Launch parallel Claude agents for implementation
4. **Status Tracking** — Monitor progress via STATUS-{issue}.md files

## Quick Commands

```bash
# Launch agent for an issue
lush agent launch --issue 19 --repo lushbot

# Launch parallel agents (wave)
lush agent wave --issues 20,21 --repo lushbot

# Check agent status
lush agent status
```

## Routing Logic

| Request Type | Load Reference |
|--------------|----------------|
| Feature folder structure, lifecycle | [references/feature-lifecycle.md](references/feature-lifecycle.md) |
| Issue templates, parent/sub pattern | [references/issue-templates.md](references/issue-templates.md) |
| Wave orchestration, parallel agents | [references/wave-orchestration.md](references/wave-orchestration.md) |
| STATUS.md tracking, templates | [references/status-tracking.md](references/status-tracking.md) |
| CLI commands, lush agent | [references/cli-commands.md](references/cli-commands.md) |
| Proposal/spec review, CLI handoff | [references/spec-review-workflow.md](references/spec-review-workflow.md) |

## Core Principles

### 1. Feature-Centric Organization

```
docs/features/
├── proposed/       # Draft proposals awaiting review
├── active/         # Approved, in implementation  
└── complete/       # Shipped (reference archive)
```

### 2. Proposal Status Lifecycle

Proposals use YAML frontmatter to track status:

```yaml
---
status: captured  # captured → draft → ready
author: Author Name
created: 2026-01-11
updated: 2026-01-11
---
```

| Status | Meaning |
|--------|---------|
| `captured` | Idea captured, not yet refined |
| `draft` | Being refined, not ready for review |
| `ready` | Ready for Opus review and approval |

Move to `active/` only after Opus review approves and creates a spec.


### 3. Wave-Based Parallelization

Analyze dependencies, group into waves:

| Wave | Issues | Agents |
|------|--------|--------|
| Wave 1 | #188, #189 (no deps) | 2 parallel |
| Wave 2 | #190, #191 (after Wave 1) | 2 parallel |
| Wave 3 | #192 (after Wave 2) | 1 agent |

### 4. STATUS-{issue}.md Tracking

Each issue gets a status file with YAML frontmatter:

```yaml
---
id: feature-name-188
phase: complete
pr: 193
updated: 2026-01-10T15:15
agent: issue-188
---
```

Template: `.agent/templates/STATUS.md`

### 5. Completion Instructions

Agents receive standard completion steps:
1. Update STATUS-{issue}.md with progress
2. Create branch, run tests
3. Commit, push, create PR

## Supported Repositories

| Repo | Path |
|------|------|
| `afd` | `d:\Github\lushly-dev\AFD` |
| `lushbot` | `d:\Github\lushly-dev\lushbot` |
| `lushly` | `d:\Github\lushly-dev\lushly` |
| `violet` | `d:\Github\lushly-dev\Violet` |
| `fast-af` | `d:\Github\lushly-dev\fast-af` |

## When to Escalate

- **Cross-repo dependencies** — Features spanning multiple repositories
- **Merge conflicts** — Wave PRs conflicting with each other
- **Agent failures** — Agents stuck or producing invalid output
