cpm:architect

To generate Architecture Decision Records from a product brief, provide the brief as input and run the /cpm:architect command, which derives architecture decisions and outputs structured ADRs capturing context, options, and trade-offs.

Documenting architecture trade-offs and rationale is best achieved by creating Architecture Decision Records that explicitly capture context, evaluated options, and the decision rationale, ensuring traceability across the software architecture.

Yes, you can trace dependencies between architecture decisions; the system captures these dependencies during ADR generation, ensuring that interrelated decisions and their trade-offs remain visible and traceable throughout the architecture exploration process.

You need to create an Architecture Decision Record whenever you must derive architecture decisions from product needs and formally capture the context, options, trade-offs, and rationale to maintain traceability for your software product.

Generating ADRs requires no specific frameworks or dependencies; you simply provide a product brief or starting input and trigger the derivation and creation of architecture decisions via the /cpm:architect command.