spec-manager 0.1.0

package/templates/agents/CODEBUDDY.md

@@ -0,0 +1,23 @@
+# Spec-Driven Development
+
+This project uses `spec-manager` for local-first spec-driven development. CodeBuddy should use the project skill at `.codebuddy/skills/spec-manager/` when the user asks for `/spec-manager` or asks to follow the spec-manager workflow.
+
+## Rules
+
+- Feature work MUST go through `spec-manager`; avoid direct code edits for non-trivial work.
+- New or non-trivial work follows L1 PRD -> L2 Design -> L3 Impl -> Agent Task.
+- Never write implementation code unless the relevant L3 spec is `frozen`.
+- `confirm` and `freeze` are user review actions. Stop after writing spec content and wait for explicit approval.
+- Before creating a new spec, inspect existing specs and decisions.
+- Before code edits, read the relevant frozen L3 spec and create/start an Agent Task.
+- Record each execution step with `spec-manager task step`; complete with `spec-manager task complete`.
+
+## Useful Commands
+
+```bash
+spec-manager project status
+spec-manager spec list
+spec-manager spec show <code> --include-content
+spec-manager decision list --topic <topic>
+spec-manager task list --topic <topic>
+```

package/templates/agents/codebuddy-skill/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: spec-manager
+description: Spec-driven project iteration workflow: L1 PRD -> L2 Design -> L3 Impl -> Agent Task, with human review gates at each layer.
+allowed-tools: Read, Write, Grep, Glob, Bash(spec-manager:*), Bash(git:*)
+---
+
+# spec-manager
+
+Use this skill when the user invokes `/spec-manager`, asks for a new feature, PRD, technical design, implementation spec, agent task, iteration plan, test plan, release notes, runbook, postmortem, ADR, or delta change.
+
+## Entry Points
+
+- `/spec-manager <request>` — start from the user's requirement and route to the right subskill.
+- `/spec-manager run <taskId>` — execute an existing Agent Task.
+
+## Route Table
+
+| Signal | Subskill |
+|---|---|
+| typo / one-line edit / log level | [subskills/quick.md](subskills/quick.md) |
+| inspect / list / search / stats | [subskills/research.md](subskills/research.md) |
+| requirement / new feature / user story | [subskills/prd.md](subskills/prd.md) |
+| technical plan / architecture / API design | [subskills/design.md](subskills/design.md) |
+| implementation / coding / planJson | [subskills/impl.md](subskills/impl.md) |
+| plan / milestone / schedule | [subskills/plan.md](subskills/plan.md) |
+| test plan / QA / cases | [subskills/testplan.md](subskills/testplan.md) |
+| release / changelog | [subskills/release.md](subskills/release.md) |
+| runbook / oncall | [subskills/runbook.md](subskills/runbook.md) |
+| postmortem / RCA | [subskills/postmortem.md](subskills/postmortem.md) |
+| ADR / why choose X | [subskills/adr.md](subskills/adr.md) |
+| delta / change / increment | [subskills/change.md](subskills/change.md) |
+
+If intent is unclear, ask the user one concise clarification question before taking action.
+
+## Hard Rules
+
+- Do not write implementation code without a frozen L3 spec.
+- Stop after writing L1/L2/L3 content and wait for explicit user approval.
+- Status transitions (`confirm` and `freeze`) are user actions.
+- Agent Tasks can only be created from frozen L3 specs.
+- Before code edits, read the relevant spec and inspect the actual source files.
+
+## Bundled References
+
+- Rules: [rules/](rules/)
+- Templates: [templates/](templates/)

package/templates/decision.md

@@ -0,0 +1,42 @@
+<!-- ========== Stage Charter: Decision Card ==========
+Value: 知识沉淀 — 回答"为什么这么做/不这么做",支撑后续 L1 的 Q4 历史决策查询
+Time horizon: 长期(直到被 supersede)
+Target reader: 未来 AI agent 在做类似需求时的参照(尤其 L1 PRE-WRITE Q4)
+Must NOT have:
+  - 文件路径 / DDL / planJson → 不属于本层
+  - 详细 trade-off / 备选方案 → 走 ADR
+  - 设计原则 → 写在 L1 正文的"设计原则"段落
+Soft boundary: 决策卡片是结构化记录;多决策关联同一 topic 时用 supersededById 串联
+
+Lifecycle:
+  active (新建) → superseded (被新决策取代,supersede 命令)
+                  → partial  (部分被取代,set-partial 命令,需 --reason)
+
+触发条件(R18): L1 spec 状态推进到 implemented 后,**必须**至少 1 张
+查询入口: `spec-manager decision list --topic <topic> --criteria AC-1`
+========== -->
+
+# {{id}} — {{what}}
+
+> 关联 spec: **{{docCode}}**  |  topic: **{{topic}}**  |  状态: **{{status}}**{{supersededByLine}}
+
+## 决定
+
+<决定了什么,1-3 句话。不要写"我们决定..."这种铺垫,直接给结论。≤500 字>
+
+## 为什么
+
+<为什么做这个决定。引用证据(数据/事故/约束/权衡),≤500 字。可选,但强烈建议填写>
+
+## 影响的验收标准
+
+<这条决策改变了哪些 AC,以及改变方式(新增/修改/废止)。AC 编号必须与 L1 spec 验收标准段落中的编号一致。可选,但建议填写以支持 requirement 维度追溯>
+
+- AC-...
+- AC-...
+
+## 关联
+
+- spec: {{docCode}}
+- topic: {{topic}}
+- 状态: {{status}}{{supersededLink}}