analyse-design-gaps
SolidCompare two design inventories produced by inventory-design and emit a structured gap artifact 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 artifact under meta/design-gaps/ feeds directly into /accelerator:extract-work-items to produce actionable work items.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- atomicinnovation
- Repository
- atomicinnovation/accelerator
- Created
- 2 months ago
- Last Updated
- today
- Language
- HTML
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
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 — including spec-vs-implementation gaps, PRD-vs-shipped-feature gaps, design-vs-build gaps, requirements-vs-code audits, or any "what's missing from X compared to Y" question — and wants a human-readable report rather than raw analyst output. Orchestrates the `gap-analyzer` agent for the primary analysis, then runs a validator-and- augmenter swarm by default to corroborate, contradict, and enrich the findings — including an actor-perspective sweep across human users, API callers, AI agents, and other actor types. The user may opt out of the swarm with `no swarm` to fall back to a lightweight gap-analyzer-only pass. Recommends a swarm team size (small / medium / large) based on gap count, gap-category distribution, and the specific domains the gaps t
kiro-validate-gap
Analyze implementation gap between requirements and existing codebase
harness-audit
Scans a project for agent-harness gaps and outputs a prioritised list with paste-ready config snippets to close them. Covers hooks, CI, pre-commit, instruction file quality, init.sh, and session discipline. Use when starting a new project, auditing an existing harness, writing or reviewing CLAUDE.md/AGENTS.md, setting up CI gates, beginning multi-day autonomous work, or when user says "set up harness", "health check", "agent discipline", "project setup", "pre-commit hooks", "stop hook", "verification gap".