@oevery/rsp 1.2.0 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  English | [简体中文](./README.zh-CN.md)
4
4
 
5
- RSP = **Rules, Specs, Plans**. A lightweight AI-assisted workflow for project rules, specs, and feature plans.
5
+ RSP = **Rules, Specs, Plans**. A lightweight AI-assisted workflow for durable project knowledge and single-file change tracking.
6
6
 
7
7
  ## Quick start
8
8
 
@@ -15,7 +15,7 @@ Recommended bootstrap flow:
15
15
 
16
16
  ```bash
17
17
  npx -y @oevery/rsp init --with-project-setup
18
- # fill .rsp/features/project-setup.md
18
+ # fill .rsp/changes/project-setup.md
19
19
  # fill .rsp/specs/design.md
20
20
  npx -y @oevery/rsp doctor
21
21
  ```
@@ -23,9 +23,9 @@ npx -y @oevery/rsp doctor
23
23
  ## Core idea
24
24
 
25
25
  - `rules/` stores durable constraints.
26
- - `specs/` stores project-level design docs.
27
- - `features/` stores active work.
28
- - `active.d/` mirrors active features with empty marker files.
26
+ - `specs/` stores project-level source-of-truth docs.
27
+ - `changes/` stores open work in a single-file format.
28
+ - `focus.d/` mirrors current focused changes with empty marker files.
29
29
  - `archives/` stores completed work.
30
30
 
31
31
  ```text
@@ -36,19 +36,27 @@ npx -y @oevery/rsp doctor
36
36
  ├── specs/
37
37
  │ ├── INDEX.md # auto-generated
38
38
  │ └── design.md
39
- ├── features/
39
+ ├── changes/
40
40
  │ └── <name>.md
41
- ├── active.d/
41
+ ├── focus.d/
42
42
  │ └── <name>
43
43
  └── archives/
44
44
  └── INDEX.md # auto-generated
45
45
  ```
46
46
 
47
+ ## Concepts
48
+
49
+ - `specs/` describes durable project facts and current agreed design.
50
+ - `changes/` captures open work, including features, fixes, refactors, docs, ops, and research.
51
+ - A change is always a single Markdown file with explicit sections for proposal, spec, design, tasks, verification, and blockers.
52
+ - Completed changes move to `archives/`, while durable outcomes should be reflected in `specs/` or `rules/` before archiving.
53
+ - Durable outcomes mean stable facts only. Do not promote task history, debugging notes, or one-off implementation context into `specs/` or `rules/`.
54
+
47
55
  ## File ownership
48
56
 
49
57
  - `AGENTS.md`: only the `<!-- rsp:begin --> ... <!-- rsp:end -->` block is managed by RSP.
50
- - `.rsp/specs/INDEX.md`: auto-generated. Rebuild with `rsp specs-index`.
51
- - `.rsp/archives/INDEX.md`: auto-generated. Rebuild with `rsp archive-index`.
58
+ - `.rsp/specs/INDEX.md`: auto-generated. Rebuild with `rsp update`.
59
+ - `.rsp/archives/INDEX.md`: auto-generated. Rebuild with `rsp update`.
52
60
  - `.rsp/specs/design.md`: created by `rsp init`, then owned by the project.
53
61
  - `.rsp/rules/project-rules.md`: optional; create only when the project has durable local rules.
54
62
  - Keep durable architecture, boundaries, and cross-cutting technical constraints in `.rsp/specs/design.md`.
@@ -63,23 +71,43 @@ Managed block example:
63
71
  ## RSP Entry
64
72
 
65
73
  Read in order:
66
- 1. .rsp/rules/*.md
67
- 2. .rsp/specs/INDEX.md
68
- 3. .rsp/specs/design.md
69
- 4. .rsp/active.d/ and matching .rsp/features/*.md
74
+ 1. .rsp/rules/rsp-rules.md
75
+ 2. .rsp/focus.d/
76
+ 3. matching .rsp/changes/*.md for the focused entries
77
+ 4. .rsp/specs/design.md
78
+ 5. .rsp/specs/INDEX.md
79
+ 6. only the relevant additional .rsp/rules/*.md and .rsp/specs/*.md files
70
80
  <!-- rsp:end -->
71
81
  ```
72
82
 
73
83
  `rsp init --agents-mode <mode>`:
74
84
 
75
- - `managed`: insert/update the managed block in `AGENTS.md`.
76
- - `skip`: scaffold `.rsp/` only.
77
- - `print`: scaffold `.rsp/` and print the managed block.
85
+ - `managed`: create `AGENTS.md` when needed and insert/update the managed block.
86
+ - `print`: initialize normally and also print the resulting `AGENTS.md` content.
78
87
 
79
88
  ## Skill
80
89
 
81
90
  Use `skills/rsp/SKILL.md` for step-by-step setup, workflow, and auditing guidance. It is intended for on-demand loading rather than always-on core rules.
82
91
 
92
+ Reading guidance:
93
+
94
+ - `README.md`: human-oriented overview and examples
95
+ - `.rsp/rules/rsp-rules.md`: canonical rules source
96
+ - `skills/rsp/SKILL.md`: operational guide for applying those rules with an agent
97
+
98
+ Surface matrix:
99
+
100
+ | Surface | Primary audience | Role |
101
+ |---|---|---|
102
+ | `README.md` | Humans | Overview, onboarding, examples |
103
+ | `.rsp/rules/rsp-rules.md` | Agents | Canonical normative rules source |
104
+ | `skills/rsp/SKILL.md` | Agents | Operational guide for applying the rules |
105
+ | `AGENTS.md` | Humans and agents | Navigation entrypoint into the right files |
106
+
107
+ Humans should usually start with `README.md`; agents should treat `.rsp/rules/rsp-rules.md` as normative.
108
+
109
+ When this README shows `rsp <command>`, it assumes the command is already available in your environment. Otherwise use `npx -y @oevery/rsp <command>`.
110
+
83
111
  Example optional installation flow:
84
112
 
85
113
  ```bash
@@ -88,22 +116,50 @@ npx skills add oevery/rsp --skill rsp
88
116
 
89
117
  This repository publishes a skill named `rsp` under `skills/rsp/`.
90
118
 
91
- Then load the installed RSP skill only when you are adopting RSP, auditing setup, or reorganizing project-level rules/specs.
119
+ ## Work Model
120
+
121
+ ```text
122
+ open → archived
123
+ ```
124
+
125
+ Directory roles are intentionally single-purpose:
126
+
127
+ - `changes/`: open changes
128
+ - `focus.d/`: currently focused changes
129
+ - `archives/`: completed history
130
+
131
+ Inside `open`, typical work includes:
132
+
133
+ - `create`: create and scope a change.
134
+ - `focus` / `unfocus`: decide which open change is currently foregrounded.
135
+ - Edit the change file directly — fill sections, mark tasks, write design decisions.
136
+ - Review whether durable updates are needed before archive.
137
+
138
+ `archive` moves completed work into history. Archive never blocks — it warns but leaves the final decision to the agent or human.
139
+
140
+ Agents should treat only entries in `focus.d/` as current work. Unfocused files in `changes/` are still open, but should not be treated as the current target unless the user explicitly asks for them or they are re-focused.
141
+
142
+ The durable update decision (whether the change produced knowledge that belongs in `.rsp/specs/` or `.rsp/rules/`) is a semantic choice made by the RSP skill or a human reviewer.
92
143
 
93
144
  ## Recommended workflow
94
145
 
95
146
  New project:
96
147
 
97
148
  1. `npx -y @oevery/rsp init`
98
- 2. Prefer `npx -y @oevery/rsp init --with-project-setup`, or run `rsp new project-setup` manually
149
+ 2. Prefer `npx -y @oevery/rsp init --with-project-setup`, or run `rsp create project-setup` manually
99
150
  3. Fill `.rsp/specs/design.md`
100
151
  4. Use `rsp add spec <name>` only when a new durable project doc is needed
101
152
  5. Use `rsp add rules project-rules` only when the project has stable local rules
102
- 6. Start work with `rsp new <name>`
153
+ 6. Start work with `rsp create <name>`
154
+ 7. If you want an existing open change to become current work, use `rsp focus <name>`
155
+ 8. Use `rsp unfocus <name>` when you want to remove a change from the current focus set
156
+ 9. Edit the change file directly to implement the work and mark tasks complete
157
+ 10. Use the RSP skill or a human review to decide whether durable updates are needed
158
+ 11. Finish with `rsp archive <name>`
103
159
 
104
160
  Existing project with a rich `AGENTS.md`:
105
161
 
106
- 1. `npx -y @oevery/rsp init --agents-mode managed`
162
+ 1. `npx -y @oevery/rsp init`
107
163
  2. Keep the managed block thin
108
164
  3. Move durable design into `.rsp/specs/design.md`
109
165
  4. Use `rsp add spec <name>` or `rsp add rules <name>` only when needed
@@ -111,38 +167,31 @@ Existing project with a rich `AGENTS.md`:
111
167
  AI-assisted setup:
112
168
 
113
169
  1. `npx -y @oevery/rsp init --agents-mode print --with-project-setup`
114
- 2. Let the AI adapt the managed block in `AGENTS.md`
115
- 3. Have the AI review and fill `.rsp/features/project-setup.md`
170
+ 2. Keep the managed block as generated and adapt only the surrounding human-owned content if needed
171
+ 3. Have the AI review and fill `.rsp/changes/project-setup.md`
116
172
  4. Have the AI fill `.rsp/specs/design.md`
117
173
  5. Run `rsp doctor`
118
174
 
119
175
  ## CLI
120
176
 
121
177
  ```text
122
- rsp init --agents-mode <mode> Scaffold .rsp/ + AGENTS.md
123
- rsp init --with-project-setup Also create .rsp/features/project-setup.md
178
+ rsp init --agents-mode <mode> Scaffold .rsp/ and ensure AGENTS.md contains the RSP entry block
179
+ rsp init --with-project-setup Also create .rsp/changes/project-setup.md
180
+ rsp update Refresh rules, repair the AGENTS block, and rebuild indices after upgrade
124
181
  rsp add rules <name> Create .rsp/rules/<name>.md
125
182
  rsp add spec <name> Create .rsp/specs/<name>.md and rebuild specs index
126
- rsp new <name> [summary] Create .rsp/features/<name>.md
127
- rsp close <name> Archive to .rsp/archives/ + update archive index
128
- rsp status [--active|--blocked|--stale <days>]
129
- Show project status summary with optional filters
130
- rsp check Validate feature files and dependency consistency
131
- rsp deps [--mermaid|--focus <name>|--reverse <name>]
132
- Show dependency summary, graph, or focused view
133
- rsp doctor Check setup health and common issues
134
- rsp specs-index Rebuild specs INDEX.md
135
- rsp archive-index Rebuild archives INDEX.md
183
+ rsp create <name> [summary] Create .rsp/changes/<name>.md
184
+ rsp focus <name> Mark an open change as currently focused
185
+ rsp unfocus <name> Remove an open change from the current focus set
186
+ rsp archive <name> Archive to .rsp/archives/ + update archive index
187
+ rsp status [--focused|--blocked|--stale <days>] [--json] [--verbose]
188
+ Show project status summary with focus-aware filters
189
+ rsp check [--json] [--verbose] Validate change files and lightly lint scenario structure
190
+ rsp doctor [--json] [--verbose]
191
+ Check setup health and common issues
136
192
  ```
137
193
 
138
- ## Doctor
139
-
140
- `rsp doctor` is read-only.
141
-
142
- - Checks `.rsp/`, `rules/rsp-rules.md`, `specs/design.md`, `specs/INDEX.md`, `archives/INDEX.md`, and the managed `AGENTS.md` block.
143
- - Verifies generated index signatures.
144
- - Verifies `active.d` markers and `features/` are in sync.
145
- - Exits non-zero when issues are found.
194
+ For exact rules, use `.rsp/rules/rsp-rules.md`. For operational durable-decision guidance, use `skills/rsp/SKILL.md`.
146
195
 
147
196
  ## Platform-agnostic
148
197
 
package/README.zh-CN.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  [English](./README.md) | 简体中文
4
4
 
5
- RSP = **Rules(规则)、Specs(规格)、Plans(计划)**。这是一个面向项目规则、项目级文档和特性计划的轻量级 AI 协作工作流。
5
+ RSP = **Rules、Specs、Plans**。这是一个面向长期项目知识与单文件 change 跟踪的轻量级 AI 协作工作流。
6
6
 
7
7
  ## 快速开始
8
8
 
@@ -15,17 +15,17 @@ npx -y @oevery/rsp doctor
15
15
 
16
16
  ```bash
17
17
  npx -y @oevery/rsp init --with-project-setup
18
- # 填写 .rsp/features/project-setup.md
18
+ # 填写 .rsp/changes/project-setup.md
19
19
  # 填写 .rsp/specs/design.md
20
20
  npx -y @oevery/rsp doctor
21
21
  ```
22
22
 
23
- ## 核心概念
23
+ ## 核心思路
24
24
 
25
25
  - `rules/` 存放长期稳定的约束。
26
- - `specs/` 存放项目级设计文档。
27
- - `features/` 存放进行中的工作。
28
- - `active.d/` 用空标记文件镜像活跃特性。
26
+ - `specs/` 存放项目级 source-of-truth 文档。
27
+ - `changes/` 以单文件格式存放 open work。
28
+ - `focus.d/` 用空标记文件镜像当前聚焦的 changes。
29
29
  - `archives/` 存放已完成工作。
30
30
 
31
31
  ```text
@@ -36,19 +36,27 @@ npx -y @oevery/rsp doctor
36
36
  ├── specs/
37
37
  │ ├── INDEX.md # 自动生成
38
38
  │ └── design.md
39
- ├── features/
39
+ ├── changes/
40
40
  │ └── <name>.md
41
- ├── active.d/
41
+ ├── focus.d/
42
42
  │ └── <name>
43
43
  └── archives/
44
44
  └── INDEX.md # 自动生成
45
45
  ```
46
46
 
47
+ ## 概念
48
+
49
+ - `specs/` 描述长期稳定的项目事实和当前认可的设计。
50
+ - `changes/` 描述 open work,包括 feature、fix、refactor、docs、ops 和 research。
51
+ - 每个 change 始终是单个 Markdown 文件,并包含 proposal、spec、design、tasks、verification 与 blockers 等明确 section。
52
+ - 完成后的 change 会移动到 `archives/`;若变更产出了长期知识,应在归档前同步写入 `specs/` 或 `rules/`。
53
+ - 所谓长期知识,只应包含稳定事实;不要把任务历史、排障笔记或一次性实现上下文提升到 `specs/` 或 `rules/`。
54
+
47
55
  ## 文件所有权
48
56
 
49
57
  - `AGENTS.md`:只有 `<!-- rsp:begin --> ... <!-- rsp:end -->` 受管块由 RSP 维护。
50
- - `.rsp/specs/INDEX.md`:自动生成,使用 `rsp specs-index` 重建。
51
- - `.rsp/archives/INDEX.md`:自动生成,使用 `rsp archive-index` 重建。
58
+ - `.rsp/specs/INDEX.md`:自动生成,使用 `rsp update` 重建。
59
+ - `.rsp/archives/INDEX.md`:自动生成,使用 `rsp update` 重建。
52
60
  - `.rsp/specs/design.md`:由 `rsp init` 创建,之后由项目维护。
53
61
  - `.rsp/rules/project-rules.md`:可选,仅在项目确有长期本地规则时创建。
54
62
  - 将长期架构、边界和跨模块技术约束放在 `.rsp/specs/design.md`。
@@ -63,22 +71,36 @@ npx -y @oevery/rsp doctor
63
71
  ## RSP Entry
64
72
 
65
73
  Read in order:
66
- 1. .rsp/rules/*.md
67
- 2. .rsp/specs/INDEX.md
68
- 3. .rsp/specs/design.md
69
- 4. .rsp/active.d/ and matching .rsp/features/*.md
74
+ 1. .rsp/rules/rsp-rules.md
75
+ 2. .rsp/focus.d/
76
+ 3. matching .rsp/changes/*.md for the focused entries
77
+ 4. .rsp/specs/design.md
78
+ 5. .rsp/specs/INDEX.md
79
+ 6. only the relevant additional .rsp/rules/*.md and .rsp/specs/*.md files
70
80
  <!-- rsp:end -->
71
81
  ```
72
82
 
73
83
  `rsp init --agents-mode <mode>`:
74
84
 
75
- - `managed`:插入/更新 `AGENTS.md` 中的受管块。
76
- - `skip`:只搭建 `.rsp/`。
77
- - `print`:搭建 `.rsp/` 并打印受管块。
85
+ - `managed`:在需要时创建 `AGENTS.md`,并插入或更新受管块。
86
+ - `print`:正常初始化,并额外打印最终的 `AGENTS.md` 内容。
78
87
 
79
88
  ## Skill
80
89
 
81
- 更完整的接入步骤、工作流说明和审计说明见 `skills/rsp/SKILL.md`。它适合按需加载,不应替代常驻核心规则。
90
+ 使用 `skills/rsp/SKILL.md` 获取逐步的 setup、workflow 和审查指导。它适合按需加载,而不是默认常驻。
91
+
92
+ 文档分层矩阵:
93
+
94
+ | Surface | 主要受众 | 职责 |
95
+ |---|---|---|
96
+ | `README.md` | 人类 | 概览、入门、示例 |
97
+ | `.rsp/rules/rsp-rules.md` | agent | 规范性的规则真相源 |
98
+ | `skills/rsp/SKILL.md` | agent | 应用这些规则的操作指南 |
99
+ | `AGENTS.md` | 人类与 agent | 帮助找到正确文件的导航入口 |
100
+
101
+ 通常应由人先读 `README.md`,而 agent 应把 `.rsp/rules/rsp-rules.md` 当作规范真相源。
102
+
103
+ 如果文档中写的是 `rsp <command>`,默认前提是你的环境里已经能直接运行 `rsp`;否则请使用 `npx -y @oevery/rsp <command>`。
82
104
 
83
105
  可选安装示例:
84
106
 
@@ -86,63 +108,84 @@ Read in order:
86
108
  npx skills add oevery/rsp --skill rsp
87
109
  ```
88
110
 
89
- 这个仓库发布的 skill 名称是 `rsp`,位于 `skills/rsp/`。
111
+ 本仓库发布了一个名为 `rsp` 的 skill,位于 `skills/rsp/`。
112
+
113
+ ## 工作模型
114
+
115
+ ```text
116
+ open → archived
117
+ ```
90
118
 
91
- 然后只在接入 RSP、审计设置或整理项目级 rules/specs 时加载这个 skill。
119
+ 各目录职责应保持单一且明确:
120
+
121
+ - `changes/`:open changes
122
+ - `focus.d/`:当前聚焦的 changes
123
+ - `archives/`:完成后的历史
124
+
125
+ 在 `open` 阶段,常见活动包括:
126
+
127
+ - `create`:创建并界定一个 change。
128
+ - `focus` / `unfocus`:调整当前聚焦的 open change。
129
+ - 直接编辑 change 文件,填写 section、勾选 tasks、记录设计决策。
130
+ - 在归档前判断是否需要 durable updates。
131
+
132
+ `archive` 会把已完成的工作归档到历史。`archive` 不会阻塞,只会给出 warning,最终判断留给 agent 或人工。
133
+
134
+ agent 应只把 `focus.d/` 中列出的 change 视为当前工作。`changes/` 中未聚焦的文件仍然是 open,但除非用户明确要求或重新 `focus`,否则不应被当作当前目标。
135
+
136
+ 关于 durable update 的决定,也就是某次变更是否产出了应该写入 `.rsp/specs/` 或 `.rsp/rules/` 的知识,本质上是语义判断,应由 RSP skill 或人工 reviewer 完成。
92
137
 
93
138
  ## 推荐工作流
94
139
 
95
140
  新项目:
96
141
 
97
142
  1. `npx -y @oevery/rsp init`
98
- 2. 优先使用 `npx -y @oevery/rsp init --with-project-setup`,或手动执行 `rsp new project-setup`
143
+ 2. 优先使用 `npx -y @oevery/rsp init --with-project-setup`,或手动执行 `rsp create project-setup`
99
144
  3. 填写 `.rsp/specs/design.md`
100
- 4. 只有在需要长期项目文档时才用 `rsp add spec <name>`
101
- 5. 只有在存在稳定本地规则时才用 `rsp add rules project-rules`
102
- 6. 使用 `rsp new <name>` 开始工作
145
+ 4. 仅在需要新的长期项目文档时使用 `rsp add spec <name>`
146
+ 5. 仅在项目存在稳定本地规则时使用 `rsp add rules project-rules`
147
+ 6. 使用 `rsp create <name>` 开始工作
148
+ 7. 如果要让某个已有 open change 成为当前工作,使用 `rsp focus <name>`
149
+ 8. 如果要将某个 change 移出当前焦点集合,使用 `rsp unfocus <name>`
150
+ 9. 直接编辑 change 文件并完成实现、勾选 tasks
151
+ 10. 使用 RSP skill 或人工 review 判断是否需要 durable updates
152
+ 11. 使用 `rsp archive <name>` 收尾
103
153
 
104
154
  已有复杂 `AGENTS.md` 的项目:
105
155
 
106
- 1. `npx -y @oevery/rsp init --agents-mode managed`
156
+ 1. `npx -y @oevery/rsp init`
107
157
  2. 保持受管块尽量薄
108
158
  3. 将长期设计收敛到 `.rsp/specs/design.md`
109
- 4. 需要时再用 `rsp add spec <name>` 或 `rsp add rules <name>`
159
+ 4. 需要时再使用 `rsp add spec <name>` 或 `rsp add rules <name>`
110
160
 
111
161
  AI 协助接入:
112
162
 
113
163
  1. `npx -y @oevery/rsp init --agents-mode print --with-project-setup`
114
- 2. 让 AI 处理 `AGENTS.md` 的受管块
115
- 3. 让 AI 审阅并填写 `.rsp/features/project-setup.md`
164
+ 2. 保持受管块原样,只在需要时调整周围由人维护的内容
165
+ 3. 让 AI 审阅并填写 `.rsp/changes/project-setup.md`
116
166
  4. 让 AI 填写 `.rsp/specs/design.md`
117
167
  5. 运行 `rsp doctor`
118
168
 
119
169
  ## CLI
120
170
 
121
171
  ```text
122
- rsp init --agents-mode <mode> 搭建 .rsp/ + AGENTS.md
123
- rsp init --with-project-setup 同时创建 .rsp/features/project-setup.md
172
+ rsp init --agents-mode <mode> 搭建 .rsp/,并确保 AGENTS.md 含有 RSP 入口块
173
+ rsp init --with-project-setup 同时创建 .rsp/changes/project-setup.md
174
+ rsp update 升级后刷新 rules、修复 AGENTS 受管块并重建各类索引
124
175
  rsp add rules <name> 创建 .rsp/rules/<name>.md
125
176
  rsp add spec <name> 创建 .rsp/specs/<name>.md 并重建 specs 索引
126
- rsp new <name> [summary] 创建 .rsp/features/<name>.md
127
- rsp close <name> 归档到 .rsp/archives/ + 更新归档索引
128
- rsp status [--active|--blocked|--stale <days>]
129
- 查看项目状态摘要,并支持轻量筛选
130
- rsp check 校验 feature 文件结构与依赖一致性
131
- rsp deps [--mermaid|--focus <name>|--reverse <name>]
132
- 查看依赖摘要、Mermaid 图或局部依赖视图
133
- rsp doctor 检查接入健康和常见问题
134
- rsp specs-index 重新生成 specs 索引
135
- rsp archive-index 重新生成 archives 索引
177
+ rsp create <name> [summary] 创建 .rsp/changes/<name>.md
178
+ rsp focus <name> 将一个 open change 标记为当前聚焦
179
+ rsp unfocus <name> 将一个 open change 移出当前聚焦集合
180
+ rsp archive <name> 归档到 .rsp/archives/ 并更新 archive index
181
+ rsp status [--focused|--blocked|--stale <days>] [--json] [--verbose]
182
+ 查看带有当前聚焦信息的项目状态摘要,并支持轻量筛选
183
+ rsp check [--json] [--verbose] 校验 change 文件,并对 scenario 结构做轻量 lint
184
+ rsp doctor [--json] [--verbose]
185
+ 检查接入健康和常见问题
136
186
  ```
137
187
 
138
- ## Doctor
139
-
140
- `rsp doctor` 是只读命令。
141
-
142
- - 检查 `.rsp/`、`rules/rsp-rules.md`、`specs/design.md`、`specs/INDEX.md`、`archives/INDEX.md` 以及 `AGENTS.md` 受管块。
143
- - 检查自动索引签名。
144
- - 检查 `active.d` 标记与 `features/` 是否一致。
145
- - 发现问题会以非零退出码结束。
188
+ 精确规则以 `.rsp/rules/rsp-rules.md` 为准;durable decision 的操作指导以 `skills/rsp/SKILL.md` 为准。
146
189
 
147
190
  ## 工具无关
148
191