feature-development

End-to-end feature development is coordinated through a seven-phase workflow covering discovery, architecture, implementation, review, and documentation. This enforces structured change management and phase-specific guidance to standardize building new capabilities across codebases.

Standardizing architecture decisions during feature development relies on architecture-aware guidance that aligns design choices with system constraints. The workflow mandates documentation steps, producing ADRs and specs to ensure traceability across teams.

Documentation and changelogs for a new feature workflow are generated through a documentation-centric closure phase. This mandatory step produces changelogs, architecture decision records, and specifications to validate the release and ensure traceability.

A phase-driven workflow supports exploring and discovering new codebase features through its initial discovery and exploration phases. It guides teams from the initial idea through architecture and implementation to release, ensuring structured change management.

The seven phases target projects requiring discovery, architecture, implementation, and documentation across multiple stages. Small codebase changes might not need the full workflow, as the process enforces mandatory documentation steps and structured change management suited for new capabilities.