kiro-validate-gap

Analyze gaps between requirements and codebase to produce structured implementation options.

1.5k|242|Updated Feb 16, 2017
One-click install
npx skills add https://github.com/growilabs/growi --skill kiro-validate-gap-growilabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/growilabs/growi/tree/main/.claude/skills/kiro-validate-gap
Command: npx skills add https://github.com/growilabs/growi --skill kiro-validate-gap-growilabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes the gap between project requirements and the current codebase to guide implementation strategy and design planning.

Core Features & Use Cases

  • Gap discovery: identify missing capabilities, inconsistencies, and risks relative to the stated requirements.
  • Multi-option analysis: evaluate approaches (extend, create, hybrid) with trade-offs and effort estimates.
  • Research-driven planning: produce a structured gap-analysis document and recommendations for design.

Quick Start

Run the gap-analysis workflow after loading the feature spec and steering context.

Frequently Asked Questions about kiro-validate-gap

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

FAQPage Schema
What is gap analysis between requirements and an existing codebase?

Gap analysis identifies missing capabilities, inconsistencies, and risks in the current codebase relative to stated requirements. It evaluates approaches like extending, creating, or hybridizing components to produce a structured implementation strategy.

How do I analyze my codebase against feature specs to plan implementation?

Load your feature spec and steering context to run a gap-analysis workflow. This produces a structured document evaluating multiple implementation approaches with trade-offs and effort estimates to guide your design planning.

When do I need to perform a gap analysis for software architecture?

Perform gap analysis when bridging the gap between updated requirements and your current codebase. Use it to discover missing capabilities and inform your implementation strategy before beginning design planning.

What is the best way to evaluate implementation options for new requirements?

Use a structured gap-analysis approach to evaluate extending, creating, or hybrid approaches. It compares trade-offs and effort estimates against your current codebase to recommend the most suitable implementation strategy.

What do I need to load before running a codebase gap analysis?

You need to load necessary feature specs and steering context before performing the analysis. These inputs allow the workflow to identify gaps and produce research-driven recommendations for your design.