skills.rest
ken5scal
ken5scalCOMMUNITY
Explore all skills by this author →
Website𝕏@ken5scalGitHub

kiro-discovery

Determine project work scope by analyzing existing specs and user input.

Updated Aug 27, 2026
Search Tags:#planning#project management#specification#decomposition#scope definition
One-click install
npx skills add https://github.com/ken5scal/.allstar --skill kiro-discovery-ken5scal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-discovery
Source: https://github.com/ken5scal/.allstar/tree/main/.claude/skills/kiro-discovery
Command: npx skills add https://github.com/ken5scal/.allstar --skill kiro-discovery-ken5scal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users determine the optimal scope for new work within a project, ensuring clear boundaries and effective planning.

Core Features & Use Cases

  • Scope assessment: Analyzes existing specs, project context, and initial ideas to identify the appropriate work boundaries.
  • Discovery facilitation: Guides users through clarifying goals, responsibilities, and dependencies to inform structured decomposition.
  • Use Case: A product team wants to initiate a new feature but needs to clarify if it extends current specs or requires new ones; this Skill guides the assessment and planning.

Quick Start

Ask the AI to analyze your project and plan the scope for your new work item.

Frequently Asked Questions about kiro-discovery

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

FAQPage Schema
How do I define scope boundaries for a new feature before starting development?▼

Scope definition for a new feature requires analyzing existing specifications and project context to determine whether to extend current specs, create new ones, or decompose the work into multiple components.

What is the best way to decompose a large project into manageable development tasks?▼

Project decomposition breaks down initial ideas by guiding users through clarifying goals, responsibilities, and dependencies, resulting in a structured breakdown of work items for effective planning.

When do I need to create new specifications instead of extending existing ones?▼

You need new specifications when scope assessment reveals that the new work item boundaries do not align with existing project specs, requiring a fresh structured definition rather than an extension.

Can I use this approach for planning refactoring efforts and not just new feature development?▼

Yes, scope assessment and task decomposition apply directly to refactoring efforts, utilizing project metadata and initial input to identify appropriate work boundaries for restructuring existing code.

How does analyzing project metadata improve task decomposition?▼

Analyzing project metadata improves task decomposition by providing existing specs and contextual boundaries, which clarifies dependencies and informs the structured breakdown of new work components.

What are the limitations of automated scope definition for complex project planning?▼

Automated scope definition relies heavily on the quality of initial user input and existing specs; if project metadata is incomplete, the resulting work boundaries and task decomposition may lack accuracy.

Related Skills

Explore More Software Engineering Skills→
ibnuhalimmibnuhalimm

Architect

Gather project context and produce a detailed architecture plan.

Community
Advanced
FrkAkFrkAk
178

manage

Manage a project's context network and propagate task changes through downstream dependencies.

Community
Advanced
haidonglethqbhaidonglethqb

project-management

Coordinate multi-plan project management by synchronizing Claude Tasks with plan files.

Community
Advanced
asermaxasermax
1

retrofit-spec

Generate feature specifications from codebase structure and repository context.

Community
Advanced