Draft ADRs and evaluate technology trade-offs across service boundaries.
npx skills add https://github.com/Adelie-Squad/solosquad --skill architect-adelie-squad
Please help me install this Agent Skill. Skill: architect Source: https://github.com/Adelie-Squad/solosquad/tree/main/agents/specialists/architect Command: npx skills add https://github.com/Adelie-Squad/solosquad --skill architect-adelie-squad
Architectural decisions and cross-service design often drift without a structured approach. This Skill provides a centralized framework to draft ADRs, define system boundaries, and evaluate technology trade-offs with collaboration prompts.
Draft an ADR for your upcoming service boundary change and use it to align engineering and product decisions.
High-intent search queries and answers about installing and using this skill.
To draft an ADR for splitting a monolith, define service boundaries, evaluate technology trade-offs, and capture the context, options, and consequences of the decision. This structured approach ensures coherent architecture and aligns engineering with product decisions.
Defining service boundaries and data ownership requires cross-service system design coordination to ensure coherent architecture. By applying structured governance and explicit gate checks, multiple teams can delineate scalability considerations and maintain clear data ownership.
You need formal architecture governance for system design when managing large-scale software projects that require service boundaries, technology choices, and trade-off evaluations across multiple teams. It prevents architectural drift by applying explicit gate checks and collaboration prompts.
Trade-off analysis for reference architecture patterns evaluates different technology choices and system boundaries to guide technical decisions. It provides a centralized framework to compare options, assess scalability considerations, and capture the consequences within an ADR.
Yes, this is explicitly designed for large-scale software projects requiring cross-service coordination. It applies to environments needing service boundary definition, technology choices, and trade-off evaluations across multiple teams to ensure a coherent architecture.
HechaoYannetGenerate a master architecture document from GDDs, ADRs, and governance constraints.
cenconq25Transform approved PRDs and architecture into Epic artifacts with TR-ID grouping.
raybirdRename, extract, and split code symbols using GitNexus CLI graph analysis.
ChaiWithJaiCreate Architecture Decision Records with standardized sections for context, constraints, options, decisions, and consequences.
