kirospec-basic

Scaffold in-project SPECs with local scripts and validate required files.

31|4|Updated Apr 6, 2026

Search Tags:#spec #kiro #design-docs #spec-init #local-specs #requirements-docs #tasks-docs

Ready to run

npx skills add https://github.com/kissrosecicd-hub/agents-evolution --skill kirospec-basic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kirospec-basic
Source: https://github.com/kissrosecicd-hub/agents-evolution/tree/main/.agents/skills/kirospec-basic
Command: npx skills add https://github.com/kissrosecicd-hub/agents-evolution --skill kirospec-basic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill centralizes SPEC creation and maintenance inside the project by leveraging local SPEC rules, enabling portable specifications without relying on external folders.

Core Features & Use Cases

In-project SPEC scaffolding: creates and maintains .kiro/specs/<spec-name>/ entirely within the project.
Template-driven guidance: reuses canonical templates from design/requirements/tasks for consistency.
Local, environment-driven workflow: validates SPEC_NAME, initializes specs with local scripts, and checks for required files (design.md, requirements.md, tasks.md).

Quick Start

Run the spec-init process to generate a new SPEC skeleton in your project with a single command.

Frequently Asked Questions about kirospec-basic

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

FAQPage Schema

How do I create local specs for design and requirements docs inside my project?▼

To create local specs, run the spec-init process to generate a SPEC skeleton within your project. It validates the SPEC_NAME and initializes the .kiro/specs directory using a local script, ensuring design.md, requirements.md, and tasks.md exist without external folder dependencies.

What is in-project SPEC scaffolding and when do I need it?▼

In-project SPEC scaffolding centralizes specification creation inside your repository. You need it when you want portable specifications that rely on local rules rather than external folders, ensuring your design.md, requirements.md, and tasks.md files remain consistent and self-contained.

How do I initialize a new SPEC skeleton from a script?▼

You initialize a new SPEC skeleton by running the spec-init process, which executes the local scripts/spec-init.sh file. This action validates your SPEC_NAME input and scaffolds the required directory structure along with the design, requirements, and tasks markdown files.

Do I need external folder dependencies to maintain requirements docs and tasks docs?▼

No, you do not need external folder dependencies to maintain requirements and tasks docs. This approach leverages local SPEC rules to enable portable specifications entirely within your project, verifying that the required markdown files exist locally.

What's the best way to ensure design.md, requirements.md, and tasks.md exist consistently?▼

The best way to ensure these docs exist consistently is using template-driven SPEC scaffolding. It reuses canonical templates for design, requirements, and tasks during initialization, automatically verifying the presence of all three required markdown files.

Why does spec-init fail when the SPEC_NAME is missing or invalid?▼

The spec-init process fails because SPEC_NAME validation is a required step before creating the local skeleton. Ensuring a valid SPEC_NAME allows the local script to correctly generate the specification directory and verify the required design, requirements, and tasks files.