implementlisted

<!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh --> # Implementing Work ## Conventions Read capy knowledge base conventions at [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md). Profile detection is delegated to [shared-profile-detection.md](shared-profile-detection.md). When the sub-task's target files activate a profile that contributes an `implement/` subdirectory (e.g., `../../profiles/k8s/implement/`), its `index.md` lists per-task gotchas the skill must consult BEFORE writing. See Step 2. ## Modes Two modes, determined automatically: **plan mode** when the user references a docs/wip feature or task number; **standalone mode** otherwise (bug fix, GitHub issue, one-off change). When ambiguous, ask. - **Plan mode:** Read [plan-mode.md](plan-mode.md) for entry, iteration, and completion procedures. - **Standalone mode:** Read [standalone-mode.md](standalone-mode.md) for entry procedure. Both modes share the same execution core (Step 2 onward) — profile detection, dependency handling, verification, review. ## Required Outputs After each execution + review cycle, verify all outputs: - [ ] Implementation addresses the requirement (plan mode: matches plan) - [ ] Verification/tests pass - [ ] Code review completed (via `$kk:review-code` — which owns indexing its own `kk:review-findings`) - [ ] New project conventions indexed as `kk:project-conventions` (skip if none established) - [ ] (Plan mode only) `tasks.md` updated