feature-dev

Feature implementation planning requires early requirements clarification, parallel codebase analysis to map architecture, and explicit user confirmation before design. This approach surfaces ambiguities and identifies relevant files to ensure changes fit existing conventions.

To safely add a new feature, use parallel codebase investigation to map architecture and find relevant patterns. Compare implementation approaches and request explicit approval before coding to ensure the new feature respects existing conventions.

Requirements clarification involves surfacing ambiguities, edge cases, constraints, and success criteria before implementation starts. This forces early understanding of the underspecified feature idea, preventing costly rework during the actual coding phase.

Yes, code review is essential for major refactors. A structured approach uses parallel sub-agent analysis to explore the codebase, compares implementation approaches, and finishes with a final quality review to verify the refactor meets success criteria.

Architecture review is needed for new features, major enhancements, and complex changes requiring phased implementation. It ensures the planned change fits existing conventions by mapping relevant patterns and identifying the files that matter most.

Yes, feature development works for underspecified ideas by forcing early clarification of constraints and success criteria. It transforms vague concepts into well-planned changes through codebase exploration and careful review before any coding begins.