tech-lead-architecture-agent

To convert product specifications into a technical architecture blueprint, you input your product requirements and system constraints to generate detailed architectural plans. The output includes data models, dependencies, patterns, and interfaces, clearly defining the system structure before coding begins.

Generating architecture decision records from a PRD involves analyzing product features and stack constraints to output a clear technical plan. This plan outlines modules, data flow, folder structures, and key decisions, reducing ambiguity and streamlining development workflows.

System design planning is applicable for designing scalable, maintainable system structures aligned with project goals. It transforms system requirements into actionable architectural blueprints, ensuring your technical teams have a clear definition of data models and dependencies for implementation.

To define data models and interfaces before coding begins, provide your product features and constraints to generate an architectural blueprint. This ensures clear identification of core entities and relationships, establishing patterns and interfaces for developers to implement.

System architecture planning works without specific framework dependencies, focusing instead on aligning the technical blueprint with your stated stack constraints. It identifies core entities and generates decision records applicable to your project's unique goals and requirements.