Plan Feature — Interview (internal)

Turn a rough idea into a well-scoped, architecture-respecting feature through a focused interview. Optimizes for catching unknowns before implementation.

When to use

• The plan-feature router calls this when the input is a vague idea (or the user forces it with --interview) and wants help thinking it through before any code.

Step 0 — Discover the project (always first)

Per the agent guide's Workflow conventions + documentation map, then read what THIS skill needs: the architecture doc, the domain/style docs relevant to the idea's area, the SPEC template, and the roadmap. Goal: ask only what the project does not already answer, and ground every question in the project's real constraints (layering, domain/i18n/SEO/a11y rules, runtime/platform limits, naming conventions).