Agent Skills › growilabs/growi › kiro-spec-init

kiro-spec-init

GitHub

根据项目描述或发现简报初始化功能规范结构，生成唯一特性名称并创建 spec.json 和 requirements.md 文件。

.claude/skills/kiro-spec-init/SKILL.md growilabs/growi

触发场景

需要新建功能规格说明时从需求文档生成结构化规范时

安装

npx skills add growilabs/growi --skill kiro-spec-init -g -y

更多选项

非标准路径

npx skills add https://github.com/growilabs/growi/tree/master/.claude/skills/kiro-spec-init -g -y

不安装直接使用

npx skills use growilabs/growi@kiro-spec-init

指定 Agent (Claude Code)

npx skills add growilabs/growi --skill kiro-spec-init -a claude-code -g -y

安装 repo 全部 skill

npx skills add growilabs/growi --all -g -y

预览 repo 内 skill

npx skills add growilabs/growi --list

SKILL.md

Frontmatter

{
    "name": "kiro-spec-init",
    "description": "Initialize a new specification with detailed project description",
    "allowed-tools": "Bash, Read, Write, Glob, AskUserQuestion",
    "argument-hint": "<project-description>"
}

Spec Initialization

## Core Task Generate a unique feature name from the project description ($ARGUMENTS) and initialize the specification structure.

Execution Steps

Check for Brief: If .kiro/specs/{feature-name}/brief.md exists (created by /kiro-discovery), read it. The brief contains problem, approach, scope, and constraints from the discovery session. Use this to pre-fill the project description and skip clarification questions that the brief already answers.
Clarify Intent: The Project Description in requirements.md must contain three elements: (a) who has the problem, (b) current situation, (c) what should change. If a brief.md exists and covers these, skip to step 3. Otherwise, ask the user to clarify before proceeding. Ask as many questions as needed; do not fill in gaps with your own assumptions.
Check Uniqueness: Verify .kiro/specs/ for naming conflicts. If the directory already exists with only brief.md (no spec.json), use that directory (discovery created it).
Create Directory: .kiro/specs/[feature-name]/ (skip if already exists from discovery)
Initialize Files Using Templates:
- Read .kiro/settings/templates/specs/init.json
- Read .kiro/settings/templates/specs/requirements-init.md
- Replace placeholders:
  - {{FEATURE_NAME}} → generated feature name
  - {{TIMESTAMP}} → current ISO 8601 timestamp
  - {{PROJECT_DESCRIPTION}} → from brief.md if available, otherwise $ARGUMENTS
  - en → language code (detect from user's input language, default to en)
- Write spec.json and requirements.md to spec directory

Important Constraints

Do NOT generate requirements, design, or tasks. This skill only creates spec.json and requirements.md.

Output Description

Provide output in the language specified in spec.json with the following structure:

Generated Feature Name: feature-name format with 1-2 sentence rationale
Project Summary: Brief summary (1 sentence)
Created Files: Bullet list with full paths
Next Step: Command block showing /kiro-spec-requirements <feature-name>

Format Requirements:

Use Markdown headings (##, ###)
Wrap commands in code blocks
Keep total output concise (under 250 words)
Use clear, professional language per spec.json.language

Safety & Fallback

Ambiguous Feature Name: If feature name generation is unclear, propose 2-3 options and ask user to select
Template Missing: If template files don't exist in .kiro/settings/templates/specs/, report error with specific missing file path and suggest checking repository setup
Directory Conflict: If feature name already exists, append numeric suffix (e.g., feature-name-2) and notify user of automatic conflict resolution
Write Failure: Report error with specific path and suggest checking permissions or disk space