ce-speclisted

# Spec **Invocation input:** Feature to specify: $ARGUMENTS Turn one planned feature into an implementation-ready specification. The feature comes from a plan directory produced by `/ce-plan` (`docs/plans/[slug]/`). This workflow closes the four gaps the plan deliberately left open: 1. **Resolve unknowns** — turn the feature's open questions into recorded decisions. 2. **Make scope testable** — turn Scope into acceptance criteria and test cases. 3. **Design against the real codebase** — replace plan-time assumptions with a concrete design. 4. **Produce an executable task list** — ordered, verifiable tasks ready to implement. It does this **without expanding the planned boundary**, and with **a human owning every judgment call**. The spec is done when a competent implementer can execute the task list with no further design decisions. This skill is **staged**. `SKILL.md` (this file) is the orchestrator: it holds the Runtime Inputs, Execution Contract, the always-on disciplines (Scope Lock, Tiered HITL, ADR rules, the Mechanical Lint Gate), and the stage map. Each stage's detailed procedure loads on demand — see *How to Run This Workflow* below. ## Runtime Inputs - **Feature id (required):** e.g. `03-user-profile`, or the qualified form `<plan-slug>/03-user-profile` for explicit selection. Provided by the invocation or the user's request. If missing, read `docs/plans/plans.json` (the plan registry), list the features under each plan, and ask which to specify. Do n