spec-mode
Skill1 starsChanged 38 days agoMITView on GitHub
Specification-driven development for complex features. Triggers when user mentions "spec", "specification", "规范", or asks to plan a complex feature. Use for multi-file changes, architectural decisions, or when requirements need clarification before implementation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AVANT-ICONIC/gpt-webui-skillstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- AVANT-ICONIC/gpt-webui-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audience-report-formattingSkill
- baidu-netdiskSkill
- baidu-netdisk-syncspace-recoverySkill
- china-proxySkill
- chrome-devtoolsSkill
- claude-maintenanceSkill
- cloudcli-device-onboardingSkill
- codex-dream-skin-fixSkill
- content-research-writerSkill
- git-history-cleanupSkill
- github-aliyun-deploySkill
- github-kbSkill
- google-flow-story-videoSkill
- mac-windows-lanSkill
- meeting-materials-uploadSkill
- meeting-reimbursement-auditSkill
- openmaicSkill
- opus-code-videoSkill
- seedance-short-dramaSkill
- video-courseware-extractorSkill
- wechat-account-bookmarksSkill
- wechat-ai-model-writerSkill
- wechat-android-shortcutsSkill
- wechat-ios-shortcutsSkill
- wechat-medical-writerSkill
- wechat-tech-writerSkill
- wps-presentation-batchSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Ask clarifying questions about the feature
- Distinctive: line 38
Write user stories in format: "作为[角色],我希望[功能],以便[价值]"
- Distinctive: line 41
Create terminology glossary if needed
- Very specific: line 70
Goal: Create design.md and tasks.md
- Distinctive: line 75
Consider trade-offs and alternatives
- Very specific: line 135
Use TaskCreate tool to create trackable tasks from tasks.md
- Very specific: line 137
Update task status with TaskUpdate as you progress
- Distinctive: line 138
Test incrementally as you build
- Distinctive: line 140
Verify against acceptance criteria
- Very specific: line 158
When starting implementation, convert tasks.md into trackable tasks:
- Distinctive: line 175
Use clear section headers matching the template
- Distinctive: line 176
Write in Chinese for requirements and design (match project language)
- Distinctive: line 178
Ask questions early rather than making assumptions
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Spec Mode - Structured Development
This skill creates structured specification documents following the .kiro/specs/ format used in the project.
When to Use
Trigger this skill when:
- User mentions "spec", "specification", "规范"
- Complex features spanning multiple files
- Architectural changes requiring design approval
- Requirements need clarification before coding
- User asks to "plan" or "design" before implementing
Spec Directory Structure
Each spec is a directory under .kiro/specs/<feature-name>/ containing:
.kiro/specs/<feature-name>/
├── requirements.md # 需求文档(用户故事 + 验收标准)
├── design.md # 设计文档(架构、技术选型、字段设计)
├── tasks.md # 任务清单(checkbox 格式)
└── *.md # 其他实现文档(可选)Three-Phase Workflow
Phase 1: Requirements Gathering
Goal: Create requirements.md
- Ask clarifying questions about the feature
- Write user stories in format: "作为[角色],我希望[功能],以便[价值]"
- Define acceptance criteria using WHEN/THEN/SHALL format
- Identify edge cases and constraints
- Create terminology glossary if needed
Output Template:
# 需求文档
## 简介
[功能概述,1-2段]
## 术语表
- **Term**: Definition
## 需求
### 需求 1: [功能名称]
**用户故事:** 作为[角色],我希望[功能],以便[价值]。
#### 验收标准
1. WHEN [条件] THEN System SHALL [行为]
2. THE System SHALL [要求]
3. IF [条件] THEN System SHALL [行为]Phase 2: Design & Planning
Goal: Create design.md and tasks.md
- Propose technical approach and architecture
- Define data models and API contracts
- List specific files to create/modify
- Consider trade-offs and alternatives
- Break down into granular tasks
- Get user approval before proceeding
design.md Template:
# 设计文档
## 概述
[设计目标、技术选型]
## 核心设计目标
1. **目标1**: 说明
2. **目标2**: 说明
## 技术选型
| 层级 | 技术 | 说明 |
|------|------|------|
| 前端 | Vue 3 | ... |
| 后端 | Spring Boot | ... |
## 架构设计
[组件图、流程图、数据流]
## 数据模型
[实体定义、字段说明]
## API 设计
[接口列表、请求/响应格式]
## 涉及文件清单
| 文件 | 修改类型 | 说明 |
|------|---------|------|tasks.md Template:
# 任务清单
## 1. 后端开发
- [ ] 1.1 创建数据模型
- [ ] 1.2 实现 Service 层
- [ ] 1.3 实现 Controller 层
## 2. 前端开发
- [ ] 2.1 创建 API 接口
- [ ] 2.2 实现核心组件
- [ ] 2.3 集成路由
## 3. 测试
- [ ] 3.1 单元测试
- [ ] 3.2 集成测试Phase 3: Implementation
Goal: Execute tasks and update progress
- Use
TaskCreatetool to create trackable tasks fromtasks.md - Execute approved design systematically
- Update task status with
TaskUpdateas you progress - Test incrementally as you build
- Document significant decisions
- Verify against acceptance criteria
Implementation Flow:
1. Read tasks.md
2. Create tasks using TaskCreate tool
3. For each task:
- TaskUpdate(status: in_progress)
- Implement the task
- Test the implementation
- TaskUpdate(status: completed)
4. Verify all acceptance criteria metTool Integration
Use TaskCreate for Task Tracking
When starting implementation, convert tasks.md into trackable tasks:
// Example: Create task from tasks.md
TaskCreate({
subject: "创建数据模型",
description: "创建 AdvancedSearchRequest.java, FieldMetadata.java 等 DTO 类",
activeForm: "创建数据模型中"
})Use EnterPlanMode for Complex Planning
For very complex features, use EnterPlanMode tool to get dedicated planning assistance before creating the spec.
Communication Style
- Use clear section headers matching the template
- Write in Chinese for requirements and design (match project language)
- Be concise but thorough
- Ask questions early rather than making assumptions
- Present options when multiple approaches are valid
- Confirm understanding before moving to next phase
Example Trigger Phrases
- "Let's spec out this feature first"
- "I need to plan a complex change"
- "Can you help me design this before coding?"
- "写一个规范文档"
- "创建一个 spec"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

