skills.rest
scapia-oss
scapia-ossOFFICIAL
Explore all skills by this author →
WebsiteGitHub

kiro-spec-quick

Generates right-sized spec documents by classifying changes into minimal or standard pipelines.

Updated Aug 27, 2026
Search Tags:#workflow automation#requirements#claude code#task breakdown#spec generation#spec-driven development#change classification
One-click install
npx skills add https://github.com/scapia-oss/compass --skill kiro-spec-quick-scapia-oss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-spec-quick
Source: https://github.com/scapia-oss/compass/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-spec-quick
Command: npx skills add https://github.com/scapia-oss/compass --skill kiro-spec-quick-scapia-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Writing a full requirements-design-tasks spec for a three-line fix wastes effort, while skipping specs entirely for risky changes invites defects. This Skill classifies each change and generates exactly as much spec as it needs, so small fixes get a one-pass minimal spec and real features get the full pipeline. ## Core Features & Use Cases - Adaptive depth tiers: MINIMAL writes spec.json, requirements.md (or bugfix.md), and tasks.md inline in about one model turn; STANDARD runs requirements, conditional design, tasks, and a sanity review. - Redline protection: money, auth, security, data-migration, concurrency, and cross-service changes are always forced into the STANDARD pipeline with design, and no flag can override this. - Spec type routing: classifies work as feature, bugfix, tech-debt, or chore and files artifacts under categorized dated paths, honoring discovery briefs and --bug/--chore flags. - Use Case: A developer runs the command with "Add retryCount to PaymentConfig, default 3" and receives a ready-to-implement minimal spec, while "Build notification system" triggers the full requirements-to-tasks pipeline. ## Quick Start Ask the AI to run /kiro-spec-quick with a short description of your change, optionally adding --minimal, --standard, --bug, or --auto flags.

Frequently Asked Questions about kiro-spec-quick

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

FAQPage Schema
How do I generate a quick spec for a small code change?▼

Run /kiro-spec-quick with a short description of the change. The Skill auto-classifies it: a few-line, low-risk change gets a MINIMAL spec written inline in about one model turn, while larger work gets the STANDARD requirements-to-tasks pipeline.

What is the difference between MINIMAL and STANDARD spec tiers?▼

MINIMAL writes spec.json, requirements.md or bugfix.md, and tasks.md directly with no sub-skills, design, or review gates. STANDARD runs the full pipeline of requirements, conditional design, tasks, and a sanity review for multi-behavior or risky changes.

Can I force a minimal spec with the --minimal flag?▼

Yes, unless the change hits a redline signal such as money, auth, security, data migration, public contracts, concurrency, or cross-service work. Redline changes are always classified as STANDARD with design forced on, and no flag can override that rule.

When does the standard pipeline include a design phase?▼

Design runs only when warranted: architecture decisions, complex-bugfix signals like schema or shared-module changes, cross-component features, or redline work. Bounded changes needing requirements but no architecture skip design and go straight to tasks.

What happens if my change is too big for one spec?▼

Changes with 10 or more tasks, multiple domains, or unrelated capabilities are not forced through this Skill. It recommends using /kiro-spec-init for a single controlled spec or splitting the work into multiple specs instead.

Related Skills

Explore More Software Engineering Skills→
agents-repoagents-repo
3

maiconfz--feature-exploration-planner--feature-intake

Frames feature ideas against repository context and produces intake summaries with blocking questions.

Official
Intermediate
albersgalbersg

sdd-verify

Verifies SDD change implementations by executing tests and validating spec compliance.

Community
Advanced
OntoLedgyOntoLedgy

product-vision-steering

Generate product.md, tech.md, and structure.md steering documents for projects.

Official
Advanced
larus-perituslarus-peritus

Spec-Driven Development Orchestrator

Orchestrate requirements, design, and task phases with validation gates.

Community
Advanced