feature-dev-next

Feature development workflows for non-trivial features are structured using stage-driven processes that guide discovery, architecture planning, implementation, and review. This approach uses explicit user approvals before proceeding to implementation to ensure right-sized scoping.

Scoping feature development based on risk is best handled using three presets: Quick, Standard, and Deep. These presets fit the scope and risk of work from quick tweaks to complex modules, ensuring the workflow matches the complexity of the feature.

To log decisions during architecture planning for traceability, enable log mode within the feature development workflow. This automatically records decisions to the plans/ directory, capturing the reasoning needed for onboarding and future reference.

Yes, a stage-driven workflow can be used for both quick tweaks and complex modules by selecting the appropriate preset. The Quick preset handles minor adjustments while the Deep preset manages complex modules requiring full discovery and architecture planning.

Yes, feature development requires explicit user approvals to proceed to Stage 4, which is the implementation phase. This ensures that discovery and architecture planning are validated before coding begins, reducing risk in non-trivial features.