@oevery/rsp 1.1.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 +110 -45
- package/README.zh-CN.md +107 -48
- package/dist/cli.mjs +1372 -920
- package/package.json +8 -5
- package/rules/rsp-rules.md +79 -81
- package/skills/rsp/SKILL.md +137 -0
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
|
|
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
|
|
|
@@ -11,12 +11,21 @@ npx -y @oevery/rsp init
|
|
|
11
11
|
npx -y @oevery/rsp doctor
|
|
12
12
|
```
|
|
13
13
|
|
|
14
|
+
Recommended bootstrap flow:
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
npx -y @oevery/rsp init --with-project-setup
|
|
18
|
+
# fill .rsp/changes/project-setup.md
|
|
19
|
+
# fill .rsp/specs/design.md
|
|
20
|
+
npx -y @oevery/rsp doctor
|
|
21
|
+
```
|
|
22
|
+
|
|
14
23
|
## Core idea
|
|
15
24
|
|
|
16
25
|
- `rules/` stores durable constraints.
|
|
17
|
-
- `specs/` stores project-level
|
|
18
|
-
- `
|
|
19
|
-
- `
|
|
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.
|
|
20
29
|
- `archives/` stores completed work.
|
|
21
30
|
|
|
22
31
|
```text
|
|
@@ -27,21 +36,31 @@ npx -y @oevery/rsp doctor
|
|
|
27
36
|
├── specs/
|
|
28
37
|
│ ├── INDEX.md # auto-generated
|
|
29
38
|
│ └── design.md
|
|
30
|
-
├──
|
|
39
|
+
├── changes/
|
|
31
40
|
│ └── <name>.md
|
|
32
|
-
├──
|
|
41
|
+
├── focus.d/
|
|
33
42
|
│ └── <name>
|
|
34
43
|
└── archives/
|
|
35
44
|
└── INDEX.md # auto-generated
|
|
36
45
|
```
|
|
37
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
|
+
|
|
38
55
|
## File ownership
|
|
39
56
|
|
|
40
57
|
- `AGENTS.md`: only the `<!-- rsp:begin --> ... <!-- rsp:end -->` block is managed by RSP.
|
|
41
|
-
- `.rsp/specs/INDEX.md`: auto-generated. Rebuild with `rsp
|
|
42
|
-
- `.rsp/archives/INDEX.md`: auto-generated. Rebuild with `rsp
|
|
58
|
+
- `.rsp/specs/INDEX.md`: auto-generated. Rebuild with `rsp update`.
|
|
59
|
+
- `.rsp/archives/INDEX.md`: auto-generated. Rebuild with `rsp update`.
|
|
43
60
|
- `.rsp/specs/design.md`: created by `rsp init`, then owned by the project.
|
|
44
61
|
- `.rsp/rules/project-rules.md`: optional; create only when the project has durable local rules.
|
|
62
|
+
- Keep durable architecture, boundaries, and cross-cutting technical constraints in `.rsp/specs/design.md`.
|
|
63
|
+
- Keep stable workflow rules, validation expectations, and local operating constraints in `.rsp/rules/project-rules.md`.
|
|
45
64
|
|
|
46
65
|
## AGENTS integration
|
|
47
66
|
|
|
@@ -52,81 +71,127 @@ Managed block example:
|
|
|
52
71
|
## RSP Entry
|
|
53
72
|
|
|
54
73
|
Read in order:
|
|
55
|
-
1. .rsp/rules
|
|
56
|
-
2. .rsp/
|
|
57
|
-
3. .rsp/
|
|
58
|
-
4. .rsp/
|
|
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
|
|
59
80
|
<!-- rsp:end -->
|
|
60
81
|
```
|
|
61
82
|
|
|
62
83
|
`rsp init --agents-mode <mode>`:
|
|
63
84
|
|
|
64
|
-
- `managed`: insert/update the managed block
|
|
65
|
-
- `
|
|
66
|
-
- `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.
|
|
67
87
|
|
|
68
88
|
## Skill
|
|
69
89
|
|
|
70
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.
|
|
71
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
|
+
|
|
72
111
|
Example optional installation flow:
|
|
73
112
|
|
|
74
113
|
```bash
|
|
75
|
-
npx skills add
|
|
114
|
+
npx skills add oevery/rsp --skill rsp
|
|
76
115
|
```
|
|
77
116
|
|
|
78
|
-
|
|
117
|
+
This repository publishes a skill named `rsp` under `skills/rsp/`.
|
|
118
|
+
|
|
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.
|
|
79
143
|
|
|
80
144
|
## Recommended workflow
|
|
81
145
|
|
|
82
146
|
New project:
|
|
83
147
|
|
|
84
148
|
1. `npx -y @oevery/rsp init`
|
|
85
|
-
2.
|
|
86
|
-
3.
|
|
87
|
-
4. Use `rsp add
|
|
88
|
-
5.
|
|
149
|
+
2. Prefer `npx -y @oevery/rsp init --with-project-setup`, or run `rsp create project-setup` manually
|
|
150
|
+
3. Fill `.rsp/specs/design.md`
|
|
151
|
+
4. Use `rsp add spec <name>` only when a new durable project doc is needed
|
|
152
|
+
5. Use `rsp add rules project-rules` only when the project has stable local rules
|
|
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>`
|
|
89
159
|
|
|
90
160
|
Existing project with a rich `AGENTS.md`:
|
|
91
161
|
|
|
92
|
-
1. `npx -y @oevery/rsp init
|
|
162
|
+
1. `npx -y @oevery/rsp init`
|
|
93
163
|
2. Keep the managed block thin
|
|
94
164
|
3. Move durable design into `.rsp/specs/design.md`
|
|
95
165
|
4. Use `rsp add spec <name>` or `rsp add rules <name>` only when needed
|
|
96
166
|
|
|
97
167
|
AI-assisted setup:
|
|
98
168
|
|
|
99
|
-
1. `npx -y @oevery/rsp init --agents-mode print`
|
|
100
|
-
2.
|
|
101
|
-
3. Have the AI fill `.rsp/
|
|
102
|
-
4.
|
|
169
|
+
1. `npx -y @oevery/rsp init --agents-mode print --with-project-setup`
|
|
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`
|
|
172
|
+
4. Have the AI fill `.rsp/specs/design.md`
|
|
173
|
+
5. Run `rsp doctor`
|
|
103
174
|
|
|
104
175
|
## CLI
|
|
105
176
|
|
|
106
177
|
```text
|
|
107
|
-
rsp init --agents-mode <mode> Scaffold .rsp/
|
|
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
|
|
108
181
|
rsp add rules <name> Create .rsp/rules/<name>.md
|
|
109
182
|
rsp add spec <name> Create .rsp/specs/<name>.md and rebuild specs index
|
|
110
|
-
rsp
|
|
111
|
-
rsp
|
|
112
|
-
rsp
|
|
113
|
-
|
|
114
|
-
rsp
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
rsp doctor
|
|
118
|
-
|
|
119
|
-
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
|
|
120
192
|
```
|
|
121
193
|
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
`rsp doctor` is read-only.
|
|
125
|
-
|
|
126
|
-
- Checks `.rsp/`, `rules/rsp-rules.md`, `specs/design.md`, `specs/INDEX.md`, `archives/INDEX.md`, and the managed `AGENTS.md` block.
|
|
127
|
-
- Verifies generated index signatures.
|
|
128
|
-
- Verifies `active.d` markers and `features/` are in sync.
|
|
129
|
-
- 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`.
|
|
130
195
|
|
|
131
196
|
## Platform-agnostic
|
|
132
197
|
|
package/README.zh-CN.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[English](./README.md) | 简体中文
|
|
4
4
|
|
|
5
|
-
RSP = **Rules
|
|
5
|
+
RSP = **Rules、Specs、Plans**。这是一个面向长期项目知识与单文件 change 跟踪的轻量级 AI 协作工作流。
|
|
6
6
|
|
|
7
7
|
## 快速开始
|
|
8
8
|
|
|
@@ -11,12 +11,21 @@ npx -y @oevery/rsp init
|
|
|
11
11
|
npx -y @oevery/rsp doctor
|
|
12
12
|
```
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
推荐启动流程：
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
npx -y @oevery/rsp init --with-project-setup
|
|
18
|
+
# 填写 .rsp/changes/project-setup.md
|
|
19
|
+
# 填写 .rsp/specs/design.md
|
|
20
|
+
npx -y @oevery/rsp doctor
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## 核心思路
|
|
15
24
|
|
|
16
25
|
- `rules/` 存放长期稳定的约束。
|
|
17
|
-
- `specs/`
|
|
18
|
-
- `
|
|
19
|
-
- `
|
|
26
|
+
- `specs/` 存放项目级 source-of-truth 文档。
|
|
27
|
+
- `changes/` 以单文件格式存放 open work。
|
|
28
|
+
- `focus.d/` 用空标记文件镜像当前聚焦的 changes。
|
|
20
29
|
- `archives/` 存放已完成工作。
|
|
21
30
|
|
|
22
31
|
```text
|
|
@@ -27,21 +36,31 @@ npx -y @oevery/rsp doctor
|
|
|
27
36
|
├── specs/
|
|
28
37
|
│ ├── INDEX.md # 自动生成
|
|
29
38
|
│ └── design.md
|
|
30
|
-
├──
|
|
39
|
+
├── changes/
|
|
31
40
|
│ └── <name>.md
|
|
32
|
-
├──
|
|
41
|
+
├── focus.d/
|
|
33
42
|
│ └── <name>
|
|
34
43
|
└── archives/
|
|
35
44
|
└── INDEX.md # 自动生成
|
|
36
45
|
```
|
|
37
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
|
+
|
|
38
55
|
## 文件所有权
|
|
39
56
|
|
|
40
57
|
- `AGENTS.md`：只有 `<!-- rsp:begin --> ... <!-- rsp:end -->` 受管块由 RSP 维护。
|
|
41
|
-
- `.rsp/specs/INDEX.md`：自动生成，使用 `rsp
|
|
42
|
-
- `.rsp/archives/INDEX.md`：自动生成，使用 `rsp
|
|
58
|
+
- `.rsp/specs/INDEX.md`：自动生成，使用 `rsp update` 重建。
|
|
59
|
+
- `.rsp/archives/INDEX.md`：自动生成，使用 `rsp update` 重建。
|
|
43
60
|
- `.rsp/specs/design.md`：由 `rsp init` 创建，之后由项目维护。
|
|
44
61
|
- `.rsp/rules/project-rules.md`：可选，仅在项目确有长期本地规则时创建。
|
|
62
|
+
- 将长期架构、边界和跨模块技术约束放在 `.rsp/specs/design.md`。
|
|
63
|
+
- 将稳定的工作流规则、验证要求和本地运行约束放在 `.rsp/rules/project-rules.md`。
|
|
45
64
|
|
|
46
65
|
## AGENTS 接入
|
|
47
66
|
|
|
@@ -52,81 +71,121 @@ npx -y @oevery/rsp doctor
|
|
|
52
71
|
## RSP Entry
|
|
53
72
|
|
|
54
73
|
Read in order:
|
|
55
|
-
1. .rsp/rules
|
|
56
|
-
2. .rsp/
|
|
57
|
-
3. .rsp/
|
|
58
|
-
4. .rsp/
|
|
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
|
|
59
80
|
<!-- rsp:end -->
|
|
60
81
|
```
|
|
61
82
|
|
|
62
83
|
`rsp init --agents-mode <mode>`：
|
|
63
84
|
|
|
64
|
-
- `managed
|
|
65
|
-
- `
|
|
66
|
-
- `print`：搭建 `.rsp/` 并打印受管块。
|
|
85
|
+
- `managed`：在需要时创建 `AGENTS.md`，并插入或更新受管块。
|
|
86
|
+
- `print`：正常初始化，并额外打印最终的 `AGENTS.md` 内容。
|
|
67
87
|
|
|
68
88
|
## Skill
|
|
69
89
|
|
|
70
|
-
|
|
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>`。
|
|
71
104
|
|
|
72
105
|
可选安装示例：
|
|
73
106
|
|
|
74
107
|
```bash
|
|
75
|
-
npx skills add
|
|
108
|
+
npx skills add oevery/rsp --skill rsp
|
|
76
109
|
```
|
|
77
110
|
|
|
78
|
-
|
|
111
|
+
本仓库发布了一个名为 `rsp` 的 skill，位于 `skills/rsp/`。
|
|
112
|
+
|
|
113
|
+
## 工作模型
|
|
114
|
+
|
|
115
|
+
```text
|
|
116
|
+
open → archived
|
|
117
|
+
```
|
|
118
|
+
|
|
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 完成。
|
|
79
137
|
|
|
80
138
|
## 推荐工作流
|
|
81
139
|
|
|
82
140
|
新项目：
|
|
83
141
|
|
|
84
142
|
1. `npx -y @oevery/rsp init`
|
|
85
|
-
2.
|
|
86
|
-
3.
|
|
87
|
-
4.
|
|
88
|
-
5.
|
|
143
|
+
2. 优先使用 `npx -y @oevery/rsp init --with-project-setup`，或手动执行 `rsp create project-setup`
|
|
144
|
+
3. 填写 `.rsp/specs/design.md`
|
|
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>` 收尾
|
|
89
153
|
|
|
90
154
|
已有复杂 `AGENTS.md` 的项目：
|
|
91
155
|
|
|
92
|
-
1. `npx -y @oevery/rsp init
|
|
156
|
+
1. `npx -y @oevery/rsp init`
|
|
93
157
|
2. 保持受管块尽量薄
|
|
94
158
|
3. 将长期设计收敛到 `.rsp/specs/design.md`
|
|
95
|
-
4.
|
|
159
|
+
4. 需要时再使用 `rsp add spec <name>` 或 `rsp add rules <name>`
|
|
96
160
|
|
|
97
161
|
AI 协助接入：
|
|
98
162
|
|
|
99
|
-
1. `npx -y @oevery/rsp init --agents-mode print`
|
|
100
|
-
2.
|
|
101
|
-
3. 让 AI
|
|
102
|
-
4.
|
|
163
|
+
1. `npx -y @oevery/rsp init --agents-mode print --with-project-setup`
|
|
164
|
+
2. 保持受管块原样，只在需要时调整周围由人维护的内容
|
|
165
|
+
3. 让 AI 审阅并填写 `.rsp/changes/project-setup.md`
|
|
166
|
+
4. 让 AI 填写 `.rsp/specs/design.md`
|
|
167
|
+
5. 运行 `rsp doctor`
|
|
103
168
|
|
|
104
169
|
## CLI
|
|
105
170
|
|
|
106
171
|
```text
|
|
107
|
-
rsp init --agents-mode <mode> 搭建 .rsp
|
|
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 受管块并重建各类索引
|
|
108
175
|
rsp add rules <name> 创建 .rsp/rules/<name>.md
|
|
109
176
|
rsp add spec <name> 创建 .rsp/specs/<name>.md 并重建 specs 索引
|
|
110
|
-
rsp
|
|
111
|
-
rsp
|
|
112
|
-
rsp
|
|
113
|
-
|
|
114
|
-
rsp
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
rsp doctor
|
|
118
|
-
|
|
119
|
-
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
|
+
检查接入健康和常见问题
|
|
120
186
|
```
|
|
121
187
|
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
`rsp doctor` 是只读命令。
|
|
125
|
-
|
|
126
|
-
- 检查 `.rsp/`、`rules/rsp-rules.md`、`specs/design.md`、`specs/INDEX.md`、`archives/INDEX.md` 以及 `AGENTS.md` 受管块。
|
|
127
|
-
- 检查自动索引签名。
|
|
128
|
-
- 检查 `active.d` 标记与 `features/` 是否一致。
|
|
129
|
-
- 发现问题会以非零退出码结束。
|
|
188
|
+
精确规则以 `.rsp/rules/rsp-rules.md` 为准；durable decision 的操作指导以 `skills/rsp/SKILL.md` 为准。
|
|
130
189
|
|
|
131
190
|
## 工具无关
|
|
132
191
|
|