architect-feature

To plan feature architecture before coding, use an interactive session to clarify requirements, surface blockers, and produce a concrete architecture plan aligned with your codebase constraints. This collaborative process reveals implementation implications early.

Collaborative feature design is an interactive process that analyzes your codebase to validate architecture decisions. It asks targeted questions, logs decisions, and generates artifacts like requirements lists and architecture plans to align stakeholders before development.

You need to validate architecture for a new feature early in development, right after feature initiation. Applying this process early surfaces blockers, reveals codebase implications, and ensures the design is sound and scalable before implementation begins.

Yes, interactive architecture planning supports complex codebase analysis by guiding you through requirement clarification and constraint satisfaction. It produces concrete deliverables through interactive exploration, ensuring your feature design handles architectural complexity.

The best way to surface blockers during feature design is through an interactive architecture session that examines your codebase and asks clarifying questions. This collaborative approach reveals implications and constraints, producing a concrete plan that addresses potential blockers early.

Guided architecture planning sessions require active participation to answer prompts and provide codebase context. The quality of deliverables depends on accurate requirement inputs, and the process focuses on planning rather than generating implementation code.