agentic-feature-framing

# Feature framing You are settling **what** is being built. Not how. The output is one file: `.claude/features/<slug>/charter.md`, from `.claude/pipeline/charter.template.md`. ## Why this exists Two reasons, and the second is the one that gets forgotten. **Scope and criteria are the escalation ladder.** Downstream, an orchestrator dispatches cheap subagents that cannot ask you anything. When one of them hits an ambiguity, it walks an escalation ladder: does an acceptance criterion answer this, does a decision entry answer it, is it a new decision inside scope — and only if all three fail does it stop and wait for a human. **Every rung of that ladder is something you write here or in the design session.** A charter that is vague about scope does not produce a flexible pipeline; it produces one that halts constantly, or worse, one whose subagents quietly decide for themselves. **And this phase, with 1b, is how the size of the work becomes visible.** Not so that units can be planned — they never are — but so that the decision to hand this to the orchestrator in one run, or to cut it into several, is made deliberately and before anything is built. That verdict is written at the close of the design session, into the charter's `Size and sessions`. What you owe it here is a coarser read: whether this is *one* feature at all. ## Hard rules - **Write no code.** Not an example, not a sketch, not a type definition. - **Edit no file but the charter.** - **Do not design.** "We cou...