skills.rest
shimaMatz
shimaMatzCOMMUNITY
Explore all skills by this author →
GitHub

kiro-validate-gap

Document gaps between approved requirements and codebase analysis in research.md.

Updated Apr 5, 2026
Search Tags:#design#architecture#codebase#requirements#analysis#gap-analysis
One-click install
npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-validate-gap-shimamatz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-validate-gap
Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-validate-gap-shimamatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify and document gaps between approved requirements and the current codebase, enabling informed design decisions and smoother implementation planning.

Core Features & Use Cases

  • Gap discovery by comparing specs, requirements, and steering context to surface missing capabilities, dependencies, and integration points.
  • Risk-focused recommendations with multiple viable implementation approaches to inform design discussions.
  • Formal research artifact generation by writing findings to .kiro/specs/$1/research.md to guide design and planning.

Quick Start

Provide the feature id to run the gap analysis and review the generated research at .kiro/specs/$1/research.md

Frequently Asked Questions about kiro-validate-gap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify gaps between approved requirements and my current codebase?▼

Gap analysis compares approved requirements and steering context against the current codebase to surface missing capabilities, dependencies, and integration points. It generates a formal research artifact to guide design discussions and implementation planning.

What is the best way to document missing capabilities for feature-level architecture review?▼

Documenting missing capabilities requires a gap-analysis framework that reads spec.json and requirements.md, then writes risk-focused recommendations with multiple viable implementation approaches to a research.md file for planning.

How do I generate a research artifact to guide implementation planning from feature specs?▼

Provide a feature id to run gap analysis and the skill writes findings to .kiro/specs/$1/research.md. This artifact captures missing capabilities, dependencies, and integration points to inform design decisions.

Can I use gap analysis for risk assessment across codebases, specs, and steering context?▼

Yes, gap analysis applies to feature-level analysis, architecture review, and risk assessment across codebases, specs, and steering context. It surfaces missing dependencies and integration points to enable informed design decisions.

What format do I need to provide for gap analysis to process my feature requirements?▼

Gap analysis requires approved requirements in .kiro/specs/$1/spec.json and .kiro/specs/$1/requirements.md. It reads these files to compare against the codebase and generate findings in research.md.

Why does gap analysis require a steering context when reviewing codebase architecture?▼

Steering context provides the broader architectural guidelines and constraints needed to accurately surface missing capabilities and integration points during gap analysis, ensuring implementation approaches align with approved design decisions.

Related Skills

Explore More Software Engineering Skills→
taku-otaku-o
1

kiro-spec-requirements

Generate EARS-format requirements drafts from project specs and steering files.

Community
Advanced
novel-jpnovel-jp

design-review

Review design and implementation plans for architectural soundness and delivery risk.

Official
Intermediate
Lira-tronLira-tron
4

generate-steering

Generate product.md, tech.md, and structure.md from codebase analysis.

Community
Advanced
valec3valec3
1

jira-task

Create Jira tasks with standardized titles, descriptions, acceptance criteria, and references.

Community
Basic