Files

Ed_ a2a1447f58 checkpoint: Claude Code integration + implement missing MCP var tools

Add Claude Code conductor commands, MCP server, MMA exec scripts,
and implement py_get_var_declaration / py_set_var_declaration which
were registered in dispatch and tool specs but had no function bodies.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-28 10:47:42 -05:00

1.5 KiB

Raw Blame History

description

description
Initialize conductor context — read product docs, verify structure, report readiness

/conductor-setup

Bootstrap a Claude Code session with full conductor context. Run this at session start.

Steps

Read Core Documents:
- conductor/index.md — navigation hub
- conductor/product.md — product vision
- conductor/product-guidelines.md — UX/code standards
- conductor/tech-stack.md — technology constraints
- conductor/workflow.md — task lifecycle (skim; reference during implementation)
Check Active Tracks:
- List all directories in conductor/tracks/
- Read each metadata.json for status
- Read each plan.md for current task state
- Identify the track with [~] in-progress tasks
Check Session Context:
- Read TASKS.md if it exists — check for IN_PROGRESS or BLOCKED tasks
- Read last 3 entries in JOURNAL.md for recent activity
- Run git log --oneline -10 for recent commits

Report Readiness: Present a session startup summary:

## Session Ready

**Active Track:** {track name} — Phase {N}, Task: {current task description}
**Recent Activity:** {last journal entry title}
**Last Commit:** {git log -1 oneline}

Ready to:
- `/conductor-implement` — resume active track
- `/conductor-status` — full status overview
- `/conductor-new-track` — start new work

Important

This is READ-ONLY — do not modify files
This replaces Gemini's activate_skill mma-orchestrator + /conductor:setup

1.5 KiB Raw Blame History

/conductor-setup

Steps

Important

1.5 KiB

Raw Blame History