architect

An implementation plan is generated by analyzing feature requirements, resolving ambiguities through clarifying questions, and mapping the design to project architecture. This approach ensures reuse-first design and explicit documentation of trade-offs before coding begins.

Requirements analysis for architecture planning involves asking clarifying questions and performing boundary checks to resolve ambiguities. This process produces a detailed plan that satisfies prior-art review and documents decisions for future work.

Ambiguities are resolved by generating clarifying questions and performing boundary checks during the requirement analysis phase. This ensures the implementation plan is fully aligned with the project architecture before development starts.

Architecture planning is needed when implementing features across multiple domains that require a detailed plan. It applies prior-art review, reuse-first design, and explicit plan documentation to align the implementation with project architecture.

Requirement analysis applies to features requiring architecture planning across multiple domains. It generates a comprehensive implementation plan that includes clarifying questions, boundary checks, and documented trade-offs.

A prior-art review is performed to support a reuse-first design approach during architecture planning. It ensures the implementation plan leverages existing project architecture and documents decisions and trade-offs for future work.