ce-implementlisted

# Implement **Invocation input:** Feature to implement: $ARGUMENTS Work a feature's `tasks.json` to done — implement each task, verify it against the spec's test cases, and confirm every acceptance criterion is met. Implementation always runs from canonical `specs/<id>/ce-spec.md` + `tasks.json`. If the approved `plan.json` gives an unambiguous feature `specification_route: compact` and its Markdown projection matches, this workflow may compose those artifacts before code changes; assurance is retained, not bypassed. It is **resumable** — it implements the next pending tasks and updates their status; re-run it to continue. A large feature need not finish in one pass. ## Runtime Inputs - **Feature id (required):** e.g. `03-user-profile`, or the qualified form `<plan-slug>/03-user-profile` for explicit selection. If missing, read `docs/plans/plans.json` and list planned features; ask only when selection is ambiguous. - **Loaded implementation authority:** `specs/<id>/ce-spec.md` and `specs/<id>/tasks.json` are the contract, whether pre-existing or composed by the compact path. - **Plan context:** load canonical `plan.json`, `feature-plan.md`, `features/<id>.md`, `shared-context.md`, `architecture-selection.json`, and applicable threat/interaction artifacts. A missing, symlinked, or mismatched authority routes to `/core-engineering:ce-plan` before code changes. - **Other loaded context:** the ADRs referenced by the spec and `docs/plans/vc-policy.md`. A