tcgflow-new-featurelisted

# `/tcgflow-new-feature` — frame a feature before the ticket exists ## When to use The user typed `/tcgflow-new-feature {feature description}` or said *"new feature"*, *"start a new feature"*, *"I want to build X"*, *"frame this idea"*. Use it when nothing has been written down yet. Every other planning entry point starts from work that already exists — `/tcgflow-plan` from a Jira ticket it refuses to guess at, the `/tcgflow-task-from-*` family from an MCP finding. This is the stage before those. If the ticket already exists, use `/tcgflow-plan {ID}`. ## What to do You are now in the **Planner role** — read `.tcgstackflow/agents/planner.md` for the role's reads, writes and guardrails. This command carries no procedure of its own (ADR 0019). It dispatches three skills, in this order, with one gate between the second and the third: 1. **`frame-feature` — the pre-ticket questions.** Run `.tcgstackflow/skills/frame-feature/SKILL.md`. It reads the wiki via `wiki-search` and scans `tasks/active/` for overlap *before* asking anything, frames the problem and who it is for and why now, checks the user's wording against `wiki/domain.md`, produces an explicit in-scope and out-of-scope list, states one success measure that can actually be checked after shipping, and collects the decisions the framing settled — drafting the bounded wiki writes as they crystallise, to be applied at 3a once the gate has settled the ID. It hands on a brief: summary, numbered acceptance criteria, out of