跳到正文
cccskills
免费在 GitHub 公开

kiro-validate-gap

Compare feature requirements with existing code to identify missing capabilities and integration challenges. Evaluate extending current components, building new ones, or combining both, and save the findings to guide technical design.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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

gotalab/cc-sdd
查看安装方法

适用场景

  • Planning a new feature in an existing system
  • Comparing component reuse with new development
  • Identifying integration questions before design
  • Saving research findings for the design phase

包含的文件（1）

  • SKILL.md5.6 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护，适用 Google 的隐私权政策和服务条款。

同一仓库的技能

cc-sdd-new-agent

免费

Add coding-agent support to cc-sdd through a documented workflow. Research the agent’s official formats, prepare an integration plan, implement registry entries and templates, and verify generated files, including Japanese and English output.

中文简介正在准备中。当前显示英语简介。

  • Adding support for a new coding agent
  • Adding an agent variant with subagent support
  • Planning migration to SKILL.md-based templates
gotalab/cc-sdd37302026年10月13日 更新

kiro-debug

免费

Investigate blocked implementation work and recurring failures using error output, code changes, configuration, and dependency evidence. Get a root cause report with a focused repair plan, verification steps, and a recommendation to retry, block, or seek human input.

中文简介正在准备中。当前显示英语简介。

  • Investigating an implementation blocker
  • Finding why repeated fixes keep failing
  • Checking runtime and dependency conflicts
gotalab/cc-sdd37302026年10月13日 更新

kiro-discovery

免费

Clarify a development request through structured questions and choose a practical next step: update an existing specification, create new ones, or implement directly. For new specifications, record scope, approach, and dependencies in planning files.

中文简介正在准备中。当前显示英语简介。

  • Clarify a development idea before defining requirements
  • Choose between updating a specification and implementing directly
  • Split a large request into features with explicit dependencies
gotalab/cc-sdd37302026年10月13日 更新

kiro-impl

免费

Implement approved development tasks one at a time using test-driven development, which starts with a failing test. Process all pending tasks or selected ones, check changes against requirements and design, and update progress after review and completion verification.

中文简介正在准备中。当前显示英语简介。

  • Working through all approved pending tasks
  • Implementing selected task numbers
  • Developing features with tests written first
gotalab/cc-sdd37302026年10月13日 更新

kiro-impl

免费

Implement approved tasks through test-driven development, writing tests before code. Run all pending tasks sequentially with subagents or select tasks for direct execution, then track completion using reviews and verification evidence.

中文简介正在准备中。当前显示英语简介。

  • Running all pending approved implementation tasks
  • Implementing selected tasks by number
  • Developing features with tests written first
gotalab/cc-sdd37302026年10月13日 更新

kiro-impl

免费

Implement approved tasks using test-driven development, writing tests before code. Run all pending tasks one at a time or select specific tasks, with configurable review and verification before updating completion status.

中文简介正在准备中。当前显示英语简介。

  • Implement all pending tasks from an approved plan
  • Work on selected task numbers
  • Develop features by writing tests before code
gotalab/cc-sdd37302026年10月13日 更新

查看 gotalab 的全部技能

报告此技能的问题