Feature Plan

Produce a plan document anyone (engineer, PM, designer, non-technical stakeholder) can read top-to-bottom and understand. Plain language, no jargon, no implementation detail.

Workflow

1. Gather the inputs. Ask the user — or read from conversation context — for:

   • Feature or project name.
   • The problem (who is hurting, how, why now).
   • The intended approach at a story level (not code).
   • Known major components.
   • Phasing intuition (what must come first, what can run in parallel).
   • Anything explicitly out of scope.
   • Decisions not yet made (open questions + likely owners).

   Don't proceed until you have at least: name, problem, solution sketch, and one or more components.

2. Draft using TEMPLATE.md. Fill every section. If a section genuinely has nothing yet, write a one-line note like "To be decided in Phase 1." — don't delete the heading.