analyse-design-gaps
SolidCompare two design inventories produced by inventory-design and emit a structured gap artefact whose prose paragraphs satisfy the extract-work-items cue-phrase contract. Use after running inventory-design for both a current and target design surface. The resulting gap artefact under meta/design-gaps/ feeds directly into /accelerator:extract-work-items to produce actionable work items.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- atomicinnovation
- Repository
- atomicinnovation/accelerator
- Created
- 5 months ago
- Last Updated
- today
- Language
- HTML
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
gap-analysis
This skill should be used when analyzing design documents, specifications, or plans for completeness gaps, architectural issues, security concerns, and performance implications. Provides focus-specific detection patterns for the designer agent.
gap-analysis
Performs a gap analysis between two artifacts (a current state and a desired state) and produces a plain-language, stakeholder-readable report indexed by stable gap IDs. Use when the user wants to compare, evaluate, audit, or reconcile one artifact against another. Does not investigate runtime bugs — use investigate. Does not assess module-level architecture — use architectural-analysis. Does not research open-ended options with no second artifact to compare against — use research.
extracting-design-md
Reverse-engineers a DESIGN.md (Google Labs format) from an already-built project and measures its design drift. Use whenever an existing codebase should adopt DESIGN.md, when UI values have multiplied (several grays, mixed radii, inconsistent buttons), when the owner says the UI looks inconsistent or "quedó desprolijo", or to re-audit drift after a migration batch — even if nobody says the word DESIGN.md.