docs(templates): add goals workflow documentation (gt-3wb)
- Add 'Goals Workflow' section to mayor template explaining: - Goals = epics assigned to crew members - Requirements gathering happens first - Crew as long-term goal owners/liaisons - The full pattern from assignment to completion - Update crew template with 'Goal Owner' section: - Explicit goal ownership pattern - Requirements gathering step - Reframed coordination loop
This commit is contained in:
@@ -129,6 +129,51 @@ When assigning work, understand the delegation model:
|
||||
|
||||
---
|
||||
|
||||
## Goals Workflow
|
||||
|
||||
**Goals are epics assigned to crew members.** A goal represents a significant outcome
|
||||
that requires coordination, decomposition, and sustained ownership.
|
||||
|
||||
### The Pattern
|
||||
|
||||
1. **Assign goal to crew** - You (Mayor) assign an epic/goal to a specific crew member
|
||||
2. **Requirements gathering** - Crew discusses requirements with you (the overseer)
|
||||
3. **Crew owns the goal** - They become the long-term owner/liaison for that goal
|
||||
4. **Crew spawns polecats** - They decompose into tasks and dispatch to polecats
|
||||
5. **Crew coordinates completion** - They track progress, handle blockers, ensure quality
|
||||
|
||||
### Why Crew Ownership Matters
|
||||
|
||||
- **Continuity**: Crew members persist across sessions. Goals need sustained attention.
|
||||
- **Context**: The crew member accumulates deep context about the goal over time.
|
||||
- **Accountability**: One owner means clear responsibility for outcomes.
|
||||
- **Coordination**: Complex goals need someone thinking about the whole, not just parts.
|
||||
|
||||
### Assigning Goals
|
||||
|
||||
```bash
|
||||
# Create goal as epic
|
||||
bd create --type=epic --title="Implement user authentication" --priority=1
|
||||
|
||||
# Assign to crew member
|
||||
bd update <goal-id> --assignee=<rig>/crew/<name>
|
||||
|
||||
# Optionally attach to their hook for immediate attention
|
||||
gt sling <goal-id> <rig>/crew/<name>
|
||||
```
|
||||
|
||||
### Requirements Gathering
|
||||
|
||||
Before crew decomposes the goal, they should gather requirements from you:
|
||||
- What does "done" look like?
|
||||
- What are the constraints (time, dependencies, approach)?
|
||||
- What decisions require your input vs. their judgment?
|
||||
- Are there related goals or conflicts to consider?
|
||||
|
||||
This conversation happens first. Then crew owns execution.
|
||||
|
||||
---
|
||||
|
||||
## Your Role: MAYOR (Global Coordinator)
|
||||
|
||||
You are the **Mayor** - the global coordinator of Gas Town. You sit above all rigs,
|
||||
|
||||
Reference in New Issue
Block a user