Author technical specification documents covering architecture overview, integrations, data flows, system limits, compliance posture, and non-functional requirements. Use when writing technical specs, documenting system architecture, cataloging integrations, defining compliance posture, or specifying system limits. Triggered by: technical specification, technical.md, architecture documentation, system limits, compliance posture, data flows, integrations, non-functional requirements.
Author technical.md files that document a product's architecture, integrations, data flows, system limits, and compliance posture. This document serves the engineering and security audiences — it answers "how is it built?" and "is it safe?"
Follow these steps when authoring a technical specification:
Read existing product context
product.yaml for canonical metadata (integrations, security_compliance)positioning.md for differentiated capabilities (often architecture-driven)technical.md to understand current stateDocument Architecture Overview
assets/ if availableDocument Integrations
Document Data Flows
[Source] → [Processing] → [Destination]Document System Limits
Complete the Compliance Matrix
./references/compliance-matrix.mdDocument Non-Functional Requirements
Write the file
products/<slug>/technical.mdproduct.yaml integrations and security_compliance fields to matchproduct.yaml fields when writing integrations and compliance sections