spec-driven-simple-task

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

You are executing a lightweight ad-hoc task using the spec-driven framework's simple-task mode.

你正在使用规范驱动框架的简单任务模式执行轻量级临时任务。

Prerequisites

前置要求

The

.spec-driven/

directory must exist at the project root. Before proceeding, verify:

ls .spec-driven/

If this fails, the project is not initialized. Run

/spec-driven-init

first.

项目根目录下必须存在

.spec-driven/

目录。继续操作前，请先验证：

ls .spec-driven/

如果命令执行失败，说明项目尚未初始化，请先运行

/spec-driven-init

。

Steps

步骤

Entry gate — evaluate the user's task description against three criteria before executing:
- Scope check: If the task clearly spans multiple modules, involves schema changes, or affects cross-cutting concerns → reject, recommend
```
/spec-driven-propose
```
  or
```
/spec-driven-brainstorm
```
- Hotfix check: If the task is framed as urgent, hotfix, or critical production fix → reject, recommend the formal change workflow (
```
/spec-driven-propose
```
  )
- If the task fails any check, explain why and suggest the appropriate alternative skill. Do not proceed.
Load spec context — read
```
.spec-driven/config.yaml
```
,
```
.spec-driven/specs/INDEX.md
```
, and any relevant main spec files to understand current requirements as background for the task.
Execute the task — perform the work directly (edit files, run commands, etc.). Do not create or modify anything under
```
.spec-driven/changes/
```
.
Assess spec impact — after completing the task, evaluate whether the work affected any specs:
- No spec impact — the task is complete, log it
- Spec drift detected — suggest
```
/spec-driven-sync-specs
```
  or
```
/spec-driven-spec-edit
```
- Mapping drift detected — suggest
```
/spec-driven-resync-code-mapping
```
- New change need discovered — suggest
```
/spec-driven-propose
```
  or
```
/spec-driven-brainstorm
```
- You MUST NOT automatically invoke other skills. Suggestions are advisory only.
Log the task — create a markdown log at
```
.spec-driven/simple-tasks/YYYY-MM-DD-<name>.md
```
:
- Ensure the directory exists:
```
mkdir -p .spec-driven/simple-tasks/
```
- ```
<name>
```
  is a short kebab-case identifier derived from the task description
- The log MUST contain: Task (description), What was done (summary), Spec impact (none / drift / new change), Follow-up (suggestions or "None")
- The
```
simple-tasks/
```
  directory is a flat log — no subdirectories, no lifecycle management.

准入校验 — 执行任务前，对照三项标准评估用户的任务描述：
- 范围检查：如果任务明显跨多个模块、涉及 schema 变更，或影响横切关注点 → 拒绝，推荐使用
```
/spec-driven-propose
```
  或
```
/spec-driven-brainstorm
```
- 热修复检查：如果任务属于紧急需求、热修复或关键生产环境修复 → 拒绝，推荐使用正式变更工作流（
```
/spec-driven-propose
```
  ）
- 如果任务未通过任意一项检查，说明原因并推荐合适的替代技能，不要继续执行。
加载规范上下文 — 读取
```
.spec-driven/config.yaml
```
、
```
.spec-driven/specs/INDEX.md
```
及所有相关的主规范文件，了解当前需求作为任务执行的背景信息。
执行任务 — 直接完成相关工作（编辑文件、运行命令等）。不要在
```
.spec-driven/changes/
```
目录下创建或修改任何内容。
评估规范影响 — 完成任务后，评估本次工作是否影响任意规范：
- 无规范影响 — 任务完成，记录日志
- 检测到规范漂移 — 建议使用
```
/spec-driven-sync-specs
```
  或
```
/spec-driven-spec-edit
```
- 检测到映射漂移 — 建议使用
```
/spec-driven-resync-code-mapping
```
- 发现新的变更需求 — 建议使用
```
/spec-driven-propose
```
  或
```
/spec-driven-brainstorm
```
- 严禁自动调用其他技能，建议仅作参考。
记录任务日志 — 在
```
.spec-driven/simple-tasks/YYYY-MM-DD-<name>.md
```
路径下创建 markdown 日志：
- 确保目录存在：
```
mkdir -p .spec-driven/simple-tasks/
```
- ```
<name>
```
  是从任务描述派生的短横线分隔的短标识符
- 日志必须包含：任务（描述）、完成内容（摘要）、规范影响（无/漂移/新变更）、后续动作（建议或“无”）
- ```
simple-tasks/
```
  目录是扁平化的日志存储目录 — 不要创建子目录，也不需要生命周期管理。

Rules

规则

This skill never creates, modifies, or archives anything under
```
.spec-driven/changes/
```
Spec context is read-only during task execution — spec updates happen through existing skills
The log file is the only artifact created by this skill
If the task grows beyond simple scope mid-execution, stop and suggest switching to
```
/spec-driven-propose
```

本技能永远不会在
```
.spec-driven/changes/
```
目录下创建、修改或归档任何内容
任务执行期间规范上下文为只读状态 — 规范更新需通过现有技能完成
日志文件是本技能生成的唯一产物
如果任务在执行过程中超出简单范围，请停止操作并建议切换到
```
/spec-driven-propose
```