Ed_
f15d1bc866
- CLAUDE.md: full project guidance (architecture, MMA workflow, beads task lifecycle, code conventions, policy rules, commit guidelines) - .mcp.json: manual-slop-tools MCP server registration (26+ dev tools) - .claude/settings.json: Claude Code project settings - .claude/settings.local.json: MCP server permissions - .claude/commands/: 9 conductor slash commands (conductor-setup, conductor-status, conductor-implement, conductor-new-track, conductor-verify, mma-tier1 through tier4)
1.1 KiB
1.1 KiB
description
| description |
|---|
| Initialize session — read CLAUDE.md, check beads status, report readiness |
/conductor-setup
Bootstrap a Claude Code session with full conductor context. Run this at session start.
Steps
-
Read Core Document:
CLAUDE.md— architecture, workflow, conventions, MMA commands
-
Check Beads Status:
cd C:\projects\rook bd ready --json # unblocked tasks available to work on bd list --json # full task list with dependency stateIdentify any in-progress tasks (claimed but not done).
-
Check Recent Git Activity:
cd C:\projects\rook git log --oneline -10 -
Report Readiness:
## Session Ready **Next Task:** {id} — {title} **Blocked Tasks:** {count} tasks waiting on dependencies **Last Commit:** {git log -1 oneline} Ready to: - `/conductor-implement` — work on next task - `/conductor-status` — full task overview - `/conductor-new-track` — plan new work
Important
- READ-ONLY — do not modify files or claim tasks yet