Plan Phase

gh issue create --title "{title}" --body "$(cat <<'EOF'
## Summary
{description}

## Acceptance Criteria
- [ ] {criterion 1}
- [ ] {criterion 2}

## Origin
{why this work exists — user request, retro finding, dependency, etc.}
EOF
)" --label "phase-{N}" --label "{category}"

3. Assign to team members

For each issue, determine the best assignee based on:

• Expertise match (check roster cards for tech preferences and work affinity)
• Current load balancing (check how many issues each member already has)
• Repo familiarity

Apply the assignee label:

gh issue edit {NUMBER} --add-label "{FIRSTNAME_LASTNAME}"

4. Multi-perspective review

Review each issue from 6 perspectives. For each perspective, assess whether the issue description is complete and whether there are concerns:

For each concern raised, either:

• Update the issue description to address it
• Post a review comment on the issue explaining the concern and resolution

gh issue comment {NUMBER} --body "$(cat <<'EOF'
**{Perspective} Review**

{findings — concerns, suggestions, or "No concerns"}
EOF
)"

5. Dependency analysis

Build a dependency graph across the proposed issues:

• Which issues must complete before others can start?
• Which issues touch the same files/systems (serialize to avoid conflicts)?
• Which cross-repo dependencies exist?

6. Propose wave structure

Group issues into waves based on:

• Priority: live bugs > security > tech debt > features > polish (per charter)
• Dependencies: blockers in earlier waves, dependents in later waves
• Parallelism: maximize concurrent work by grouping independent issues
• Repo grouping: minimize context-switching per agent

Present the proposed structure:

**Phase {N} Plan**

### Wave 1: {theme}
| Issue | Title | Assignee | Priority | Dependencies |
|-------|-------|----------|----------|--------------|
| #N    | ...   | Name     | bug      | None         |

### Wave 2: {theme}
| Issue | Title | Assignee | Priority | Dependencies |
|-------|-------|----------|----------|--------------|
| #N    | ...   | Name     | feature  | Wave 1: #M   |

**Total issues:** {count}
**Estimated waves:** {count}
**Cross-repo dependencies:** {list or "None"}

7. Present to user for approval

Display the full plan. Do NOT create issues or start implementation without user approval. The user may:

• Approve the plan as-is
• Request changes to scope, assignments, or wave grouping
• Defer specific items to a later phase

What remains manual

• User must approve the plan before issues are created
• Cross-team dependency resolution requires coordination with other repo managers
• Effort estimates are rough — actual complexity may shift items between waves