metis: Command for Claude Code

Workspace Resolution

1. If $ARGUMENTS specifies a project name or todo, parse accordingly
2. Otherwise, use the most recently modified directory under workspaces/ (excluding instructions/)
3. If no workspace exists, ask the user to create one first
4. Read all files in workspaces/<project>/briefs/ for user context (this is the user's input surface)

Phase Check

• Read files in workspaces/<project>/todos/active/ to see what needs doing
• Read files in workspaces/<project>/todos/completed/ to see what's done
• If $ARGUMENTS specifies a specific todo, focus on that one
• Otherwise, pick the next active todo
• Reference plans in workspaces/<project>/02-plans/ for context
• If any file in briefs/ was modified after specs/_index.md, STOP — briefs changed since analysis. Flag for user decision: re-run /analyze or acknowledge the brief change.

Execution Model

This phase executes under the autonomous execution model (see rules/autonomous-execution.md). Implementation is fully autonomous — agents execute in parallel, self-validate through TDD, and converge through quality gates. The human observes outcomes but does not sit in the execution loop. Pre-existing failures are fixed, not reported (zero-tolerance). Agent-to-agent delegation (reviewer, security-reviewer) is autonomous, not human-gated.

Workflow

NOTE: Run /implement repeatedly until all todos/active have been moved to todos/completed

1. Prepare todos

You MUST always use the todo-manager to create detailed todos for EVERY SINGLE TODO in todos/000-master.md.

• Review with agents before implementation
• Ensure that both FE and BE detailed todos exist, if applicable

2. Context anchoring (MUST run before each todo)

Before implementing ANY todo, re-read the source material that spawned it:

1. Re-read the relevant spec files — check specs/_index.md, identify which spec files cover the domain of this todo, and read them. The spec is the authority on what to build. If the spec says create_user(name, email, password_hash), that is the signature.
2. Re-read the plan section in 02-plans/ that this todo implements — not the whole directory, but the specific plan paragraphs. If the plan describes a DataFabric class with 3 methods, you are building that class with those 3 methods.
3. Re-read relevant journals in workspaces/<project>/journal/ — decisions, trade-offs, and risks from analysis inform how to implement. If a journal says "chose event-driven over polling because of X," the implementation must be event-driven.
4. Re-read the todo itself — the description, not just the title. Todos have implementation details that get ignored when agents skim titles.
5. Read current source code before calling any existing service or function. Do not trust plans, specs, or previous todos for current method signatures — the code is the truth for what exists NOW. Specs are the truth for what SHOULD exist.