feature-define

To define a feature before development, you can use an interactive interview process to capture the problem, scope, and approach, producing a structured feature-definition markdown file for downstream consumption.

Gathering product requirements for early feature planning is best done through a guided interview that extracts problem statements, goals, constraints, and deliverables into a structured definition document.

Structuring feature scope and acceptance criteria during product discovery involves refining problem statements and task breakdowns through an interactive interview to ensure scoped, branch-free workflow outputs.

Yes, you can output a feature definition file by completing an interactive interview that writes a temporary structured markdown file to your tmp directory, ready for downstream setup workflows to consume.

No, feature definition does not require existing documentation scaffolding because it enforces a scoped, branch-free workflow by avoiding unnecessary scaffolding during the interview and planning process.