Spec Goal Development

面向跨项目 Codex 编码智能体的默认开发编排 Skill。对自然语言提出的新增、修改、调试、重构、集成或发布请求,自动判断是否属于复杂或意图不明确的开发任务;必要时用普通语言澄清真实目标,显性展示 SPEC 创建与用户授权,建立并展示 Goal,分片实施、持续调试、分层验证并完成交付闭环。非开发任务和简单、低风险、局部且可逆的开发任务走轻量路径。

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add hanshuang1008-del/spec-goal-development --skill spec-goal-development
Manual install
git clone --depth 1 https://github.com/hanshuang1008-del/spec-goal-development.git /tmp/spec-goal-development
mkdir -p ~/.claude/skills
cp -r /tmp/spec-goal-development/. ~/.claude/skills/spec-goal-development

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# SPEC 与 Goal 开发工作流

把本 Skill 当作**复杂开发任务的默认编排层**。用户不需要主动提及 Skill、SPEC、Goal 或 Sub-agent;Agent 负责识别、解释并推进,但关键状态和授权必须让用户看见。

## 1. 自动判断是否进入完整流程

从用户的自然语言请求和仓库事实判断:

- **非开发任务**:不使用本 Skill,按请求处理。
- **简单开发任务**:目标明确、局部、低风险、可逆、无需跨文件或契约变化时,走轻量路径:事实检查 → 最小修改 → 受影响验证 → 结果说明。不创建正式 SPEC、Goal 或 Sub-agent。
- **复杂或意图不明确的开发任务**:涉及新增功能、跨文件/跨层修改、接口/数据/权限/安全/配置/迁移变化、复杂调试、集成、发布,或同一句需求存在多种合理理解时,自动进入完整闭环。

即使用户只说“帮我加个登录”“把这个页面改成可下单”“这个功能总是报错”,也要根据风险和不确定性自行选择流程,不要求用户先说出流程术语。

项目专用 Skill、`AGENTS.md` 和事实源约束具体业务与技术规则;它们可以补充本流程,但不能以跳过意图确认、完成标准、验证或收尾为代价。发生冲突时遵守更高优先级的项目规则,并记录影响。

## 2. 显性但紧凑的状态协议

关键能力必须让用户看见,但不能把内部执行日志全部输出。完整流程只使用短状态,不重复已经确认的内容。

### 输出预算

| 阶段 | 基准预算 | 必要时硬上限 |
|---|---:|---:|
| 首次响应 | 5 行 | 10 行 |
| 需求澄清 | 3 个短段落 | 5 个要点 |
| SPEC 草案 | 8 个要点 | 12 个要点 |
| Goal 建立 | 3 项 | 5 项 |
| 阶段更新 | 4 行 | 8 行 |
| 最终交付 | 5–8 行 | 12 行 |

5 行是默认观感目标。首次响应只有满足以下任一条件时才可扩展到 10 行:需要用户授权、涉及安全/迁移/不可逆操作、存在阻塞/失败/回滚、需要同时说明 2 个以上实施切片,或存在 2 个以上用户决策点。其他阶段只有对应的安全、授权、关键失败、回滚或用户决策需要才使用硬上限。

### 必须显性展示的门禁

不要一次性把所有状态都播报。进入相应阶段时,按一行显示:

```text
[流程] SPEC-Goal|阶段:需求澄清|状态:进行中
```

创建 SPEC 时显示:

```text
[SPEC 草案] 已创建|目标:……|不做:……|完成:……
[授权] 请确认是否按这个方向实现;确认前不会修改产品代码。
```

用户确认后显示:

```text
[SPEC] APPROVED|依据:用户确认“……”
[Goal] 已建立|阶段:1/4|完成条件:……
```

如果无法创建工具级 Goal,显示:

```text
[Goal] 未建立|原因:……|替代:使用文本状态持续跟踪
```

需要并行时,先用一行说明建议和授权点;用户同意后再展示分工。验证和交付只报告实际结果、未验证项和阻塞,不复制完整 SPEC。

超出基准预算时按顺序降级:保留当前状态、风险、当前动作和下一步;压缩已确认事实;删除重复背景、工具日志和逐步过程;把详细表格写入参考文件。达到硬上限仍无法说明时,只给紧凑摘要并询问用户是否展开。除非用户要求,不展示完整内部模板、每个工具调用或逐步思考过程。

## 3. 先读取事实

开始复杂开发任务前:
Read the full skill on GitHub

Details

Skill name
spec-goal-development
License
MIT
Repo updated
3 August 2026

FAQ

What does the Spec Goal Development skill do?

面向跨项目 Codex 编码智能体的默认开发编排 Skill。对自然语言提出的新增、修改、调试、重构、集成或发布请求,自动判断是否属于复杂或意图不明确的开发任务;必要时用普通语言澄清真实目标,显性展示 SPEC 创建与用户授权,建立并展示 Goal,分片实施、持续调试、分层验证并完成交付闭环。非开发任务和简单、低风险、局部且可逆的开发任务走轻量路径。

How do I install the Spec Goal Development skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add hanshuang1008-del/spec-goal-development --skill spec-goal-development. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Spec Goal Development popular?

It lives in hanshuang1008-del/spec-goal-development, which has 44 GitHub stars and 0 forks.

Related skills

Traits

44

harrysolovay/traits-poc

Use when the user corrects your approach or expresses a reusable coding preference, even without mentioning traits: propose saving new durable insights and ask for approval. Also use when creating or revising traits, configuring trait sources, reconciling overlaps, or checking traits before committing.

Software Development

Sankhya API Java

43

andressaolivi/sankhya-skills

Conhecimento sobre os pontos de extensão Java do ERP Sankhya — interfaces oficiais de customização e padrões de uso da camada de persistência. Use quando o usuário perguntar sobre customização Java do Sankhya: AcaoRotinaJava, EventoProgramavelJava, RegraNegocioJava, TarefaJava, AcaoReguaCobranca, DynamicVO, JapeSession, EntityFacade, JdbcWrapper, ServiceContext, ServiceBroker; action buttons, eventos programáveis, regras de negócio, workflow Java, régua de cobrança, manipulação de VOs, persistência JAPE, SQL nativo com macros do Sankhya. NÃO use para configuração funcional do ERP (use sankhya-

Software Development

Weather

44

iamclancyliang/nanobot-eino

Get current weather and forecasts (no API key required).

Software Development

Check Crewai API

49

crewAIInc/skills

Current crewai 1.15.x API versus the 0.x API that coding assistants remember: imports, Agent/Task/Crew parameters and defaults, kickoff variants, CrewOutput fields, LLM model strings and provider extras, structured output (output_pydantic, response_model, response_format), guardrails, unified Memory, knowledge embedders, the `crewai create crew` wizard vs --classic, reset-memories flags, and removed features. Use when writing, reviewing, or debugging any crewai code, before trusting remembered crewai syntax, or when a user pastes errors like `cannot import name 'BaseTool' from 'crewai_tools'`,

Software Development24

Cleanddd Dotnet Coding

49

zhouda1fu/Ncp.Admin

在 CleanDDD 项目中落地已建模的需求(聚合/命令/查询/API 端点(Endpoints)/事件/仓储/配置/测试)的编码指南;用于编写或修改业务功能、端点与数据访问时

Software Development12

AI Memory System Architecture

44

hyxnj666-creator/ai-memory

System architecture facts: components, data flow, integration boundaries. Load when implementing cross-component features, debugging integration issues, or onboarding to the codebase. Topics: Event sourcing for the billing audit log.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.