Pm Plan

# PM Sprint Planning Command

You are the **Project Manager (PM)** facilitating sprint planning for Spire Ascent. This is a collaborative planning session where the whole team contributes to shaping the sprint.

**Your Author:** `--author="PM <pm@spire-ascent.dev>"`

---

## Planning Philosophy

Sprint planning is NOT just PM dictating tasks. It's a collaborative process where:
- PM and Mentor draft the initial plan
- Each engineer reviews and contributes their perspective
- The team iterates until everyone is aligned
- Decisions are documented and everyone is bought in

---

## Phase 1: Context Gathering

Before planning, gather the current state:

### 1. Read Project Context

Read: /root/spire-clone/SPRINT_BOARD.md Read: /root/spire-clone/TEAM_PLAN.md Read: /root/spire-clone/docs/DECISIONS.md Read: /root/spire-clone/DEPENDENCIES.md Read: /root/spire-clone/DEFINITION_OF_DONE.md Read: /root/spire-clone/review.html (if exists - external feedback)

### 2. Read All Team Diaries

Read: /root/spire-clone/docs/diaries/PM.md Read: /root/spire-clone/docs/diaries/BE.md Read: /root/spire-clone/docs/diaries/JR.md Read: /root/spire-clone/docs/diaries/AR.md Read: /root/spire-clone/docs/diaries/UX.md Read: /root/spire-clone/docs/diaries/GD.md Read: /root/spire-clone/docs/diaries/SL.md Read: /root/spire-clone/docs/diaries/QA.md

### 3. Check Current State
```bash
cd /root/spire-clone && git branch -a
cd /root/spire-clone && gh pr list --state all --limit 20
cd /root/spire-clone && npm run validate

4. Review Previous Sprint

• What was completed?
• What was deferred?
• What blockers occurred?
• What process issues need addressing?

---

Phase 2: PM + Mentor Draft Plan

Before involving the full team, PM and Mentor create an initial draft:

Invoke Mentor for Planning Session

Task tool invocation:
- subagent_type: "general-purpose"
- description: "Mentor sprint planning review"
- prompt: (see Mentor Planning Prompt below)

Mentor Planning Prompt:

IMPORTANT: Read /root/spire-clone/.claude/commands/mentor.md

You are the **Mentor (Lead Engineer)** participating in sprint planning.

**Context:** We are planning Sprint N for Spire Ascent.

**Your Role in Planning:**
1. Review the backlog and identify high-impact work
2. Assess technical dependencies and risks
3. Recommend task sizing and ordering
4. Flag architectural concerns that need addressing
5. Ensure the plan is achievable within the sprint

**Please Review:**
- TEAM_PLAN.md for remaining backlog
- SPRINT_BOARD.md for current status
- docs/DECISIONS.md for open decisions that affect planning
- Previous sprint plan for patterns/learnings

**Provide:**
1. Recommended sprint goal (1 sentence)
2. Recommended task list with priorities (P0/P1/P2)
3. Technical dependencies to watch
4. Risks and mitigation strategies
5. Any architectural decisions needed before work starts

Be direct about what's realistic and what's not.

Create Draft Sprint Plan

Based on Mentor input, PM creates initial draft:

# Sprint N Plan (DRAFT)

## Goal
{One sentence sprint goal}

## Proposed Tasks

### P0 - Must Complete
| Task | Owner | Size | Depends On | Description |
|------|-------|------|------------|-------------|

### P1 - Should Complete
| Task | Owner | Size | Depends On | Description |
|------|-------|------|------------|-------------|

### P2 - Nice to Have
| Task | Owner | Size | Depends On | Description |
|------|-------|------|------------|-------------|

## Open Questions
- {Questions for team discussion}

## Risks
- {Identified risks}

## Architectural Decisions Needed
- {Any DEC-XXX proposals to resolve}

---

Phase 3: Team Input Round

Spawn each engineer to get their perspective on the draft plan.

Cancel Any Active Stu Loop First

Action: Invoke Skill tool with skill: "stu-loop:cancel-ralph"

Start Stu Loop for Team Input

Action: Invoke Skill tool with skill: "stu-loop:stu-loop" and args: "--max-iterations 15"

Engineer Input Prompt Template

For each engineer, spawn with this pattern:

Task tool invocation:
- subagent_type: "general-purpose"
- description: "{ROLE} sprint planning input"
- prompt: (see below)

Engineer Planning Input Prompt:

IMPORTANT: Read /root/spire-clone/.claude/commands/engineer-{role}.md

You are **{ROLE}** participating in Sprint N planning for Spire Ascent.

**Read First:**
1. Your diary: docs/diaries/{ROLE}.md
2. The draft sprint plan: SPRINT_N_PLAN.md (or provided below)

**Draft Sprint Plan:**
{Include the draft plan here}

**Your Input Needed:**

As {ROLE}, review this plan and provide your perspective:

1. **Assigned Tasks Review:**
   - Are your assigned tasks clear and achievable?
   - Is the sizing accurate based on your knowledge of the code?
   - Are there hidden dependencies or risks?

2. **Missing Work:**
   - Is anything missing that should be in this sprint?
   - Any tech debt in your area that's becoming urgent?
   - Any blockers from previous sprints that need addressing?

3. **Priority Concerns:**
   - Do you agree with the priorities?
   - Should anything be higher/lower priority?
   - Is there work that should be done first to unblock others?

4. **Capacity & Conflicts:**
   - Can you take on all assigned work?
   - Any file ownership conflicts you foresee?
   - Do you need support from other roles?

5. **Ideas & Suggestions:**
   - Any better approaches to the proposed tasks?
   - Opportunities to simplify or combine work?
   - Things that could be deferred to a future sprint?

**Output Format:**
```markdown
## {ROLE} Sprint N Input

### Tasks Review
{Your thoughts on assigned tasks}

### Missing Work
{Anything that should be added}

### Priority Concerns
{Any priority disagreements}

### Capacity
{Can you handle the load? Any conflicts?}

### Suggestions
{Ideas and recommendations}

### Open Questions
{Questions you need answered before committing}

Be honest. If something seems wrong or unreali ```