kiro-discovery

Determine optimal action paths and work decomposition for new initiatives.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-discovery-taku-o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-discovery
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-discovery
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-discovery-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Entry point for new work. 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

  • Guides teams to decide whether to update an existing spec, create a new spec, or perform a mixed decomposition of work.
  • Uses structured dialogue to surface intent, questions, and constraints, reducing back-and-forth and rework.
  • Outputs actionable next steps and boundary definitions that feed into subsequent specification work.

Quick Start

Provide your initial idea or request, and kiro-discovery will outline the optimal action path and clarifying questions.

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 specification or create a new one for new work initiatives?

New work discovery guides you through structured dialogue to determine the optimal action path, evaluating whether to update an existing specification, create a new one, or perform mixed decomposition based on your intent and constraints.

What is the best way to decompose complex new initiatives into actionable steps?

Work decomposition identifies the optimal action path for new initiatives by clarifying intent through structured questions, outputting actionable next steps with clearly defined boundaries and dependencies to guide subsequent specification work.

How does structured dialogue help with planning and discovering new work directions?

Structured dialogue surfaces intent, questions, and constraints during discovery, reducing back-and-forth and rework by refining ideas into an actionable next step with clear boundary definitions for specification work.

Can I use workflow discovery to refine vague ideas into actionable specifications?

Yes, workflow discovery takes your initial idea or request and refines it through structured dialogue and clarifying questions, outputting an actionable next step with defined boundaries to feed into subsequent specification work.

When do I need specification discovery before starting a new project workflow?

You need specification discovery as an entry point for new work to identify the optimal action path and work decomposition, ensuring ideas are refined and boundaries are defined before subsequent specification work begins.

What are the limitations of using discovery dialogue for work decomposition?

Discovery dialogue focuses on determining the action path and boundary definitions for new work; it does not generate the full specification itself, but rather outputs the actionable next step and dependencies to guide subsequent specification work.