Technical Architecture (TRD) Architect FAQs

Question 1

How does the skill handle different programming languages?

Accepted Answer

It includes an auto-detection step that looks for files like go.mod or package.json to load language-specific engineering standards while still keeping the architectural design abstract.

Question 2

What is the purpose of the TRD creation skill?

Accepted Answer

The TRD (Technical Requirement Document) skill ensures that system architecture is defined by patterns and capabilities (the 'How' and 'Where') before developers commit to specific technologies or libraries.

Question 3

When should I trigger this skill in my workflow?

Accepted Answer

It should be triggered as Gate 3, after the PRD (Gate 1) and Feature Map (Gate 2) are validated, but before starting API design or task breakdown.

Question 4

Why does this skill forbid mentioning specific products like PostgreSQL?

Accepted Answer

To prevent premature optimization and vendor lock-in. Architecture should focus on capabilities (e.g., 'Relational Database') so that implementation choices can be evaluated based on the full dependency analysis in later stages.

Question 5

What are the 'Red Flags' in TRD creation?

Accepted Answer

Red flags include specific version numbers, cloud provider service names (like AWS RDS), package manager commands, and framework-specific terms that couple the architecture to a single implementation.

Technical Architecture (TRD) Architect

Technical Architecture (TRD) Architect

Key Features

Use Cases

Key Features

Use Cases