🔧 chore(playbook): align repo with latest workflow
lsp-server ci / build-and-test (push) Failing after 0s
lsp-server ci / build-and-test (push) Failing after 0s
sync playbook-managed rules and prompts. migrate memory-bank to the new structure and move plans to docs/superpowers/plans. keep product README files untouched.
This commit is contained in:
@@ -141,4 +141,35 @@ VSCode 扩展作为纯客户端,通过 stdio 与独立的 LSP 服务器进程
|
||||
|
||||
---
|
||||
|
||||
**最后更新**:2026-02-02
|
||||
## ADR-007: 使用 vendored playbook 与主循环维护代理文档
|
||||
|
||||
**日期**: 2026-05-24
|
||||
**状态**: 已采纳
|
||||
|
||||
### 决策
|
||||
|
||||
将 `docs/standards/playbook/` 作为 vendored 快照,通过
|
||||
`git subtree` 升级;仓库内规则、提示词和 `.agents/` 通过
|
||||
`python docs/standards/playbook/scripts/playbook.py -config playbook.toml`
|
||||
同步;后续实施计划统一放到 `docs/superpowers/plans/`,
|
||||
并使用 `main_loop.py claim / finish` 维护 `memory-bank/progress.md`
|
||||
状态块。
|
||||
|
||||
### 理由
|
||||
|
||||
- 需要与 playbook 上游架构保持强对齐,减少手工漂移
|
||||
- 需要把框架管理文件与项目自维护文件分清边界
|
||||
- 需要统一 Plan 留痕和状态流转,避免旧 `docs/plans/`
|
||||
与旧 `plan-status` 机制继续分叉
|
||||
|
||||
### 影响
|
||||
|
||||
- 升级 playbook 时必须先做 subtree,再执行同步脚本
|
||||
- `AGENT_RULES.local.md` 与 `memory-bank/*.md` 仍由项目自行维护
|
||||
- 产品 README 不再承载 playbook 对齐信息
|
||||
- 后续会话应优先读取 `docs/superpowers/plans/` 与新的
|
||||
`workflow-state` / `plan-status` 状态块
|
||||
|
||||
---
|
||||
|
||||
**最后更新**:2026-05-24
|
||||
|
||||
Reference in New Issue
Block a user