feature-dev

Feature implementation in an existing codebase follows a 7-phase workflow: Discovery, Explore, Clarify, Design, Implement, Review, and Summary. This structured approach reads project configuration and explores existing code to ensure new features match current architecture and coding standards.

Adding features to a software project with an unknown tech stack requires a tech-agnostic approach. The workflow discovers the existing framework, database, and architecture by reading configuration files and using sub-agents for codebase exploration, adapting implementation dynamically without prior assumptions.

Agile development workflows are supported through a structured feature development process. It guides teams sequentially through discovery, clarification, design, implementation, and review phases, ensuring requirements are met while maintaining main conversation context throughout the coding workflow.

Feature development works with any framework and database because it is tech stack agnostic. It reads existing project configuration and adapts to the established architecture, utilizing sub-agents to explore the codebase and ensure the new implementation aligns with current patterns.

Codebase exploration matters because it identifies existing framework patterns and architecture before coding begins. Using sub-agents to explore the project ensures the new feature implementation remains consistent with current coding standards and integrates seamlessly into the established software project.

Structured feature implementation workflows require clear project configuration files to discover architecture patterns. If the existing software project lacks documentation or standard configurations, the tech-agnostic adaptation may struggle to maintain codebase consistency during the implementation phase.