plan-feature

Provide the request in any form — prose, a ticket, or a conversation — and the Skill explores the repo, routes the work to a new or existing feature slice, settles open key decisions with you one at a time, and ends with a readable plan summary for approval.

Routing is decided by where the behaviour lives: it reads every existing SPEC.md and its criteria, then routes to amend when a governed slice already owns the behaviour, new when none does, and carve when the behaviour runs but is ungoverned.

A key decision is a choice the input leaves open with more than one viable answer that shapes the slice across criteria, such as a rounding policy or data shape. Each is asked one at a time with a recommendation, then captured into an ADR or CONTEXT.md glossary entry.

Yes. When no one can answer, the Skill takes its own recommendation and flags the decision as defaulted in the plan summary and at the end of the pipeline, so a defaulted decision is never silent.

Plan lenses are optional repo-defined markdown prompts in .speccle/lenses/plan/ that review a plan's shape. Each runs as a parallel subagent, and findings are advisory only — they cannot veto the plan and are surfaced in the summary for the human to rule on.

No. It drafts no criteria and writes no code; its only files are decision records such as ADRs and glossary entries. Criteria drafting belongs to the downstream spec-feature stage in the same session.