据 AlphaMoat 统计,截至 2026-10,OpenSpec 累计下载 13,621 次、获 7 个星标,按累计下载量在本次参与排名的 10,914 个 AI 技能中排名第 2,045 位,在「开发编程」分类(1,069 个)中排名第 144 位。
列表默认按累计下载量排序,也可按星标排序;详情页排名按累计下载量计算。
| 平台 | 累计下载 | 星标 | 评论 |
|---|---|---|---|
| ClawHub ↗ | 5,133 | - | - |
| SkillHub ↗ | 1.4万 | 7 | — |
各平台的计数口径不同,统计时间不一致。
它用提案、规格、设计和任务组织功能开发、迁移与重构,并按新建、规划、实施、验证、归档推进。全局 @latest 可能改变安装版本行为,工作流也可能改动项目文件,写入或归档前应审阅。 使用npm和已审核固定的项目本地OpenSpec CLI;流程为新建、规划、实施、验证、归档,归档会将增量规格合入主规格并移动变更。确认写入并检查生成的集成文件。
资料发布于 2026-10-27
以下是根据技能文档生成的示例,不代表实际运行结果。
2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。
| 月份 | 累计下载 | 环比 | 星标 |
|---|---|---|---|
| 2026-10 | 1.4万 | — | 7 |
| 2026-09 | 7,202 | — | 7 |
| 2026-08 | 5,766 | +11.0% | 7 |
| 2026-07 | 5,196 | +24.5% | 6 |
| 2026-06 | 4,175 | +1.5% | - |
| 2026-05 | 4,113 | — | 2 |
以下是作者发布的原始文件,按纯文本显示,本站未做修改或审核;其中的链接不可点击,命令请核实后再运行。抓取于 2026-10-23。
--- name: openspec description: Spec-driven development with OpenSpec CLI. Use when building features, migrations, refactors, or any structured development work. Manages proposal → specs → design → tasks → implementation workflows. Supports custom schemas (TDD, rapid, etc.). Trigger on requests involving feature planning, spec writing, change management, or when /opsx commands are mentioned. --- # OpenSpec — Spec-Driven Development OpenSpec structures AI-assisted development into trackable changes with artifacts (proposal, specs, design, tasks) that guide implementation. ## Setup
```bash
# Install globally
npm install -g @fission-ai/openspec@latest
# Initialize in a project
cd /path/to/project
openspec init --tools claude
# Update after CLI upgrade
openspec update
```
## Core Workflow
Each change follows: **new → plan → apply → verify → archive**
### 1. Start a Change
```bash
# Create change folder with default schema
openspec new change <name>
# With specific schema
openspec new change <name> --schema tdd-driven
```
### 2. Plan (Create Artifacts)
Use the CLI `instructions` command to get enriched prompts for each artifact:
```bash
# Get instructions for next artifact
openspec instructions --change <name> --json
# Check progress
openspec status --change <name> --json
```
**Artifact sequence (spec-driven schema):**
1. `proposal.md` — Why and what (intent, scope, approach)
2. `specs/` — Requirements + scenarios (Given/When/Then)
3. `design.md` — Technical approach and architecture decisions
4. `tasks.md` — Implementation checklist with checkboxes
### 3. Implement
Read `tasks.md` and work through items, marking `[x]` as complete.
### 4. Verify
```bash
openspec validate --change <name> --json
```
Checks completeness, correctness, and coherence.
### 5. Archive
```bash
openspec archive <name> --yes
```
Merges delta specs into main `openspec/specs/` and moves change to archive.
## Agent Workflow (How to Use as an AI Agent)
When the user asks to build/migrate/refactor something with OpenSpec:
1. **Check project state:**
```bash
openspec list --json # Active changes
openspec list --specs --json # Current specs
openspec schemas --json # Available schemas
```
2. **Create the change:**
```bash
openspec new change <name> [--schema <schema>]
```
3. **For each artifact**, get instructions and create the file:
```bash
openspec instructions <artifact> --change <name> --json
openspec status --change <name> --json
```
Then write the artifact file to `openspec/changes/<name>/`.
4. **Implement** tasks from `tasks.md`.
5. **Validate and archive:**
```bash
openspec validate <name> --json
openspec archive <name> --yes
```
## CLI Quick Reference
| Command | Purpose |
|---------|---------|
| `openspec list [--specs] [--json]` | List changes or specs |
| `openspec show <name> [--json]` | Show change/spec details |
| `openspec status --change <name> [--json]` | Artifact completion status |
| `openspec instructions [artifact] --change <name> [--json]` | Get enriched creation instructions |
| `openspec validate [name] [--all] [--json]` | Validate changes/specs |
| `openspec archive <name> [--yes]` | Archive completed change |
| `openspec schemas [--json]` | List available schemas |
| `openspec templates [--json]` | Show template paths |
| `openspec config` | View/modify settings |
Always use `--json` for programmatic/agent use.
## Custom Schemas
Schemas define artifact sequences. Create custom ones for different workflows:
```bash
# Fork built-in schema
openspec schema fork spec-driven my-workflow
# Create from scratch
openspec schema init my-workflow
# Validate
openspec schema validate my-workflow
```
Schema files live in `openspec/schemas/<name>/schema.yaml` with templates in `templates/`.
For schema structure details, see [references/schemas.md](references/schemas.md).
## Project Structure
```
project/
├── openspec/
│ ├── config.yaml # Project config (default schema, context, rules)
│ ├── specs/ # Source of truth — current system behavior
│ ├── changes/ # Active changes (one folder each)
│ │ └── <change-name>/
│ │ ├── .openspec.yaml
│ │ ├── proposal.md
│ │ ├── specs/ # Delta specs (what's changing)
│ │ ├── design.md
│ │ └── tasks.md
│ └── schemas/ # Custom schemas
└── .claude/skills/ # Auto-generated Claude integration
```
## Spec Format
Specs use RFC 2119 keywords (SHALL/MUST/SHOULD/MAY) with Given/When/Then scenarios:
```markdown
### Requirement: User Authentication
The system SHALL issue a JWT token upon successful login.
#### Scenario: Valid credentials
- GIVEN a user with valid credentials
- WHEN the user submits login form
- THEN a JWT token is returned
```
## Delta Specs
Changes don't rewrite specs — they describe deltas (ADDED/MODIFIED/REMOVED) that merge into main specs on archive.
## Config
`openspec/config.yaml` sets defaults:
```yaml
schema: spec-driven # or tdd-driven, rapid, custom
context: |
Tech stack: TypeScript, React, Node.js
Testing: Jest
rules:
proposal:
- Include rollback plan
specs:
- Use Given/When/Then format
```
【全栈能力】编程大神.Skill:面向复杂真实项目的高阶全栈编程助手。不止生成代码,而是从一句目标接手陌生代码库,拆解需求、补齐实现、追到根因、完成重构、联调前后端,并把结果推进到能运行、能验证、能交付。覆盖 Web、后端、脚本、iOS、安卓、鸿蒙 ArkUI、微信小程序及其他技术栈,支持中英文工程、疑难 Bug、跨模块任务和长任务续做;用构建、日志、真实入口、设备或接口证据说明结果。仅问概念时直接回答,要求落地时持续推进到验收或明确阻塞。
编程专家 Pro:融合编程专家 2.0.3 工程专题与编程大神的鸿蒙 ArkTS/ArkUI、微信小程序和小游戏开发资料。用于项目实现、根因调试、审查、重构、测试、架构性能分析及多端开发验证。支持自然语言和 @专题标识,按任务读取包内知识;只问概念时直接回答。
编程专家.Skill P8级编程助手,25年实战经验技能Skill,全栈:Java/Php网站/软件项目、API设计、Bug诊断、代码生成、代码审查、重构、测试用例、性能基准、技术选型、文档生成、任务拆解、Spec驱动、Karpathy规范、CMS二次开发、前端设计、MySQL/Mariadb、项目知识图谱,以及工程纪律层(根因调试硬闭环、阶段导航、事故复盘/SLO、威胁建模/供应链安全、生产就绪/渐进式发布、AI编码治理、面向Agent代码可读性、LLM应用安全)。支持 @标识 显式调用跳过路由。
编程专家.Skill P8级编程助手,25年实战经验技能Skill,全栈:Java/Php网站/软件项目、API设计、Bug诊断、代码生成、代码审查、重构、测试用例、性能基准、技术选型、文档生成、任务拆解、Spec驱动、Karpathy规范、CMS二次开发、前端设计、MySQL/Mariadb、项目知识图谱,以及工程纪律层(根因调试硬闭环、阶段导航、事故复盘/SLO、威胁建模/供应链安全、生产就绪/渐进式发布、AI编码治理、面向Agent代码可读性、LLM应用安全)。支持 @标识 显式调用跳过路由。
编程专家 Pro:融合编程专家 2.0.3 工程专题与编程大神的鸿蒙 ArkTS/ArkUI、微信小程序和小游戏开发资料。用于项目实现、根因调试、审查、重构、测试、架构性能分析及多端开发验证。支持自然语言和 @专题标识,按任务读取包内知识;只问概念时直接回答。
编程专家 Pro:融合编程专家 2.0.3 工程专题与编程大神的鸿蒙 ArkTS/ArkUI、微信小程序和小游戏开发资料。用于项目实现、根因调试、审查、重构、测试、架构性能分析及多端开发验证。支持自然语言和 @专题标识,按任务读取包内知识;只问概念时直接回答。
编程专家.Skill P8级编程助手,25年实战经验技能Skill,全栈:Java/Php网站/软件项目、API设计、Bug诊断、代码生成、代码审查、重构、测试用例、性能基准、技术选型、文档生成、任务拆解、Spec驱动、Karpathy规范、CMS二次开发、前端设计、MySQL/Mariadb、项目知识图谱,以及工程纪律层(根因调试硬闭环、阶段导航、事故复盘/SLO、威胁建模/供应链安全、生产就绪/渐进式发布、AI编码治理、面向Agent代码可读性、LLM应用安全)。支持 @标识 显式调用跳过路由。
用 gh 命令行工具查看 GitHub 上的 PR 检查、工作流运行与 API 查询的技能。
数据月份:2026-10 · 下载/星标数聚合自公开技能注册库(ClawHub、SkillHub),按月更新。口径说明见数据方法。