kiro-validate-gap
Analyze implementation gap between requirements and existing codebase
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- kiro-validate-gap
- metadata
- { "shared-rules": "gap-analysis.md" }
- description
- Analyze implementation gap between requirements and existing codebase
02 资源文件 1
- 参考文档agents/openai.yaml179 B
03 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
{{KIRO_DIR}}/specs/$1/spec.jsonfor language and metadata - Read
{{KIRO_DIR}}/specs/$1/requirements.mdfor 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
-
Read Analysis Guidelines:
- Read
rules/gap-analysis.mdfrom this skill's directory for comprehensive analysis framework
- Read
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
{{KIRO_DIR}}/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
- Save the gap analysis to
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 $1first 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 $1to create technical design document - Or
$kiro-spec-design $1 -yto auto-approve requirements and proceed directly
Note: Gap analysis is optional but recommended for brownfield projects to inform design decisions.
04 同仓库更多 Skills
kiro-spec-init
暂无简介
kiro-spec-init
暂无简介
sb-verify-completion
Consequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted.
sb-validate-implementation
Validate completed Tasks against active Requirement IDs and record completion on GO under an explicit lifecycle-validation request or ordinary Drive authority. Also owns completion withdrawal under an evidenced Drive replan recovery handoff. For a consequence-free claim check, use sb-verify-completion.
sb-validate-design
Independently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.
sb-steering
Maintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.