kiro-discovery

Determine the optimal action path for new work items from project state.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/notta50/korenani --skill kiro-discovery-notta50
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-discovery
Source: https://github.com/notta50/korenani/tree/main/.claude/skills/kiro-discovery
Command: npx skills add https://github.com/notta50/korenani --skill kiro-discovery-notta50

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

kiro-discovery helps teams determine the optimal action path for a new work item by selecting between updating an existing spec, creating a new spec, performing a mixed decomposition, or opting for no new spec, based on current project state.

Core Features & Use Cases

  • Determines the best action path (update an existing spec, create a new spec, mixed decomposition, or none) from the current project state.
  • Guides structured dialogue to clarify user intent and avoid assumptions.
  • Outputs an actionable next step for downstream work such as spec initialization or tasking.

Quick Start

Provide your idea to kiro-discovery to receive the recommended action path.

Frequently Asked Questions about kiro-discovery

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

FAQPage Schema
How do I determine the best action path for a new work item in project planning?

To determine the action path for a new work item, evaluate the current project state to select between updating an existing spec, creating a new spec, or performing a mixed decomposition. This prevents assumptions by guiding structured dialogue for early-stage discovery.

When do I need to update an existing spec versus create a new spec during discovery?

You need to update an existing spec when the new work item fits current roadmap boundaries, whereas creating a new spec is required for standalone ideas. Action path determination depends on metadata gathering and context loading from the current project state.

What is mixed decomposition in early-stage product discovery?

Mixed decomposition in product discovery is an action path that splits a new work item by updating existing specs while simultaneously creating new ones. It is selected when project state analysis shows the work item crosses multiple boundaries requiring both actions.

How do I gather metadata and context for roadmap planning and spec initialization?

You gather metadata and context for roadmap planning through a disciplined workflow of metadata gathering, action-path determination, and boundary questioning. This structured dialogue clarifies user intent and outputs an actionable next step for spec initialization.

Can I skip spec creation if my new work item does not require roadmap changes?

You can skip spec creation by selecting the no new spec action path. This occurs during early-stage discovery when boundary questioning determines the work item requires no changes to the current project state or roadmap guidance.