build-feature

To turn a vague feature request into a ready feature plan, provide an initial brief. The system applies an intake questionnaire to surface decisions, assumptions, and blockers, producing a decision-complete plan ready for handoff.

A decision-complete feature plan is a concrete output detailing scope boundaries, affected routes, data changes, and rollout considerations. It ensures engineers can implement without guessing or needing further alignment.

Scoping a feature spanning UI, backend, data, or integrations requires clarifying boundaries. A structured intake process consolidates system compatibility guardrails and rollout criteria into a decision-ready plan.

Yes, the feature planning process captures assumptions and blockers. The consolidated intake questionnaire specifically surfaces these elements alongside decisions and scope boundaries to ensure alignment before implementation begins.

Yes, you can use this for product roadmap planning and feature intake. It translates vague requests into structured plans by defining scope boundaries, affected data changes, and rollout considerations to align with roadmap decisions.