Review architecture specifications for completeness, abstraction, and separation of concerns.
npx skills add https://github.com/igor1309/skills --skill arch-spec-review
Please help me install this Agent Skill. Skill: arch-spec-review Source: https://github.com/igor1309/skills/tree/main/arch-spec-review Command: npx skills add https://github.com/igor1309/skills --skill arch-spec-review
Architecture documents often drift into implementation details, omit clear boundaries, or fail to state constraints and extension points, making them hard to review and evolve; this Skill helps reviewers keep specifications at the right level of abstraction and identify genuine architectural gaps.
Review the attached architecture document for clear component responsibilities, end-to-end flows, stated constraints, extension points, and any improperly specified implementation details.
High-intent search queries and answers about installing and using this skill.
To review an architecture spec, evaluate component boundaries, end-to-end flows, and constraints while identifying over-specification. This ensures the document maintains appropriate abstraction and separation of concerns without drifting into implementation details.
Abstraction discipline in architecture documentation ensures specs define "who" and "what" rather than "how". It highlights when a document improperly requests implementation details, keeping the focus on architectural boundaries and component responsibilities.
Check an architecture document for completeness by verifying stated constraints, extension points, error handling boundaries, and deferred decisions. This validates that primary flows and component responsibilities are clear before starting implementation planning.
Yes, this architecture spec review identifies missing flows and ambiguous responsibilities. It evaluates top-level, implementation-agnostic documents to find genuine architectural gaps and produces focused recommendations on architectural concerns.
You should not use an architecture spec review for detailed implementation planning or low-level design docs. It targets top-level, implementation-agnostic architecture documents and separates architectural questions from specific technology or implementation requests.
The best way to separate architectural questions from implementation requests is to apply a structured review that identifies over-specification. This produces focused findings that isolate genuine architectural gaps from improperly specified implementation details.
luanrodriguesCreate technology-agnostic technical architecture documents defining patterns, boundaries, and data flows.
oduffy-delphiProduce detailed implementation plans with tasks, dependencies, and artifacts.
ConsiliencyGenerate standardized C4 architecture diagrams using Mermaid syntax.
edpagetReview code changes against architectural principles and detect semantic violations.