architecture-decision-records
Creates, reviews, updates, and manages Architecture Decision Records (ADRs) — the institutional memory of technical decision-making. Use this skill whenever the user wants to: create an ADR for a technology or architecture decision, document why a specific technology was chosen, record a technical decision before implementing it, update or supersede an existing ADR, review a proposed decision for completeness, check whether a decision warrants an ADR, maintain the ADR index, or understand why a past decision was made. Also trigger when the user asks "why are we using X", "who decided this", "was this decision documented", "log a design decision", "decision history", "record a technical decision", or "document this choice".
Repository SourceNeeds Review
architecture-review-governance
Defines architecture principles, catches design problems before code is written, and detects drift as delivery proceeds. Use this skill whenever the user wants to: review a system design or architecture proposal, evaluate trade-offs between technical approaches (microservices vs monolith, sync vs async, edge vs cloud), identify architectural anti-patterns or hidden coupling, enforce service and component boundaries, review integration design or data flow, validate non-functional requirements, detect architecture drift, or self-review a design before presenting it to the team. Also trigger when the user asks "is this the right approach", "what are the trade-offs", or "does this architecture scale".
Repository SourceNeeds Review
data-governance-privacy
Activate when classifying data (PII, sensitive, internal, public), running a Privacy Impact Assessment (PIA/DPIA), defining retention or deletion policies, designing GDPR/CCPA compliance workflows, handling subject access requests (SAR) or right-to-erasure, evaluating cross-border data transfers (EU SCCs, adequacy decisions), scoping data minimisation, reviewing new third-party data sharing, or assessing EU AI Act Article 10/13 data transparency obligations for an ML/LLM feature that trains on user data. Use before a feature that collects, stores, shares, or trains on user data is shipped.
Repository SourceNeeds Review
design-doc-generator
Activate when the user wants to produce a technical design document from existing requirements, specifications, or a PRD. Use this skill to convert the outputs of prd-creator, requirements-tracer, specification-driven-development, and architecture-decision-records into a single, implementation-ready DESIGN.md that engineers can build from. Also trigger for: "write the design doc", "technical design", "system design", "how should we build this", "design document", "architecture doc", "translate specs to design", "what does the implementation look like", "design from requirements", "component design", "data flow design", "turn the PRD into a design".
Repository SourceNeeds Review