kiro-spec-quick

Generates requirements, design, and tasks spec files through a four-phase workflow.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-quick-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-quick
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-spec-quick
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-quick-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing complete feature specifications manually is slow and error-prone. This Skill automates the creation of a full spec package (requirements, design, and tasks) in a single run, with an optional interactive mode for step-by-step approval. ## Core Features & Use Cases - Four-Phase Spec Generation: Initializes a spec directory, then generates requirements.md, design.md, and tasks.md under .kiro/specs/{feature-name}/. - Automatic and Interactive Modes: Run all phases unattended with the --auto flag, or approve each phase manually in interactive mode. - Final Sanity Review: Reviews the generated requirements, design, and tasks for contradictions, missing prerequisites, and task coverage before declaring completion. - Use Case: Describe a feature like "user profile with avatar upload" and receive a complete, structured spec ready for implementation, with optional follow-up validation via gap analysis and design review commands. ## Quick Start Generate a quick spec for a user profile feature with avatar upload using automatic mode.

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 feature spec automatically?

Provide a feature description with the --auto flag, and the skill executes all four phases without stopping: spec initialization, requirements generation, design generation, and tasks generation. A final sanity review runs before completion.

What files does the quick spec generation create?

It creates a directory at .kiro/specs/{feature-name}/ containing spec.json, requirements.md, design.md, and tasks.md. The spec.json and requirements skeleton are initialized from templates in .kiro/settings/templates/specs/.

What is the difference between automatic and interactive mode?

Automatic mode runs all four phases continuously without prompts when --auto is present. Interactive mode pauses after each phase and asks for confirmation before continuing to the next phase.

Does quick spec generation skip any validation steps?

Yes, it skips gap analysis and design review validations that standalone commands provide. A lightweight sanity review still runs at the end, and you can optionally run $kiro-validate-gap or $kiro-validate-design afterward.

What happens if a spec generation phase fails?

The workflow stops immediately, displays the error and current state, and suggests a manual recovery command such as continuing from the failed phase with the corresponding standalone spec command.