studiogadgetstudiogadget/skills/kiro-validate-gap/SKILL.md

kiro-validate-gap

Skill3 starsChanged 6 months agoApache-2.0View on GitHub

Analyze implementation gap between requirements and existing codebase

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

aiproxer/aiproxeredited, first seen Nov 8, 2026
growilabs/growiedited, first seen Oct 8, 2026
kyuki3rain/cc-sdd-adredited, first seen Jul 27, 2026

Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
growilabs/growi★ 1.5k76% same
aiproxer/aiproxer★ 2297% same
kyuki3rain/cc-sdd-adr★ 076% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- cc-sdd-restack-after-mergeSkill
- cc-sdd-review-slice-stackSkill
- ci-stable-log-testingSkill
- create-issueSkill
- docker-deployment-guideSkill
- hibernate-pcSkill
- kiro-debugSkill
- kiro-discoverySkill
- kiro-implSkill
- kiro-reviewSkill
- kiro-spec-batchSkill
- kiro-spec-designSkill
- kiro-spec-initSkill
- kiro-spec-quickSkill
- kiro-spec-requirementsSkill
- kiro-spec-statusSkill
- kiro-spec-tasksSkill
- kiro-steering-customSkill
- kiro-steeringSkill
- kiro-validate-designSkill
- kiro-validate-implSkill
- kiro-verify-completionSkill
- notion-pdfSkill
- playwright-scraperSkill
- pptx-slides-creatorSkill
- pr-creatorSkill
- pytest-marksSkill
- python-readable-codeSkill
- resolve-pr-review-threadsSkill
- sec-diff-reviewSkill
- sec-full-scanSkill
- sec-runtime-scanSkill
- skill-creatorSkill
- storage-stateSkill

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. 9 are common, 2 are distinctive, and 9 are very specific to this project.

9
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read docs/specs/$1/spec.json for language and metadata
line 27
Very specific:
Read docs/specs/$1/requirements.md for requirements
line 28
Very specific:
Read rules/gap-analysis.md from this skill's directory for comprehensive analysis framework
line 34
Distinctive:
If multi-agent is enabled, spawn sub-agents for each area above.
line 43
Common:
After all parallel research completes, synthesize findings for gap analysis.
line 45
Common:
Follow gap-analysis.md framework for thorough investigation
line 48
Distinctive:
Use WebSearch/WebFetch for external dependency research if needed
line 50
Very specific:
Use language specified in spec.json for output
line 52
Common:
Create comprehensive gap analysis following the output guidelines in gap-analysis.md
line 55
Very specific:
If the file already exists, append the new analysis (separated by a horizontal rule ---) rather than overwriting previous research
line 64
Common:
Verify the file was written by reading it back
line 65
Common:
Thorough Investigation: Use tools to deeply understand existing codebase
line 70
Very specific:
Context Discipline: Start with core steering and expand only with analysis-relevant steering or use-case-aligned local agent …
line 72
Common:
Grep extensively: Search codebase for patterns, conventions, and integration points
line 77
Common:
Use Markdown headings for clarity
line 89
Common:
Keep summary concise (under 300 words)
line 90
Very specific:
Missing Requirements: If requirements.md doesn't exist, stop with message: "Run /kiro-spec-requirements $1 first to generate requirements"
line 96
Common:
Requirements Not Approved: If requirements not approved, warn user but proceed (gap analysis can inform requirement revisions)
line 97
Very specific:
Language Undefined: Default to English (en) if spec.json doesn't specify language
line 100
Very specific:
Run /kiro-spec-design $1 to create technical design document
line 106

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Implementation Gap Validation

<background_information>

Mission: Analyze the gap between requirements and existing codebase to inform implementation strategy
Success Criteria:
- Comprehensive understanding of existing codebase patterns and components
- Clear identification of missing capabilities and integration challenges
- Multiple viable implementation approaches evaluated
- Technical research needs identified for design phase </background_information>

<instructions>
## Core Task
Analyze implementation gap for feature **$1** based on approved requirements and existing codebase.

Execution Steps

Load Context:
- Read docs/specs/$1/spec.json for language and metadata
- Read docs/specs/$1/requirements.md for requirements
- Core steering context: product.md, tech.md, structure.md
- Additional steering files only when directly relevant to the feature's domain rules, integrations, runtime prerequisites, compliance/security constraints, or existing product boundaries
- Relevant local agent skills or playbooks only when they clearly match the feature's host environment or use case and provide analysis-relevant context
Read Analysis Guidelines:
- Read rules/gap-analysis.md from this skill's directory for comprehensive analysis framework

Parallel Research

The following research areas are independent and can be executed in parallel:

Codebase analysis: Existing implementations, architecture patterns, integration points, extension possibilities
External dependency research: Dependency compatibility, version constraints, known integration challenges (when needed)
Context loading: Requirements, core steering, task-relevant extra steering, relevant local agent skills/playbooks, and gap-analysis rules

If multi-agent is enabled, spawn sub-agents for each area above. Otherwise execute sequentially.

After all parallel research completes, synthesize findings for gap analysis.

Execute Gap Analysis:
- Follow gap-analysis.md framework for thorough investigation
- Analyze existing codebase using Grep and Read tools
- Use WebSearch/WebFetch for external dependency research if needed
- Evaluate multiple implementation approaches (extend/new/hybrid)
- Use language specified in spec.json for output
Generate Analysis Document:
- Create comprehensive gap analysis following the output guidelines in gap-analysis.md
- Present multiple viable options with trade-offs
- Flag areas requiring further research
Write Gap Analysis to Disk:
Write the gap analysis to disk so it survives session boundaries and can be referenced during design phase.
- Save the gap analysis to docs/specs/$1/research.md
- If the file already exists, append the new analysis (separated by a horizontal rule ---) rather than overwriting previous research
- Verify the file was written by reading it back

Important Constraints

Information over Decisions: Provide analysis and options, not final implementation choices
Multiple Options: Present viable alternatives when applicable
Thorough Investigation: Use tools to deeply understand existing codebase
Explicit Gaps: Clearly flag areas needing research or investigation
Context Discipline: Start with core steering and expand only with analysis-relevant steering or use-case-aligned local agent skills/playbooks</instructions>

Tool Guidance

Read first: Load spec, core steering, relevant local playbooks/agent skills, and rules before analysis
Grep extensively: Search codebase for patterns, conventions, and integration points
WebSearch/WebFetch: Research external dependencies and best practices when needed
Write last: Generate analysis only after complete investigation

Output Description

Provide output in the language specified in spec.json with:

Analysis Summary: Brief overview (3-5 bullets) of scope, challenges, and recommendations
Document Status: Confirm analysis approach used
Next Steps: Guide user on proceeding to design phase

Format Requirements:

Use Markdown headings for clarity
Keep summary concise (under 300 words)
Detailed analysis follows gap-analysis.md output guidelines

Safety & Fallback

Error Scenarios

Missing Requirements: If requirements.md doesn't exist, stop with message: "Run /kiro-spec-requirements $1 first to generate requirements"
Requirements Not Approved: If requirements not approved, warn user but proceed (gap analysis can inform requirement revisions)
Empty Steering Directory: Warn user that project context is missing and may affect analysis quality
Complex Integration Unclear: Flag for comprehensive research in design phase rather than blocking
Language Undefined: Default to English (en) if spec.json doesn't specify language

Next Phase: Design Generation

If Gap Analysis Complete:

Review gap analysis insights
Run /kiro-spec-design $1 to create technical design document
Or /kiro-spec-design $1 -y to auto-approve requirements and proceed directly

Note: Gap analysis is optional but recommended for brownfield projects to inform design decisions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free