spec-manager 0.1.0 → 0.1.1

package/templates/agent-plan.json

@@ -3,11 +3,12 @@
   "_constraints": [
     "step 1 必须是上下文收集(读 L3 spec + 父 L2 + 历史任务)",
     "末步必须是可执行的验证命令(R10)",
+    "coveredSpecs 必须包含当前 L3 specCode；若覆盖多条 L3,列出所有 specCode",
     "单 Agent Task = 单 L3 spec,步数 ≤ 20(R11);超 16 步必拆 L3",
     "每步 name 必须含 verb+object+file,禁止'优化/改进/处理'等模糊动词",
     "stepType 仅限 llm_call / mcp_tool / human_gate"
   ],
-  "coveredSpecs": ["2026-06-04-c3d4e5"],
+  "coveredSpecs": ["<current-L3-specCode>"],
   "steps": [
     {"stepNo": 1, "stepType": "mcp_tool", "name": "上下文收集: spec-manager spec show L3 + 父 L2 + 读 templates/agent-plan.json"},
     {"stepNo": 2, "stepType": "mcp_tool", "name": "编辑 <ServiceName>.java 新增方法 <verb>"},

package/templates/agents/AGENTS.md

@@ -4,14 +4,16 @@ This file is the spec-manager skill-like entrypoint for Codex, OpenCode, and oth
 
 This project uses `spec-manager` for local-first spec-driven development. Specs, tasks, decisions, changes, and audit data are stored as markdown/JSON files in the repository.
 
-## Mandatory Workflow
+## Unified Rules
 
-- Feature work MUST go through `spec-manager`; do not jump directly from a user request to implementation code.
-- 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`.
-- `draft -> confirmed` and `confirmed -> frozen` are user review actions. After writing spec content, stop and wait for explicit user approval.
+- Feature work MUST go through `spec-manager`.
+- New or non-trivial work follows L1 -> L2 -> L3 -> Agent Task.
+- Never write implementation code without a frozen L3 spec.
+- L1/L2 approval advances `draft -> confirmed`; one explicit L3 approval (an explicit user approval) advances `draft -> frozen`.
 - Before creating a new spec, inspect existing specs and decisions with `spec-manager spec list` and `spec-manager decision list --topic <topic>`.
-- Before code edits, read the relevant frozen L3 spec and create/start an Agent Task.
+- Before code edits, read the frozen L3 spec and create/start an Agent Task.
+- planJson `coveredSpecs` MUST include the current L3 specCode.
+- Validate L3 markdown plans with `spec-manager spec validate-plan --from-spec <L3-code>`.
 - Record execution with `spec-manager task step`; finish with `spec-manager task complete`.
 
 ## Common Commands

package/templates/agents/CLAUDE.md

@@ -2,10 +2,14 @@
 
 This project uses `spec-manager` via the `/spec-manager` skill.
 
-- All feature work MUST go through `/spec-manager`; no direct code changes for non-trivial work.
+- Feature work MUST go through `spec-manager`.
+- New or non-trivial work follows L1 -> L2 -> L3 -> Agent Task.
 - Never write implementation code without a frozen L3 spec.
-- Never skip human review gates. L1, L2, and L3 each require explicit user approval.
-- Status transitions (`confirm` and `freeze`) are user actions, not AI actions.
+- L1/L2 approval advances `draft -> confirmed`; one explicit L3 approval (an explicit user approval) advances `draft -> frozen`.
+- Before code edits, read the frozen L3 spec and create/start an Agent Task.
+- planJson `coveredSpecs` MUST include the current L3 specCode.
+- Validate L3 markdown plans with `spec-manager spec validate-plan --from-spec <L3-code>`.
+- Record execution with `spec-manager task step`; finish with `spec-manager task complete`.
 - For research, prefer `spec-manager spec show` metadata first, then `--include-content` when full context is required.
 
 Use the installed `.claude/skills/spec-manager/` skill when the user invokes `/spec-manager` or approves the next spec-manager step.

package/templates/agents/CODEBUDDY.md

@@ -2,15 +2,17 @@
 
 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
+## Unified 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.
+- Feature work MUST go through `spec-manager`.
+- New or non-trivial work follows L1 -> L2 -> L3 -> Agent Task.
+- Never write implementation code without a frozen L3 spec.
+- L1/L2 approval advances `draft -> confirmed`; one explicit L3 approval (an explicit user approval) advances `draft -> frozen`.
 - 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`.
+- Before code edits, read the frozen L3 spec and create/start an Agent Task.
+- planJson `coveredSpecs` MUST include the current L3 specCode.
+- Validate L3 markdown plans with `spec-manager spec validate-plan --from-spec <L3-code>`.
+- Record execution with `spec-manager task step`; finish with `spec-manager task complete`.
 
 ## Useful Commands
 

package/templates/agents/CURSOR.md

@@ -0,0 +1,28 @@
+# spec-manager Workflow Capsule
+
+This file is the spec-manager entrypoint for Cursor. Cursor reads project rules from `.cursorrules`; route feature work through `spec-manager`.
+
+This project uses `spec-manager` for local-first spec-driven development. Specs, tasks, decisions, changes, and audit data are stored as markdown/JSON files in the repository.
+
+## Unified Rules
+
+- Feature work MUST go through `spec-manager`.
+- New or non-trivial work follows L1 -> L2 -> L3 -> Agent Task.
+- Never write implementation code without a frozen L3 spec.
+- L1/L2 approval advances `draft -> confirmed`; one explicit L3 approval (an explicit user approval) advances `draft -> frozen`.
+- Before code edits, read the frozen L3 spec and create/start an Agent Task.
+- planJson `coveredSpecs` MUST include the current L3 specCode.
+- Validate L3 markdown plans with `spec-manager spec validate-plan --from-spec <L3-code>`.
+- Record execution with `spec-manager task step`; finish with `spec-manager task complete`.
+
+## Common 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>
+```
+
+When the user asks for `/spec-manager <request>` or asks to use spec-manager, treat it as a request to follow this workflow.

package/templates/agents/WINDSURF.md

@@ -0,0 +1,28 @@
+# spec-manager Workflow Capsule
+
+This file is the spec-manager entrypoint for Windsurf. Windsurf reads project rules from `.windsurfrules`; route feature work through `spec-manager`.
+
+This project uses `spec-manager` for local-first spec-driven development. Specs, tasks, decisions, changes, and audit data are stored as markdown/JSON files in the repository.
+
+## Unified Rules
+
+- Feature work MUST go through `spec-manager`.
+- New or non-trivial work follows L1 -> L2 -> L3 -> Agent Task.
+- Never write implementation code without a frozen L3 spec.
+- L1/L2 approval advances `draft -> confirmed`; one explicit L3 approval (an explicit user approval) advances `draft -> frozen`.
+- Before code edits, read the frozen L3 spec and create/start an Agent Task.
+- planJson `coveredSpecs` MUST include the current L3 specCode.
+- Validate L3 markdown plans with `spec-manager spec validate-plan --from-spec <L3-code>`.
+- Record execution with `spec-manager task step`; finish with `spec-manager task complete`.
+
+## Common 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>
+```
+
+When the user asks for `/spec-manager <request>` or asks to use spec-manager, treat it as a request to follow this workflow.

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

@@ -13,6 +13,17 @@ Use this skill when the user invokes `/spec-manager`, asks for a new feature, PR
 - `/spec-manager <request>` — start from the user's requirement and route to the right subskill.
 - `/spec-manager run <taskId>` — execute an existing Agent Task.
 
+## Unified Rules
+
+- Feature work MUST go through `spec-manager`.
+- New or non-trivial work follows L1 -> L2 -> L3 -> Agent Task.
+- Never write implementation code without a frozen L3 spec.
+- L1/L2 approval advances `draft -> confirmed`; one explicit L3 approval (an explicit user approval) advances `draft -> frozen`.
+- Before code edits, read the frozen L3 spec and create/start an Agent Task.
+- planJson `coveredSpecs` MUST include the current L3 specCode.
+- Validate L3 markdown plans with `spec-manager spec validate-plan --from-spec <L3-code>`.
+- Record execution with `spec-manager task step`; finish with `spec-manager task complete`.
+
 ## Route Table
 
 | Signal | Subskill |
@@ -36,7 +47,7 @@ If intent is unclear, ask the user one concise clarification question before tak
 
 - 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.
+- Status transitions are user actions; one L3 `confirm` approval advances directly to frozen.
 - Agent Tasks can only be created from frozen L3 specs.
 - Before code edits, read the relevant spec and inspect the actual source files.