Add specialized agents and product lenses to CLAUDE.md
- md-database, md-discord, md-league, md-ops agents defined in .claude/agents/ - "When to Use Which Agent" guide for routing decisions - Product lenses section (Operations, Experience, Growth) - ROADMAP.md skeleton with future considerations Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
f9d5494615
commit
3359d2fc19
31
CLAUDE.md
31
CLAUDE.md
@ -117,3 +117,34 @@ Major Domo has a searchable knowledge base for release notes, session summaries,
|
|||||||
- **Tags**: `major-domo`, `database`, `deployment`, `release-notes`, `discord`, etc.
|
- **Tags**: `major-domo`, `database`, `deployment`, `release-notes`, `discord`, etc.
|
||||||
|
|
||||||
Always check the KB before investigating issues that may have been solved before.
|
Always check the KB before investigating issues that may have been solved before.
|
||||||
|
|
||||||
|
## Specialized Agents
|
||||||
|
|
||||||
|
Use these agents when working on specific sub-projects:
|
||||||
|
|
||||||
|
| Agent | Model | Domain | When to Use |
|
||||||
|
|---|---|---|---|
|
||||||
|
| `md-database` | Opus | Database API | Schema changes, migrations, endpoints, service layer |
|
||||||
|
| `md-discord` | Opus | Discord bot | Commands, UX flows, services, background tasks |
|
||||||
|
| `md-league` | Opus | League strategy | Season ops, feature priorities, roadmap, cross-project coordination |
|
||||||
|
| `md-ops` | Sonnet | Release ops | Merging PRs, deploys, branch cleanup, process enforcement |
|
||||||
|
|
||||||
|
PO agents (Opus) decide **what** to build. `md-ops` (Sonnet) ensures it **ships correctly** — reviewed, tested, deployed in order. Implementation is delegated to `engineer`, `issue-worker`, or `swarm-coder` agents.
|
||||||
|
|
||||||
|
### When to Use Which Agent
|
||||||
|
|
||||||
|
- **Design question** about an API endpoint or schema → `md-database`
|
||||||
|
- **Design question** about a bot command or UX flow → `md-discord`
|
||||||
|
- **"Should we build X?"** or cross-project feature planning → `md-league`
|
||||||
|
- **Merge a PR**, deploy, tag a release, clean up branches → `md-ops`
|
||||||
|
- **Write code** to implement a spec → `engineer` or `swarm-coder` (not the PO agents)
|
||||||
|
|
||||||
|
## Product Lenses
|
||||||
|
|
||||||
|
Work is organized by league impact:
|
||||||
|
|
||||||
|
- **Operations**: Season lifecycle, transaction reliability, commissioner tools
|
||||||
|
- **Experience**: Command usability, mobile-friendly interactions, response times
|
||||||
|
- **Growth**: Website features, gameplay simulation, draft modernization, external integrations
|
||||||
|
|
||||||
|
See `ROADMAP.md` for the current product roadmap.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user