emerge/architecture-methodology
Enforces a 4-phase architecture design workflow by reading `.arch/state.json` on every request to gate responses by phase. Phase 1 extracts and validates requirements from PRDs; Phase 2 selects architecture patterns and establishes high-level structure; Phase 3 designs and accepts components sequentially; Phase 4 finalises and documents the solution. Use when discussing system design, solution architecture, PRD analysis, component design, technology selection, or architecture patterns — distinct from general coding help by its strict phase-gating, anti-pattern detection, and state-tracked component acceptance.
93
97%
Does it follow best practices?
Impact
89%
1.07xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers all evaluation dimensions. It provides specific actions for each of 4 phases, includes natural trigger terms architects would use, explicitly states when to use it, and clearly differentiates itself from general coding assistance. The description is comprehensive without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions across 4 phases: 'extracts and validates requirements from PRDs', 'selects architecture patterns', 'designs and accepts components sequentially', 'finalises and documents the solution'. Also mentions specific mechanisms like 'reading .arch/state.json' and 'phase-gating'. | 3 / 3 |
Completeness | Clearly answers both what (4-phase workflow with specific actions per phase) AND when ('Use when discussing system design, solution architecture, PRD analysis...'). Includes explicit 'Use when...' clause with multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'system design', 'solution architecture', 'PRD analysis', 'component design', 'technology selection', 'architecture patterns'. These are terms developers naturally use when seeking architecture help. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from 'general coding help' and highlights unique characteristics: 'strict phase-gating', 'anti-pattern detection', 'state-tracked component acceptance', and the specific '.arch/state.json' mechanism. Clear niche in architecture design workflows. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent workflow clarity, concrete actionable guidance, and efficient token usage. The phase-gating mechanism is well-defined with explicit validation checklists and clear boundary enforcement. The main weakness is that all content is inline rather than using progressive disclosure to separate detailed reference material.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and structured lists to convey information. No unnecessary explanations of concepts Claude already knows; every section serves a clear purpose. | 3 / 3 |
Actionability | Provides concrete JSON state file structure, explicit acceptance commands (/accept or ACCEPT), specific checklists for phase transitions, and exact redirect phrases for boundary enforcement. Highly executable guidance. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear phase sequencing, explicit validation checklists before each transition, and feedback loops (redirect patterns when out-of-phase). The 'Before Every Architecture-Related Response' section establishes a clear validation checkpoint. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic file with no references to external documentation. For a skill of this complexity, splitting anti-patterns, phase details, or examples into separate files would improve navigation. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents