/implement [target]

Implement code from the approved plan. Strict constraints enforced.

First: Activate Workflow

bash

mkdir -p .claude && echo '{"skill":"implement","started":"'$(date -Iseconds)'"}' > .claude/active-workflow.json

Step 0: Load Expert Context (MANDATORY)

Before implementing, read these expert skills:

code

Read: .claude/skills/clarity/        (clear, simple code)
Read: .claude/skills/pragmatism/     (get it working first)
Read: .claude/skills/composition/    (small composable pieces)
Read: .claude/skills/design-patterns/ (proven patterns)

Apply these principles throughout implementation. Skip if files don't exist.

⚠️ STRICT REQUIREMENTS - NO JUDGMENT CALLS

You MUST follow these constraints EXACTLY:

•MAX 30 LINES PER FUNCTION - No function may exceed 30 lines. Split if needed.
•ONE FILE PER CONCERN - No god files. Each file has one purpose.
•FOLLOW THE PLAN - Create exactly the files/functions listed in the plan. No extras.
•MEANINGFUL NAMES - Variables/functions must describe what they do.
•NO HARDCODED VALUES - Use constants or config for magic numbers/strings.
•HANDLE ALL ERRORS - Every operation that can fail must have error handling.

FORBIDDEN (Phase will FAIL if detected):

•Functions longer than 30 lines
•Vague names: data, result, temp, item, stuff, info, obj
•Multiple concerns in one file
•Hardcoded configuration values
•Ignored error cases
•Features not in the plan
•Source citation comments ("Bloch Item 24", "per Kernighan", "Liskov says") — patterns should be self-evident

Process

•Load Plan - Read plan from .claude/plans/ or context
•Check Structure - Verify types/interfaces exist from /structure-first
•Implement - Write code following the plan EXACTLY
•Verify - Ensure code compiles/lints
•Dead Code Cleanup - Remove any dead code introduced (see below)

REQUIRED Output Format

markdown

## Implementation: [feature]

FILES_CREATED:
- path/to/file.ts: [functions defined]

LONGEST_FUNCTION: [name] at [N] lines (must be ≤30)

### Verification:
```bash
$ npx tsc --noEmit
(no errors)

Dead Code Cleanup:

TOOL_USED: [knip|qodana|vulture|deadcode|cargo-udeps] DEAD_CODE_FOUND: [N] items DEAD_CODE_REMOVED: [list or "none"]

APPLIED:

IMPLEMENT_COMPLETE

code


## Dead Code Cleanup (MANDATORY)

After implementation, detect language and remove dead code:

| Language | Detection | Tool | Command |
|----------|-----------|------|---------|
| JS/TS | `package.json` | knip | `npx knip --reporter compact` |
| Java | `pom.xml` or `build.gradle` | Qodana | Use `mcp__qodana__qodana_scan` |
| Python | `pyproject.toml` or `*.py` | vulture | `uvx vulture . --min-confidence 80` |
| Go | `go.mod` | deadcode | `go run golang.org/x/tools/cmd/deadcode@latest ./...` |
| Rust | `Cargo.toml` | cargo-udeps | `cargo +nightly udeps` |
| C# | `*.csproj` | Qodana | Use `mcp__qodana__qodana_scan` |

**Process:**
1. Run the appropriate tool for the detected language
2. Parse output for unused exports, functions, imports, variables
3. Remove dead code directly (no confirmation needed for code YOU just wrote)
4. Re-run tool to verify cleanup

<critical>Only remove dead code in files YOU modified during this implementation. Never touch unrelated files.</critical>

Skip items marked with `@keep`, `// keep`, or `# keep`.

## Validation (Phase will FAIL if violated)

- Any function > 30 lines
- Vague variable names detected
- Files not in plan created without justification
- Dead code left behind in files you created/modified

## 🛑 MANDATORY STOP

After implementation:
- DO NOT proceed to next phase
- DO NOT continue with "let me also..."

**Your turn ends here.** Output IMPLEMENT_COMPLETE and STOP.