kiro-discovery

Identify discovery paths and decompose project work into spec boundaries.

Updated Feb 25, 2024
One-click install
npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-discovery-ryowatanabe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-discovery
Source: https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper/tree/main/.claude/skills/kiro-discovery
Command: npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-discovery-ryowatanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify the appropriate discovery path and decompose work into clear spec boundaries for a project.

Core Features & Use Cases

  • Determines the optimal action path (existing spec extension vs new spec) and guides stakeholders
  • Produces a concrete boundary and roadmap for downstream work
  • Supports iterative dialogue to refine ideas and avoid premature commitments

Quick Start

Describe the best action path or work decomposition for a new project and outline the next steps.

Frequently Asked Questions about kiro-discovery

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

FAQPage Schema
How do I decompose work into clear spec boundaries for a new project with unclear scope?▼

To decompose work into clear spec boundaries for a new project, you must first identify the appropriate discovery path. This structured process defines action paths, enforces boundary identification, and generates a just-in-time brief to guide downstream spec work.

When should I extend an existing spec versus creating a new spec for project planning?▼

You should extend an existing spec versus creating a new spec by evaluating action paths during initial project discovery. This evaluation determines the optimal extension or creation route, producing a concrete boundary and roadmap that avoids premature commitments through iterative dialogue.

What is the best way to identify the appropriate discovery path for project management initiatives?▼

The best way to identify the appropriate discovery path for project management initiatives is to apply structured discovery steps. This mechanism clarifies action paths and decomposes work into boundaries, generating a just-in-time brief or roadmap for downstream work.

Can I use iterative dialogue to refine project scope and avoid premature commitments during discovery?▼

Yes, you can use iterative dialogue to refine project scope and avoid premature commitments during discovery. This process supports ongoing refinement to determine the optimal action path and produces a concrete boundary and roadmap for downstream work.

How do I generate a just-in-time brief or roadmap to guide downstream spec work?▼

You generate a just-in-time brief or roadmap to guide downstream spec work by enforcing structured discovery steps and boundary identification. This approach clarifies action paths for a project and outputs the roadmap needed for subsequent tasks.

What are the limitations of using structured discovery steps for work decomposition in AI-agent project management?▼

Structured discovery steps for work decomposition in AI-agent project management are applied when starting new initiatives with unclear scope or multiple potential specs. They enforce boundary identification but may require iterative dialogue to refine ideas before generating a just-in-time brief.