implementlisted

# Implement ## Step 1: Read the context Read everything. Subagents cannot access the codebase — you are their only source of context. **Internal docs** - `.harness/engineering/architecture.md` — stack, components, data flow, constraints - `.harness/engineering/implementation-plan.md` — phases and task ordering - `.harness/engineering/features/` — all feature spec files (read every one) - `.harness/adr/` — architectural decisions that constrain implementation - `.harness/product/CONTEXT.md` — domain vocabulary (use these terms exactly in all code) **Codebase** - `CLAUDE.md` — conventions, naming, patterns, do-not-edit files - `README.md` — public description, install/run instructions - Scan key directories: identify what files exist, what each does, what's absent - Check `package.json` / `pyproject.toml` / `go.mod` — dependencies and scripts Build a dependency map: - Which features are `planned`? - Which phase is current — the lowest phase number with `planned` features? - Within the current phase, are any features dependent on others in the same phase? If there is a conflict between `implementation-plan.md` and a feature spec, the feature spec takes precedence — it is the authoritative technical reference. Use `implementation-plan.md` only for phase ordering and task dependencies. ## Step 2: Classify features as HITL or AFK Before implementing anything, classify each `planned` feature in the current phase: **AFK** (can be implemented autonomously) — ALL must be true: