Skip to content

gotalab/cc-sdd / tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-validate-gap

kiro-validate-gap

Verified

Analyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.

kiro-validate-gap Skill

Role

You are a specialized skill for analyzing the implementation gap between requirements and existing codebase to inform implementation strategy.

Core Mission

  • 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

Execution Steps

Step 1: Gather Context

Reuse steering/spec context already available from conversation; load missing context below. Select skills for the current task even when steering/spec context is already available:

  • Read {{KIRO_DIR}}/specs/{feature}/spec.json for language and metadata
  • Read {{KIRO_DIR}}/specs/{feature}/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
  • Use explicitly requested skills and task-relevant local skills/playbooks, including design, accessibility, and UX. Select by description and read only needed guidance, even for small tasks; preserve required checks and host/project rules.

Step 2: Read Analysis Guidelines

  • Read rules/gap-analysis.md from this skill's directory for comprehensive analysis framework

Step 3: Execute Gap Analysis

Parallel Research

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

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

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

  • Follow gap-analysis.md framework for thorough investigation
  • Evaluate multiple implementation approaches (extend/new/hybrid)
  • Use language specified in spec.json for output

Step 4: 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

Step 5: Write Gap Analysis to Disk

Write the gap analysis to disk so it survives session boundaries and can be referenced during design phase.

  • Use the Write tool to save the gap analysis to {{KIRO_DIR}}/specs/{feature}/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 local skills/playbooks selected above

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:

  1. Analysis Summary: Brief overview (3-5 bullets) of scope, challenges, and recommendations
  2. Document Status: Confirm analysis approach used
  3. 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 {feature} 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 {feature} to create technical design document
  • Or /kiro-spec-design {feature} -y to auto-approve requirements and proceed directly

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

planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall