kiro-validate-gap

Name: kiro-validate-gap
Availability: InStock
Author: miyamo2

Analyze gaps between requirements and an existing codebase to inform implementation planning.

Updated Jan 26, 2026

Search Tags:#design #documentation #research #codebase #requirements #analysis #gap-analysis

Ready to run

npx skills add https://github.com/miyamo2/braider --skill kiro-validate-gap-miyamo2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/miyamo2/braider/tree/main/.gemini/skills/kiro-validate-gap
Command: npx skills add https://github.com/miyamo2/braider --skill kiro-validate-gap-miyamo2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the gap between approved requirements and an existing codebase to inform implementation planning and design decisions.

Core Features & Use Cases

Load context: read specs, guidelines, and steering content to shape the gap analysis.
Identify gaps: surface missing capabilities, unknowns, risks, and constraints.
Output artifacts: generate a structured research document and actionable design inputs for the design phase.

Quick Start

Run the gap analysis against the target feature using the provided spec and repository context.

Frequently Asked Questions about kiro-validate-gap

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

FAQPage Schema

How do I analyze gaps between requirements and an existing codebase?▼

Gap analysis between requirements and a codebase involves loading specs and repository context to identify missing capabilities, unknowns, and risks, producing a structured research document for implementation planning.

What is feature-oriented gap analysis in software engineering?▼

Feature-oriented gap analysis is the structured process of comparing approved requirements against existing modules, architectures, and integrations to surface constraints and generate actionable design inputs.

How do I generate traceability documentation for missing codebase capabilities?▼

Generate traceability documentation by reading approved specs and steering content against the repository to identify missing capabilities, outputting a structured gap-analysis document with actionable findings.

When do I need a gap analysis for implementation planning?▼

You need a gap analysis for implementation planning when transitioning from approved requirements to design, requiring the identification of unknowns, constraints, and missing capabilities across target modules.

Can I use gap analysis to inform design decisions for new integrations?▼

Yes, gap analysis applies to feature-oriented assessments across modules and integrations, surfacing risks and constraints to produce actionable research items that directly inform downstream design decisions.

What limitations exist when analyzing codebase gaps against approved specs?▼

Limitations of codebase gap analysis include its dependency on accurate prerequisite specs and steering content; it produces research items and design inputs but does not directly execute code modifications or implement features.