kiro-spec-quick

Generate complete feature specifications from a short project description.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-quick-taku-o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-quick
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-spec-quick
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-quick-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the repetitive work of initializing and assembling feature specifications from a short project description, removing manual file creation and coordination between requirements, design, and tasks generation.

Core Features & Use Cases

  • Phased Spec Generation: Runs a 4-phase workflow to initialize a spec, generate requirements, design, and tasks, with progress reporting after each phase.
  • Interactive or Automatic Modes: Supports interactive approval between phases or a continuous --auto mode that runs all phases and a final sanity review without prompts.
  • Template-driven Initialization: Creates spec directories and files from templates, ensures name uniqueness, and integrates discovery briefs when present.
  • Use Case: Quickly bootstrap a feature spec for a small-to-medium product feature, then validate and hand off to engineering.

Quick Start

Provide a short project description such as User profile with avatar upload --auto to generate a complete spec end-to-end.

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 feature specifications from a short project description?

To generate feature specifications from a short project description, this Skill runs a 4-phase workflow that initializes a spec, then generates requirements, design, and tasks with progress reporting. It removes manual file creation and coordinates the assembly automatically.

Can I fully automate requirements, design, and task breakdown generation?

Yes, you can fully automate requirements, design, and task breakdown generation by using the --auto continuous execution mode. This mode runs all phases and a final sanity review without requiring interactive approval prompts between each phase.

What is the best way to bootstrap a spec for small-to-medium product features?

The best way to bootstrap a spec for small-to-medium product features is using template-driven initialization, which creates spec directories and files from templates while ensuring name uniqueness and integrating discovery briefs when present.

Does spec generation support interactive approval between phases?

Spec generation supports interactive approval between phases, allowing you to review and validate progress after requirements, design, and tasks are generated. This ensures quality control before handing off the complete spec to engineering.

When do I need a final sanity review for task breakdown generation?

A final sanity review for task breakdown generation is needed when running in --auto mode to validate the complete end-to-end spec without manual checks. It ensures the assembled requirements, design, and tasks are coherent before engineering handoff.

Why use automated spec generation instead of manual file creation for product requirements?

Automated spec generation eliminates repetitive manual file creation and coordination between requirements, design, and tasks generation. It quickly bootstraps a complete feature specification from a short project description and validates it for engineering handoff.