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

kiro-discovery

Determine KiRO spec action paths from project state and planning artifacts.

Updated Apr 5, 2026
Search Tags:#planning#discovery#decision#roadmap#spec#kiro#boundary
One-click install
npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-discovery-shimamatz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-discovery
Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-discovery
Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-discovery-shimamatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Entry point for new work that determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

Core Features & Use Cases

  • Automates the initial scoping of KiRO spec work by assessing existing specs, steering documents, and the project roadmap to identify the correct boundary.
  • Guides decision-making about whether to extend an existing spec, create new specs, or decompose work into multiple specs, with questions to clarify user intent.
  • Produces actionable next steps and, when needed, just-in-time briefs and roadmaps to drive parallel spec creation.

Quick Start

Run discovery to determine the appropriate action path and generate a just-in-time roadmap and brief for new specs.

Frequently Asked Questions about kiro-discovery

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

FAQPage Schema
How do I decide whether to update an existing KiRO spec or create a new one?▼

Spec discovery evaluates existing spec inventories, steering documents, and roadmap context to determine the correct action path. It clarifies boundary questions to guide whether you should extend a current spec, create a new one, or decompose work into multiple specs.

What is the best way to scope new roadmap work before writing specs?▼

Guided discovery scopes new roadmap work by scanning existing planning artifacts to identify correct boundaries. It refines ideas through structured dialogue and outputs a concrete plan with recommended paths, next steps, and just-in-time briefs.

How do I decompose a large project into multiple KiRO specs?▼

Discovery determines work decomposition by assessing project state and existing planning artifacts to identify boundaries. It clarifies intent through dialogue and outputs just-in-time briefs and roadmap updates to drive parallel spec creation for large projects.

Do I need existing steering documents to plan a new spec?▼

Discovery scans existing steering documents and specs to determine the optimal action path. If steering documents are missing, it clarifies boundary questions with you directly to establish the correct path and generate a concrete plan.

When should I avoid automated spec discovery and plan manually?▼

Automated spec discovery is designed for new work entry where planning artifacts exist. If your work requires no spec or lacks planning artifacts entirely, the discovery process will determine that no spec is needed and output that path.

Related Skills

Explore More Product & Management Skills→
BarryYinBarryYin

kiro-discovery

Determine the correct action path for features or bugs using .kiro specs.

Community
Advanced
gaebalaigaebalai
8

kiro-discovery

Determine optimal action paths or work decomposition for new projects.

Community
Advanced
shimaMatzshimaMatz

kiro-spec-batch

Orchestrates automated spec generation for roadmap features via dependency waves.

Community
Advanced
snicmakinosnicmakino
2

kiro-discovery

Evaluate specs and steering inputs to recommend project action boundaries.

Community
Advanced