jpmschweitzerandClaude Opus 4.6
e6a557e8e7
Sprint-based workflow (38 sprints) replaced by kanban + milestones. Milestones are many-to-many with tickets and can block each other. New: /whats-next skill (dependency-driven batch selection with Si refinement review), /pr-process skill (renamed from pr-push, adds review comment pickup), clerk agent + pre-push hook for D-record consistency checks. Deleted: sprint CLI, sprint-start/sprint-plan/sprint-status skills, team-scoped file restrictions. Si rewritten as refinement manager. All 19 agent briefings updated from stale PROJECT_STATE.md reference to live ticket milestone queries. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
34 lines
1.8 KiB
Markdown
34 lines
1.8 KiB
Markdown
# Team Patterns
|
|
|
|
## Model selection
|
|
|
|
Default model is Opus 4.6 (200K context). For heavy sessions (workshops,
|
|
large reviews, milestone planning), switch to extended context on-demand:
|
|
|
|
- `/model sonnet[1m]` — Sonnet 4.6 with 1M context window
|
|
- `/model opus[1m]` — Opus 4.6 with 1M context window
|
|
- Cost: 2x input + 1.5x output for tokens beyond 200K (Tier 4 required)
|
|
|
|
## Large content pushes
|
|
|
|
When producing many files (wiki pages, content batches, bulk docs):
|
|
1. **Lore librarian** agent (read-only): ingests all source material, answers focused context queries from writers, tracks cross-file consistency
|
|
2. **Multiple writer** agents (parallel, by domain): each gets a task slice, writes directly to disk using the Write tool — one file at a time, write often, no text accumulation
|
|
3. **Reviewer** agents (blocked until writing done): check voice consistency, attribute uniformity, style
|
|
|
|
Key: writers use Write tool directly (no transcription bottleneck), librarian catches contradictions early, split work by domain not volume.
|
|
|
|
## Team monitoring (stuck agent detection)
|
|
|
|
When leading a team (workshop, batch, or any multi-agent session):
|
|
|
|
**Agent heartbeat rule** — include in every agent spawn prompt:
|
|
> If you have been working on a single task for more than 15 minutes
|
|
> without making progress, message the team lead with what is blocking
|
|
> you. Do not keep retrying the same approach silently.
|
|
|
|
**Team lead proactive checks:**
|
|
- If an agent has not sent a message in ~20 minutes, ping them for a status update.
|
|
- **Bottleneck detection:** if other agents are idle and waiting on one agent's output, that agent's silence is a red flag — check on them immediately, do not wait for the next natural message.
|
|
- When checking on a stuck agent, offer to reassign the task or pull in another agent to help.
|