重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
npx skills add https://github.com/feiskyer/codex-settings --skill kiro-skill一个交互式工作流,将想法转化为全面的功能规范、设计文档和可操作的实现计划。
当你提及创建功能规范、设计文档或实现计划时,此技能将引导你完成:
存储:在 .kiro/specs/{feature-name}/ 目录中创建文件(使用 kebab-case 命名)
在回应前阅读 helpers/kiro-identity.md。它定义了语气、语言偏好和最小化代码理念。
如果你需要视觉化的阶段门或流程参考,请查看 helpers/workflow-diagrams.md。
将一个粗略的想法转化为结构化的需求,包含用户故事和 EARS 验收标准。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
生成初始需求
.kiro/specs/{feature-name}/requirements.md需求结构
# 需求文档
## 简介
[功能摘要 - 它解决了什么问题?]
## 需求
### 需求 1
**用户故事:** 作为一个 [角色],我想要 [功能],以便 [收益]
#### 验收标准
1. WHEN [事件] THEN [系统] SHALL [响应]
2. IF [前置条件] THEN [系统] SHALL [响应]
3. WHEN [事件] AND [条件] THEN [系统] SHALL [响应]
### 需求 2
**用户故事:** 作为一个 [角色],我想要 [功能],以便 [收益]
#### 验收标准
1. WHEN [事件] THEN [系统] SHALL [响应]
简易需求语法方法 - 结构化的验收标准:
WHEN [事件] THEN [系统] SHALL [响应] - 事件驱动IF [条件] THEN [系统] SHALL [响应] - 条件驱动WHILE [状态] [系统] SHALL [响应] - 状态驱动WHERE [功能] [系统] SHALL [响应] - 普遍性[系统] SHALL [响应] - 无条件如果澄清过程停滞:
根据已批准的需求创建全面的设计文档,并在设计过程中进行研究。
.kiro/specs/{feature-name}/requirements.md 存在识别研究需求
进行研究
创建 .kiro/specs/{feature-name}/design.md,包含:
概述
架构
组件与接口
数据模型
错误处理
测试策略
# 功能设计
## 概述
[高级方法和关键决策]
## 架构
```mermaid
graph TD
A[Component A] --> B[Component B]
B --> C[Component C]
interface UserModel {
id: string;
email: string;
role: UserRole;
}
[继续其他部分...]
如果设计变得过于复杂:
将已批准的设计转化为可操作的、测试驱动的实现任务。
核心原则:将设计转化为提示,供代码生成 LLM 以测试驱动的方式实现每个步骤。
关注点:
排除项:
创建 .kiro/specs/{feature-name}/tasks.md,包含:
# 实现计划
- [ ] 1. 设置项目结构和核心接口
- 为模型、服务、存储库创建目录结构
- 定义建立系统边界的接口
- _需求:1.1_
- [ ] 2. 实现数据模型和验证
- [ ] 2.1 创建核心数据模型接口和类型
- 为所有数据模型编写 TypeScript 接口
- 实现数据完整性的验证函数
- _需求:2.1, 3.3, 1.2_
- [ ] 2.2 实现带验证的用户模型
- 编写带验证方法的 User 类
- 为用户模型验证创建单元测试
- _需求:1.2_
- [ ] 3. 创建存储机制
- [ ] 3.1 实现数据库连接工具
- 编写连接管理代码
- 创建错误处理工具
- _需求:2.1, 3.3_
[其他任务...]
结构:
每个任务必须包含:
质量标准:
重要:此工作流仅用于创建规划工件。
以精确和专注的方式实现功能规范中的特定任务。
始终先阅读规范文件:
.kiro/specs/{feature-name}/requirements.md.kiro/specs/{feature-name}/design.md.kiro/specs/{feature-name}/tasks.md在没有理解完整上下文的情况下,切勿执行任务。
任务选择
实现
完成协议
对于实现请求:
对于信息请求:
stateDiagram-v2
[*] --> Requirements
Requirements --> ReviewReq : Complete
ReviewReq --> Requirements : Changes
ReviewReq --> Design : Approved
Design --> ReviewDesign : Complete
ReviewDesign --> Design : Changes
ReviewDesign --> Tasks : Approved
Tasks --> ReviewTasks : Complete
ReviewTasks --> Tasks : Changes
ReviewTasks --> [*] : Approved
Execute : Execute Single Task
[*] --> Execute : Task Request
Execute --> [*] : Complete
通过检查确定当前状态:
# 检查 .kiro 目录
if [ -d ".kiro/specs" ]; then
# 列出功能
ls .kiro/specs/
# 对于特定功能,检查阶段
FEATURE="$1"
if [ -f ".kiro/specs/$FEATURE/requirements.md" ]; then
echo "Requirements exists"
fi
if [ -f ".kiro/specs/$FEATURE/design.md" ]; then
echo "Design exists"
fi
if [ -f ".kiro/specs/$FEATURE/tasks.md" ]; then
echo "Tasks exists - ready for execution"
fi
fi
Kiro 为功能开发提供了一个结构化的、迭代的方法:
每个阶段在继续之前都需要明确的用户批准,确保在整个开发过程中保持一致性和质量。
每周安装次数
52
仓库
GitHub 星标数
167
首次出现
2026年1月23日
安全审计
安装于
codex50
claude-code49
opencode49
gemini-cli49
github-copilot47
cursor47
An interactive workflow that transforms ideas into comprehensive feature specifications, design documents, and actionable implementation plans.
When you mention creating a feature spec, design document, or implementation plan, this skill helps guide you through:
Storage : Creates files in .kiro/specs/{feature-name}/ directory (kebab-case naming)
Read helpers/kiro-identity.md before responding. It defines tone, language preference, and minimal-code philosophy.
If you need visual phase gates or flow references, see helpers/workflow-diagrams.md.
Transform a rough idea into structured requirements with user stories and EARS acceptance criteria.
Generate Initial Requirements
.kiro/specs/{feature-name}/requirements.mdRequirements Structure
# Requirements Document
## Introduction
[Feature summary - what problem does this solve?]
## Requirements
### Requirement 1
**User Story:** As a [role], I want [feature], so that [benefit]
#### Acceptance Criteria
1. WHEN [event] THEN [system] SHALL [response]
2. IF [precondition] THEN [system] SHALL [response]
3. WHEN [event] AND [condition] THEN [system] SHALL [response]
### Requirement 2
**User Story:** As a [role], I want [feature], so that [benefit]
#### Acceptance Criteria
1. WHEN [event] THEN [system] SHALL [response]
Easy Approach to Requirements Syntax - structured acceptance criteria:
WHEN [event] THEN [system] SHALL [response] - Event-drivenIF [condition] THEN [system] SHALL [response] - ConditionalWHILE [state] [system] SHALL [response] - State-drivenWHERE [feature] [system] SHALL [response] - Ubiquitous[system] SHALL [response] - UnconditionalIf clarification stalls:
Create comprehensive design document based on approved requirements, conducting research during the design process.
.kiro/specs/{feature-name}/requirements.mdIdentify Research Needs
Conduct Research
Create .kiro/specs/{feature-name}/design.md with:
Overview
Architecture
Components and Interfaces
Data Models
Error Handling
Testing Strategy
# Feature Design
## Overview
[High-level approach and key decisions]
## Architecture
```mermaid
graph TD
A[Component A] --> B[Component B]
B --> C[Component C]
interface UserModel {
id: string;
email: string;
role: UserRole;
}
[Continue with other sections...]
If design becomes too complex:
Convert approved design into actionable, test-driven implementation tasks.
Core Principle : Convert design into prompts for code-generation LLM to implement each step in test-driven manner.
Focus :
Exclude :
Create .kiro/specs/{feature-name}/tasks.md with:
# Implementation Plan
- [ ] 1. Set up project structure and core interfaces
- Create directory structure for models, services, repositories
- Define interfaces that establish system boundaries
- _Requirements: 1.1_
- [ ] 2. Implement data models and validation
- [ ] 2.1 Create core data model interfaces and types
- Write TypeScript interfaces for all data models
- Implement validation functions for data integrity
- _Requirements: 2.1, 3.3, 1.2_
- [ ] 2.2 Implement User model with validation
- Write User class with validation methods
- Create unit tests for User model validation
- _Requirements: 1.2_
- [ ] 3. Create storage mechanism
- [ ] 3.1 Implement database connection utilities
- Write connection management code
- Create error handling utilities
- _Requirements: 2.1, 3.3_
[Additional tasks...]
Structure :
Each Task Must Include :
Quality Standards :
Important : This workflow is ONLY for creating planning artifacts.
Implement specific tasks from the feature specification with precision and focus.
ALWAYS read spec files first :
.kiro/specs/{feature-name}/requirements.md.kiro/specs/{feature-name}/design.md.kiro/specs/{feature-name}/tasks.mdNever execute tasks without understanding full context.
Task Selection
Implementation
Completion Protocol
For implementation requests :
For information requests :
stateDiagram-v2
[*] --> Requirements
Requirements --> ReviewReq : Complete
ReviewReq --> Requirements : Changes
ReviewReq --> Design : Approved
Design --> ReviewDesign : Complete
ReviewDesign --> Design : Changes
ReviewDesign --> Tasks : Approved
Tasks --> ReviewTasks : Complete
ReviewTasks --> Tasks : Changes
ReviewTasks --> [*] : Approved
Execute : Execute Single Task
[*] --> Execute : Task Request
Execute --> [*] : Complete
Determine current state by checking:
# Check for .kiro directory
if [ -d ".kiro/specs" ]; then
# List features
ls .kiro/specs/
# For specific feature, check phase
FEATURE="$1"
if [ -f ".kiro/specs/$FEATURE/requirements.md" ]; then
echo "Requirements exists"
fi
if [ -f ".kiro/specs/$FEATURE/design.md" ]; then
echo "Design exists"
fi
if [ -f ".kiro/specs/$FEATURE/tasks.md" ]; then
echo "Tasks exists - ready for execution"
fi
fi
Kiro provides a structured, iterative approach to feature development:
Each phase requires explicit user approval before proceeding, ensuring alignment and quality throughout the development process.
Weekly Installs
52
Repository
GitHub Stars
167
First Seen
Jan 23, 2026
Security Audits
Gen Agent Trust HubFailSocketPassSnykPass
Installed on
codex50
claude-code49
opencode49
gemini-cli49
github-copilot47
cursor47
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
125,600 周安装