ce-planlisted

# Plan **Invocation input:** Project description: $ARGUMENTS Decompose a project description into an ordered, dependency-aware list of implementation features — validated for sizing, risk, reachability, and session fit — and write it to a single planning artifact. This skill is **staged**. `SKILL.md` (this file) is the orchestrator: it holds the Execution Contract, Core Concepts, and the stage map. Each stage's detailed procedure lives in a separate file you load only when you reach that stage — do not load them all up front. ## Runtime Inputs - **Project description (required):** provided by the invocation or the user's request. If it is empty or missing, ask the user for the project description in one short prompt before proceeding. Do not invent a description. - **Project brief (optional):** a dedicated `brief:` input — `brief=docs/briefs/<slug>.md` on the invocation line, or a `brief:` argument when invoked directly (e.g. by `/ce-brief` at handoff). Distinct from the project-wide reference-document list, this channel arms the **Brief-Aware Skip Contract** in Stage 1.4: the brief's intent answers let Stage 1.4 skip what it already covers and ask only the codebase-grounded residue. - **Optional inputs** (project-wide reference documents, target tool, ordering constraints, MVP notes, known risks, environment pitfalls, preferred stack, examples, existing conventions): collect interactively per Stage 1 only when needed for feature boundaries, ordering,