Standardize technical design documents with templates and review checklists.
npx skills add https://github.com/jralph/.config-opencode --skill design-architect
Please help me install this Agent Skill. Skill: design-architect Source: https://github.com/jralph/.config-opencode/tree/main/skills/design-architect Command: npx skills add https://github.com/jralph/.config-opencode --skill design-architect
Design teams often produce inconsistent design documents, leading to miscommunication, rework, and missed requirements. This Skill defines a standardized approach to creating and reviewing technical design documents for software systems.
Create a new design document named design.md following the standard template, populate Overview, Architecture, Components and Interfaces, and Data Models, and then run through the design-review checklist.
High-intent search queries and answers about installing and using this skill.
Standardize technical design documents by applying a fixed template covering Overview, Architecture, Components, Interfaces, Data Models, and Validation criteria. This structured approach reduces ambiguity, ensures traceability of requirements, and aligns project designs with architectural principles.
A system design template should include sections for Overview, Architecture, Components and Interfaces, Data Models, and Validation criteria. Defining these components standardizes architecture definitions and component interactions to ensure completeness and clarity across software projects.
Conduct a design review by running through a standardized checklist that traces requirements directly to design elements. This guided review process ensures completeness, verifies alignment with architectural principles, and identifies missing requirements before implementation begins.
Yes, you can align project designs with enterprise architecture by using standardized templates and review workflows. This ensures technical decisions for systems like a payments service are documented clearly and adhere to established architectural principles across teams.
The best way to document component interactions and data models is by populating a standardized design document template. Specifying these sections ensures clear traceability of system architecture and reduces miscommunication during software development.
pradyumnasagarAutomate inter-skill data transfer and provenance capture via JSON Material Passports.
lookatitudeGenerate system design documents with components, data flows, and failure modes.
Weihong-LiuGenerate SVG architecture diagrams in HTML from system components and relationships.
CiabatosGenerate markdown architecture documents with Mermaid diagrams and code references.
