implement

Implement

Start implementation for $ARGUMENTS.

Phase 1: Read Specification

• If $ARGUMENTS is a directory path, read order.md and todo.md from that directory
• Otherwise, look for specs/{feature-name}/order.md and specs/{feature-name}/todo.md
• If todo.md exists, process tasks from top to bottom, marking each - [x] on completion

If no specification is found: STOP and ask the user to provide the spec directory path or run /specify first.

Phase 2: Project Environment Detection

Detect the project's language, frameworks, and tooling to determine the correct test/lint/build commands.

Test, Lint, and Build Commands

Auto-detect the project's test, lint, and build commands from configuration files (package managers, task runners, build tools, etc.). If undetectable, ask the user.

• Monorepo: If the project is a monorepo, detect commands per package/workspace rather than the entire repository.
• Non-interactive mode: Always run commands in non-interactive mode to prevent watch-mode hangs.

Coverage Command and Thresholds

Detect the project's coverage command and minimum coverage thresholds:

1. Detect the coverage command and configured thresholds from the project's configuration files
2. If thresholds exist, coverage verification becomes mandatory in Phase 4

Project Conventions

• Read CLAUDE.md if present
• Read AGENTS.md if present
• Check docs/ directory for architecture and coding guidelines

Phase 3: Sequential Task Execution

For each task in the task list, execute steps 1–6 in order. Do NOT proceed to the next task until all quality gates in step 5 pass.

1. Understand the task

• Read and understand the task requirements from the specification
• Check for similar existing implementations to follow as patterns

2. Impact analysis

Before writing code, identify existing code that depends on or is affected by the change (callers, imports, shared types, configuration). List affected files and assess risk of breakage.