Technical Design Creator

Creates technical design documents that communicate architecture decisions, system structure, and key trade-offs. The output defines what to build and how it is structured — not how to execute the work step by step.

Core Principle: Architecture Over Implementation

Before adding any detail, ask: "If we change frameworks or libraries, does this still apply?"

• YES → include it (architectural decision)
• NO → exclude it (implementation detail)

Include: API contracts, data schemas, component diagrams, technology choices with rationale, event/log schemas, integration boundaries.

Exclude: CLI commands, code snippets, framework-specific syntax, file paths, tool-specific configuration.

The technical design must survive implementation changes. If the team migrates ORMs or rewrites a service, the design doc should remain valid.

Routing