starting-a-new-feat

To scope a new feature request, validate the project state, elicit actors and requirements, and establish stable acceptance criteria to prevent premature implementation and ensure properly scoped feature definitions.

You should do a Phase 0 Discovery for larger greenfield projects with multiple anticipated features or personas to properly identify requirements before creating new feature definitions.

To decide between creating a new feature or extending an existing one, evaluate project state, elicit requirements, and route through the appropriate pipeline to distinguish a genuinely new feature from a user story.

The SDDPro feature pipeline directs feature requests to appropriate feature-generation, validation, user-story, or end-to-end workflows while blocking unjustified direct implementation.

No, feature planning applies to both greenfield projects and existing SDDPro projects, requiring project-state validation to identify existing features before work begins.

Blocking premature implementation ensures new feature requests are properly discovered, scoped, and routed through the development pipeline, preventing unstable acceptance criteria and misaligned user stories.