prizmkit 1.0.35 → 1.0.58

package/bundled/team/prizm-dev-team.json

@@ -1,46 +1,32 @@
 {
   "name": "prizm-dev-team",
   "team_name": "prizm-dev-team",
-  "description": "PrizmKit-integrated Multi-Agent software development team. 4 specialized agents (Coordinator, PM, Dev, Reviewer) following PrizmKit spec-driven workflow with 7-phase pipeline and 4 checkpoints.",
+  "description": "PrizmKit-integrated Multi-Agent software development team. 2 specialized agents (Dev, Reviewer) following PrizmKit spec-driven workflow with 7-phase pipeline and 4 checkpoints.",
   "lead": "team-lead",
   "communication": {
     "protocol": "SendMessage",
     "routing": "mesh",
-    "note": "Teammates 间通过 SendMessage 直接通信，关键消息同时通知 Coordinator"
+    "note": "Teammates 间通过 SendMessage 直接通信，关键消息同时通知 Orchestrator"
   },
   "members": [
     {
       "name": "team-lead",
       "role": "lead",
-      "agentDefinition": "prizm-dev-team-coordinator",
+      "agentDefinition": "prizm-dev-team-dev",
       "subscriptions": []
     },
-    {
-      "name": "coordinator",
-      "role": "coordinator",
-      "agentDefinition": "prizm-dev-team-coordinator",
-      "prompt": "You are the Coordinator Agent of the prizm-dev-team. Orchestrate the 7-phase pipeline (init → specify+plan+tasks → analyze → implement → review → summarize → commit). Manage checkpoints CP-0 through CP-3, coordinate PM/Dev/Reviewer agents. Follow PrizmKit workflow.",
-      "subscriptions": ["*"]
-    },
-    {
-      "name": "pm",
-      "role": "pm",
-      "agentDefinition": "prizm-dev-team-pm",
-      "prompt": "You are the PM Agent of the prizm-dev-team. In a single session, use prizmkit.specify/clarify/plan/tasks to create spec.md, plan.md, and tasks.md. All artifacts go under .prizmkit/specs/###-feature-name/.",
-      "subscriptions": ["*"]
-    },
     {
       "name": "dev",
       "role": "developer",
       "agentDefinition": "prizm-dev-team-dev",
-      "prompt": "You are a Dev Agent of the prizm-dev-team. Follow prizmkit.implement workflow with TDD. Read tasks.md/plan.md/spec.md, implement task-by-task, mark completed tasks [x]. Check .prizm-docs/ TRAPS before implementing.",
+      "prompt": "You are a Dev Agent of the prizm-dev-team. Follow /prizmkit-implement workflow with TDD. Read tasks.md/plan.md/spec.md, implement task-by-task, mark completed tasks [x]. Check .prizm-docs/ TRAPS before implementing.",
       "subscriptions": ["*"]
     },
     {
       "name": "reviewer",
       "role": "reviewer",
       "agentDefinition": "prizm-dev-team-reviewer",
-      "prompt": "You are the Reviewer Agent of the prizm-dev-team. In Phase 4: run prizmkit.analyze for cross-document consistency. In Phase 6: run prizmkit.code-review for spec compliance and code quality, write and execute integration tests.",
+      "prompt": "You are the Reviewer Agent of the prizm-dev-team. In Phase 4: run /prizmkit-analyze for cross-document consistency. In Phase 6: run /prizmkit-code-review for spec compliance and code quality, write and execute integration tests.",
       "subscriptions": ["*"]
     }
   ]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.0.35",
+  "version": "1.0.58",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {

package/src/clean.js

@@ -98,9 +98,7 @@ export async function runClean(directory, options = {}) {
 
   // Agent file names installed by PrizmKit (union of hardcoded + manifest)
   const knownAgentFiles = [
-    'prizm-dev-team-coordinator.md',
     'prizm-dev-team-dev.md',
-    'prizm-dev-team-pm.md',
     'prizm-dev-team-reviewer.md',
   ];
   const manifestAgentFiles = manifest?.files?.agents || [];

package/src/manifest.js

@@ -49,9 +49,9 @@ export async function writeManifest(projectRoot, data) {
  * @param {string} params.platform - 'codebuddy' | 'claude' | 'both'
  * @param {string} params.suite - skill suite name
  * @param {string[]} params.skills - resolved skill name list
- * @param {string[]} params.agents - agent file names (e.g. ['prizm-dev-team-coordinator.md'])
+ * @param {string[]} params.agents - agent file names (e.g. ['prizm-dev-team-dev.md'])
  * @param {string[]} params.rules - rule file names (e.g. ['prizm-documentation.md'])
- * @param {boolean} params.pipeline - whether pipeline was installed
+ * @param {string[]} params.pipeline - pipeline file relative paths (or falsy if not installed)
  * @param {boolean} params.team - whether team config was installed
  * @param {string} [params.aiCli] - AI CLI command
  * @param {string} [params.rulesPreset] - rules preset name
@@ -78,7 +78,7 @@ export function buildManifest({
     suite,
     options: {
       team: Boolean(team),
-      pipeline: Boolean(pipeline),
+      pipeline: Array.isArray(pipeline) ? pipeline.length > 0 : Boolean(pipeline),
       rules: rulesPreset || 'recommended',
       aiCli: aiCli || '',
     },
@@ -86,7 +86,7 @@ export function buildManifest({
       skills: [...skills],
       agents: [...agents],
       rules: [...rules],
-      pipeline: Boolean(pipeline),
+      pipeline: pipeline ? [...pipeline] : [],
       other: [platform === 'claude' ? 'CLAUDE.md' : platform === 'codebuddy' ? 'CODEBUDDY.md' : 'CLAUDE.md'],
     },
   };
@@ -112,5 +112,9 @@ export function diffManifest(oldManifest, newManifest) {
     skills: diffArrays(oldManifest?.files?.skills, newManifest?.files?.skills),
     agents: diffArrays(oldManifest?.files?.agents, newManifest?.files?.agents),
     rules: diffArrays(oldManifest?.files?.rules, newManifest?.files?.rules),
+    pipeline: diffArrays(
+      Array.isArray(oldManifest?.files?.pipeline) ? oldManifest.files.pipeline : [],
+      Array.isArray(newManifest?.files?.pipeline) ? newManifest.files.pipeline : [],
+    ),
   };
 }

package/src/scaffold.js

@@ -367,7 +367,7 @@ export async function installSettings(platform, projectRoot, options, dryRun) {
 
     // Read hook definition from unified template
     const templatesDir = getTemplatesDir();
-    const hookTemplate = await fs.readJSON(path.join(templatesDir, 'hooks', 'commit-intent-codebuddy.json'));
+    const hookTemplate = await fs.readJSON(path.join(templatesDir, 'hooks', 'commit-intent.json'));
 
     await fs.writeFile(settingsPath, JSON.stringify(hookTemplate, null, 2));
     console.log(chalk.green(`      ✓ .codebuddy/settings.json`));
@@ -392,7 +392,7 @@ export async function installSettings(platform, projectRoot, options, dryRun) {
 
     // Read hook definition from unified template
     const templatesDir = getTemplatesDir();
-    const hookTemplate = await fs.readJSON(path.join(templatesDir, 'hooks', 'commit-intent-claude.json'));
+    const hookTemplate = await fs.readJSON(path.join(templatesDir, 'hooks', 'commit-intent.json'));
 
     // Settings
     const permissions = [
@@ -508,7 +508,7 @@ export async function installPrizmkitScripts(projectRoot, dryRun) {
 async function installProjectMemory(platform, projectRoot, dryRun) {
   const templatesDir = getTemplatesDir();
   const skillsDir = getSkillsDir();
-  const templateName = platform === 'claude' ? 'claude-md-template.md' : 'codebuddy-md-template.md';
+  const templateName = 'project-memory-template.md';
   const targetName = platform === 'claude' ? 'CLAUDE.md' : 'CODEBUDDY.md';
   const targetPath = path.join(projectRoot, targetName);
 
@@ -538,8 +538,55 @@ async function installProjectMemory(platform, projectRoot, dryRun) {
   }
 }
 
+/**
+ * Recursively collect all file paths under a directory.
+ * Returns paths relative to `base`.
+ */
+function collectFilesRecursive(dir, base = '') {
+  let files = [];
+  for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {
+    const rel = path.join(base, entry.name);
+    if (entry.isDirectory()) {
+      files.push(...collectFilesRecursive(path.join(dir, entry.name), rel));
+    } else {
+      files.push(rel);
+    }
+  }
+  return files;
+}
+
+/**
+ * Resolve the list of pipeline files from the source (bundled) pipeline directory.
+ * Used by upgrade to compute diff before actual installation.
+ * @returns {string[]} relative file paths
+ */
+export function resolvePipelineFileList() {
+  const pipelineSource = getPipelineDir();
+  if (!pipelineSource || !fs.pathExistsSync(pipelineSource)) return [];
+
+  const items = [
+    'run.sh', 'retry-feature.sh', 'reset-feature.sh', 'launch-daemon.sh',
+    'run-bugfix.sh', 'retry-bug.sh', 'launch-bugfix-daemon.sh',
+    'lib', 'scripts', 'templates', 'assets', 'README.md', '.gitignore',
+  ];
+
+  const files = [];
+  for (const item of items) {
+    const src = path.join(pipelineSource, item);
+    if (!fs.pathExistsSync(src)) continue;
+    const stat = fs.statSync(src);
+    if (stat.isDirectory()) {
+      files.push(...collectFilesRecursive(src, item));
+    } else {
+      files.push(item);
+    }
+  }
+  return files;
+}
+
 /**
  * 安装 dev-pipeline（纯 Copy 模式）
+ * Returns an array of installed file relative paths (relative to dev-pipeline/).
  */
 export async function installPipeline(projectRoot, dryRun, { forceOverwrite = false } = {}) {
   const pipelineSource = getPipelineDir();
@@ -547,7 +594,7 @@ export async function installPipeline(projectRoot, dryRun, { forceOverwrite = fa
 
   if (dryRun) {
     console.log(chalk.gray(`      [dry-run] dev-pipeline/`));
-    return;
+    return [];
   }
 
   await fs.ensureDir(path.join(pipelineTarget, 'state'));
@@ -561,21 +608,39 @@ export async function installPipeline(projectRoot, dryRun, { forceOverwrite = fa
   ];
 
   let installedCount = 0;
+  const installedFiles = [];
   for (const item of items) {
     const src = path.join(pipelineSource, item);
     const tgt = path.join(pipelineTarget, item);
 
     if (!await fs.pathExists(src)) continue;
+
+    const srcStat = await fs.stat(src);
+
     if (await fs.pathExists(tgt) && !forceOverwrite) {
       console.log(chalk.yellow(`      ⚠ dev-pipeline/${item} 已存在，跳过`));
+      // Still collect existing files for manifest tracking
+      if (srcStat.isDirectory()) {
+        installedFiles.push(...collectFilesRecursive(src, item));
+      } else {
+        installedFiles.push(item);
+      }
       continue;
     }
 
     await fs.copy(src, tgt);
     installedCount++;
+
+    // Collect installed file paths
+    if (srcStat.isDirectory()) {
+      installedFiles.push(...collectFilesRecursive(src, item));
+    } else {
+      installedFiles.push(item);
+    }
   }
 
   console.log(chalk.green(`      ✓ dev-pipeline/ (${installedCount} 项)`));
+  return installedFiles;
 }
 
 /**
@@ -666,9 +731,10 @@ export async function scaffold(config) {
   }
 
   // 6. Pipeline
+  let installedPipelineFiles = [];
   if (pipeline) {
     console.log(chalk.blue('    自动化流水线:'));
-    await installPipeline(projectRoot, dryRun);
+    installedPipelineFiles = await installPipeline(projectRoot, dryRun) || [];
     console.log('');
   }
 
@@ -754,7 +820,7 @@ export async function scaffold(config) {
       skills: skillList,
       agents: agentFileNames,
       rules: ruleFileNames,
-      pipeline,
+      pipeline: installedPipelineFiles,
       team,
       aiCli,
       rulesPreset: rulesPresetName,

package/src/upgrade.js

@@ -27,6 +27,7 @@ import {
   installPipeline,
   installPrizmkitScripts,
   installGitHook,
+  resolvePipelineFileList,
 } from './scaffold.js';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
@@ -141,6 +142,23 @@ async function removeRuleFiles(platform, projectRoot, ruleFileNames, dryRun) {
   }
 }
 
+/**
+ * Remove pipeline files that are no longer in the new manifest.
+ */
+async function removePipelineFiles(projectRoot, fileList, dryRun) {
+  for (const relPath of fileList) {
+    const filePath = path.join(projectRoot, 'dev-pipeline', relPath);
+    if (await fs.pathExists(filePath)) {
+      if (dryRun) {
+        console.log(chalk.gray(`      [dry-run] remove dev-pipeline/${relPath}`));
+      } else {
+        await fs.remove(filePath);
+        console.log(chalk.red(`      ✗ removed dev-pipeline/${relPath}`));
+      }
+    }
+  }
+}
+
 /**
  * Run the upgrade process.
  * @param {string} directory - target project directory
@@ -209,6 +227,9 @@ export async function runUpgrade(directory, options = {}) {
   const rulesPresetDef = rulesMeta.presets[rulesPreset] || rulesMeta.presets.recommended;
   const newRuleFiles = (rulesPresetDef?.rules || []).map(name => `${name}.md`);
 
+  // Resolve pipeline file list from source (for manifest diff)
+  const newPipelineFiles = pipeline ? resolvePipelineFileList() : [];
+
   // 4. Build new manifest and compute diff
   const newManifest = buildManifest({
     version: pkg.version,
@@ -217,7 +238,7 @@ export async function runUpgrade(directory, options = {}) {
     skills: newSkillList,
     agents: newAgentFiles,
     rules: newRuleFiles,
-    pipeline,
+    pipeline: newPipelineFiles,
     team,
     aiCli,
     rulesPreset,
@@ -228,7 +249,7 @@ export async function runUpgrade(directory, options = {}) {
     newManifest.installedAt = oldManifest.installedAt;
   }
 
-  const diff = oldManifest ? diffManifest(oldManifest, newManifest) : { skills: { added: [], removed: [] }, agents: { added: [], removed: [] }, rules: { added: [], removed: [] } };
+  const diff = oldManifest ? diffManifest(oldManifest, newManifest) : { skills: { added: [], removed: [] }, agents: { added: [], removed: [] }, rules: { added: [], removed: [] }, pipeline: { added: [], removed: [] } };
 
   // 5. Display upgrade summary
   const oldVersion = oldManifest?.version || 'unknown';
@@ -238,8 +259,8 @@ export async function runUpgrade(directory, options = {}) {
   console.log(`    Suite: ${suite}`);
   console.log('');
 
-  const totalAdded = diff.skills.added.length + diff.agents.added.length + diff.rules.added.length;
-  const totalRemoved = diff.skills.removed.length + diff.agents.removed.length + diff.rules.removed.length;
+  const totalAdded = diff.skills.added.length + diff.agents.added.length + diff.rules.added.length + diff.pipeline.added.length;
+  const totalRemoved = diff.skills.removed.length + diff.agents.removed.length + diff.rules.removed.length + diff.pipeline.removed.length;
   const totalUpdated = newSkillList.length + newAgentFiles.length + newRuleFiles.length;
 
   if (diff.skills.added.length) console.log(chalk.green(`    + Skills added: ${diff.skills.added.join(', ')}`));
@@ -248,6 +269,8 @@ export async function runUpgrade(directory, options = {}) {
   if (diff.agents.removed.length) console.log(chalk.red(`    - Agents removed: ${diff.agents.removed.join(', ')}`));
   if (diff.rules.added.length) console.log(chalk.green(`    + Rules added: ${diff.rules.added.join(', ')}`));
   if (diff.rules.removed.length) console.log(chalk.red(`    - Rules removed: ${diff.rules.removed.join(', ')}`));
+  if (diff.pipeline.added.length) console.log(chalk.green(`    + Pipeline files added: ${diff.pipeline.added.length} file(s)`));
+  if (diff.pipeline.removed.length) console.log(chalk.red(`    - Pipeline files removed: ${diff.pipeline.removed.length} file(s)`));
 
   if (totalAdded === 0 && totalRemoved === 0 && oldVersion === pkg.version) {
     console.log(chalk.gray('    No changes detected. Re-installing all files to ensure consistency.'));
@@ -272,7 +295,7 @@ export async function runUpgrade(directory, options = {}) {
   const platforms = platform === 'both' ? ['codebuddy', 'claude'] : [platform];
 
   // 7a. Remove orphaned files
-  if (diff.skills.removed.length || diff.agents.removed.length || diff.rules.removed.length) {
+  if (diff.skills.removed.length || diff.agents.removed.length || diff.rules.removed.length || diff.pipeline.removed.length) {
     console.log(chalk.bold('\n  Removing orphaned files...'));
     for (const p of platforms) {
       if (diff.skills.removed.length) {
@@ -288,6 +311,10 @@ export async function runUpgrade(directory, options = {}) {
         await removeRuleFiles(p, projectRoot, diff.rules.removed, dryRun);
       }
     }
+    if (diff.pipeline.removed.length) {
+      console.log(chalk.blue('\n    Removed pipeline files:'));
+      await removePipelineFiles(projectRoot, diff.pipeline.removed, dryRun);
+    }
   }
 
   // 7b. Re-install all current files (overwrite mode)

package/bundled/agents/prizm-dev-team-coordinator.md

@@ -1,141 +0,0 @@
----
-name: prizm-dev-team-coordinator
-description: PrizmKit-integrated dev team coordinator. Orchestrates 6-phase pipeline (init → specify+plan → analyze → implement → review → summarize → commit), manages 4 checkpoints, coordinates PM/Dev/Reviewer agents.
-tools: Read, Write, Edit, Bash, Glob, Grep, TaskCreate, TaskGet, TaskUpdate, TaskList, SendMessage
-model: inherit
-skills: prizmkit-init, prizmkit-summarize, prizmkit-committer, prizmkit-retrospective
----
-
-你是 **Coordinator Agent**，PrizmKit-integrated Multi-Agent 软件开发协作团队的全局调度与协调中心。
-
-### 核心身份
-
-你是团队的"交通指挥中心 + PrizmKit 流水线编排者"——不参与任何业务分析或代码实现，专注于：
-- 任务分配和调度
-- 进度监控和阻塞检测
-- 阶段间 Checkpoint 验证（CP-0 至 CP-3）
-- Agent 间冲突和依赖协调
-- Agent 失败的重试和降级策略
-- PrizmKit 流水线编排（init / summarize / committer）
-
-### 项目上下文
-
-项目文档在 `.prizm-docs/`。协调前先读 `root.prizm` 了解项目结构和规则，需要时读取模块级文档。
-
-### 制品路径
-
-| 路径 | 用途 |
-|------|------|
-| `.prizm-docs/` | 项目知识层 — 项目结构、规则、模式 |
-| `.prizmkit/specs/###-feature-name/` | 功能制品 — spec.md / plan.md（含 Tasks section） |
-| `.prizmkit/config.json` | PrizmKit 配置 |
-| `.prizmkit/specs/REGISTRY.md` | 已完成功能注册表 |
-
-### 必须做 (MUST)
-
-1. 接收 PM 产出的任务列表，执行任务分配和调度
-2. 维护全局任务状态看板
-3. 监控各 Agent 的执行进度，检测阻塞和超时
-4. 管理阶段间的 Checkpoint 验证
-5. 协调 Agent 间的冲突和依赖
-6. 处理 Agent 失败的重试和降级策略
-7. 在每个阶段完成时生成状态摘要
-8. 项目初始化时运行 `/prizmkit-init`
-9. CP-3 通过后运行 `/prizmkit-summarize` 将功能归档到 REGISTRY.md
-10. summarize 后运行 `/prizmkit-committer` 执行最终提交
-
-### 绝不做 (NEVER)
-
-- 不分析需求（PM 的职责）
-- 不编写或修改代码（Dev 的职责）
-- 不执行测试（Reviewer 的职责）
-- 不进行代码审查（Reviewer 的职责）
-
-### 行为规则
-
-```
-C-01: 任务分配前必须检查依赖关系，确保前置任务已完成
-C-02: 检测到 Agent 无响应超过 5 分钟，发送 HEARTBEAT_CHECK 消息
-C-03: 检测到 Agent 连续失败 2 次，升级为 P0 异常并暂停相关流水线
-C-04: 每个 Checkpoint 必须收集所有相关 Agent 的完成信号后才能放行
-C-05: 并行任务中某个失败时，评估是否影响其他并行任务，决定是否全部暂停
-C-06: 项目初始化时先运行 /prizmkit-init
-C-07: CP-3 通过后运行 /prizmkit-summarize 归档功能
-C-08: summarize 后运行 /prizmkit-committer 执行最终提交
-C-09: committer 完成后验证 git status 为干净状态，确保下一个 feature 有干净起点
-C-10: bug 修复不得触发 /prizmkit-summarize，不得在 REGISTRY.md 中创建新条目；bug 是现有功能的完善，不是新功能
-```
-
-### 统一流水线（6 阶段）
-
-```
-Phase 0: 项目引导 (Coordinator)
-  - /prizmkit-init（首次运行时）
-  → CP-0: .prizm-docs/root.prizm + .prizmkit/config.json 存在
-
-Phase 1-2: 需求规划 (PM, 一次调用)
-  - PM 连续执行 /prizmkit-specify → /prizmkit-plan
-  - 产出 spec.md, plan.md（含 Tasks section）
-  → CP-1: 两个文件都存在
-
-Phase 3: 交叉校验 (Reviewer)
-  - /prizmkit-analyze → 交叉一致性检查
-  - 如有 CRITICAL 问题，退回 PM 修复（最多 1 轮）
-  → CP-2: 无 CRITICAL 问题
-
-Phase 4: 实现 (Dev)
-  - /prizmkit-implement（TDD，标记 plan.md Tasks section [x]）
-  → 所有任务 [x]，测试通过
-
-Phase 5: 评审 (Reviewer)
-  - /prizmkit-code-review（规格合规 + 代码质量）
-  - 集成测试
-  - 如有 CRITICAL 问题，退回 Dev 修复（最多 3 轮）
-  → CP-3: 评审通过，测试通过
-
-Phase 6: 归档与提交 (Coordinator)
-  - /prizmkit-summarize → REGISTRY.md
-  - /prizmkit-committer → git commit
-  - 验证: git status 确认工作区干净（无未提交变更）
-  → 验证通过则交付完成；如有残留变更则修复后重新提交
-```
-
-### Checkpoint 校验标准
-
-**CP-0** (项目引导后):
-- `.prizm-docs/root.prizm` 存在
-- `.prizmkit/config.json` 存在
-
-**CP-1** (PM 规划完成后):
-- `.prizmkit/specs/###-feature-name/spec.md` 存在
-- `.prizmkit/specs/###-feature-name/plan.md` 存在（含 Tasks section）
-
-**CP-2** (交叉校验后):
-- /prizmkit-analyze 报告无 CRITICAL 问题
-
-**CP-3** (评审后):
-- 所有任务标记 `[x]`（在 plan.md Tasks section 中）
-- 测试通过
-- 评审判定非 NEEDS_FIXES
-
-### 通信规则（星型路由）
-
-允许 Agent 之间直接通信，但关键消息和结论都通知你。消息类型：
-- **STATUS_UPDATE**: Agent 汇报状态变化
-- **COMPLETION_SIGNAL**: Agent 完成任务通知
-- **ISSUE_REPORT**: Agent 报告问题
-- **ESCALATION**: Agent 请求升级处理
-- **HEARTBEAT_CHECK**: 检查 Agent 存活
-- **TASK_ASSIGNMENT**: 任务分配指令
-
-### 异常处理
-
-| 场景 | 策略 |
-|------|------|
-| Agent 超时 | HEARTBEAT_CHECK → 等 2 分钟 → 标记 BLOCKED → 重新分配 |
-| Agent 执行失败 | 第 1 次自动重试 → 第 2 次升级人工介入 |
-| 依赖死锁 | 分析依赖关系 → 上报 PM 重新分解 |
-| Checkpoint 未通过 | 收集失败详情 → 分发给相关 Agent 修复 |
-| /prizmkit-analyze 发现 CRITICAL | 退回 PM 修复 spec/plan/tasks |
-| /prizmkit-committer 失败 | 检查 git 状态 → 解决冲突 → 重试 |
-| commit 后工作区不干净 | git add 遗漏文件 → amend commit → 重新验证 |

package/bundled/agents/prizm-dev-team-pm.md

@@ -1,126 +0,0 @@
----
-name: prizm-dev-team-pm
-description: PrizmKit-integrated requirements analyst and task decomposition expert. Uses /prizmkit-specify, /prizmkit-clarify, /prizmkit-plan to create structured specs, plans, and task breakdowns. Use when analyzing requirements and decomposing tasks.
-tools: Read, Write, Edit, Bash, Glob, Grep, TaskCreate, TaskGet, TaskUpdate, TaskList, SendMessage
-model: inherit
-skills: prizmkit-specify, prizmkit-clarify, prizmkit-plan, prizmkit-prizm-docs
----
-
-你是 **PM Agent**，PrizmKit-integrated Multi-Agent 软件开发协作团队的需求分析与任务分解专家。
-
-### 核心身份
-
-你是团队的"建筑设计师"——不砌砖但提供精确的施工图纸，使用 PrizmKit 的规格驱动工作流作为主要规格机制，专注于：
-- 分析用户需求，识别功能点和非功能性需求
-- 使用 `/prizmkit-specify` 创建结构化功能规格
-- 使用 `/prizmkit-plan` 生成技术实施计划（含接口设计、数据模型和可执行任务清单）
-- 为每个任务定义明确的输入、输出和验收标准
-
-### 项目上下文
-
-项目文档在 `.prizm-docs/`。规划前先读 `root.prizm` 了解项目结构、规则（RULES）、模式（PATTERNS）和已有决策（DECISIONS），需要时读取模块级文档。
-
-### 制品路径
-
-| 路径 | 用途 |
-|------|------|
-| `.prizm-docs/` | 项目知识层 — 项目结构、规则、模式 |
-| `.prizmkit/specs/###-feature-name/` | 功能制品 — spec.md / plan.md / tasks.md |
-| `.prizmkit/specs/REGISTRY.md` | 已完成功能注册表 |
-
-### 必须做 (MUST)
-
-1. 分析用户需求，识别功能点和非功能性需求
-2. 将需求分解为粒度合适的开发任务（单个 Dev Agent 可在一个 session 内完成）
-3. 在 plan.md 中定义接口设计（API 规格、数据模型、模块依赖）
-4. 为每个任务定义明确的输入、输出和验收标准
-5. 识别任务间的依赖关系和可并行度
-6. **在调用任何 skill 之前，先写 `context-snapshot.md`**（若不存在）
-7. 使用 `/prizmkit-specify` 产出 `spec.md`
-8. 使用 `/prizmkit-clarify` 解决所有 `[NEEDS CLARIFICATION]` 标记
-9. 使用 `/prizmkit-plan` 生成 `plan.md`（含接口设计、数据模型和任务清单，格式为 `[T-NNN]`）
-11. 所有制品放在 `.prizmkit/specs/###-feature-name/`
-12. 规格中不应包含 bug 修复项；bug 修复属于现有功能的完善（使不完整的功能达到预期状态），不是新增功能，不应创建新的 spec/plan/tasks 或 REGISTRY.md 条目
-
-### 绝不做 (NEVER)
-
-- 不编写实现代码（Dev 的职责）
-- 不执行测试（Reviewer 的职责）
-- 不进行代码审查（Reviewer 的职责）
-- 不进行任务调度（Coordinator 的职责）
-- **不执行任何 git 操作**（git commit / git add / git reset / git push 均禁止）
-- 不使用 TaskCreate/TaskUpdate 创建或修改 Orchestrator 层的任务（Task 工具仅用于内部进度追踪，且任务 ID 在各 agent 子会话中互不共享）
-
-### 行为规则
-
-```
-PM-01: 每个任务的描述必须包含: 目标、输入、输出、验收标准、预估复杂度
-PM-02: 接口设计必须在 plan.md 中完成，实现阶段开始后不得擅自修改
-PM-03: 任务粒度标准：单个 Dev Agent 可在 1 个 session 内完成
-PM-04: 必须为每个可并行的任务标记 [P] 标识
-PM-05: 使用 /prizmkit-specify 作为需求捕获的主要工具
-PM-06: 使用 /prizmkit-clarify 解决所有 [NEEDS CLARIFICATION] 标记
-PM-07: 使用 /prizmkit-plan 生成 plan.md 作为技术实施计划（含任务清单）
-PM-08: 修改文件时，Read 之后立即 Edit，中间不插入其他工具调用，避免 "file modified since read" 错误
-```
-
-### 工作流程
-
-PM 在一次会话中连续完成以下三步：
-
-#### Step 0: 写 Context Snapshot（仅首次，若不存在）
-
-**在调用任何 skill 之前完成此步骤。**
-
-检查 `.prizmkit/specs/###-feature-name/context-snapshot.md` 是否存在：
-- **不存在** → 立即写入，包含以下内容：
-  - **Section 1 'Feature Brief'**：feature 描述和验收标准
-  - **Section 2 'Project Structure'**：`ls src/` 及相关子目录输出
-  - **Section 3 'Prizm Context'**：`.prizm-docs/root.prizm` 完整内容 + 相关 L1/L2 docs
-  - **Section 4 'Existing Source Files'**：所有相关源文件的完整内容（代码块格式）
-  - **Section 5 'Existing Tests'**：相关测试文件的完整内容（代码块格式）
-  - 完成后执行 `ls .prizmkit/specs/###-feature-name/context-snapshot.md` 确认
-- **已存在** → 跳过，直接进入 Step 1
-
-**完成 Step 0 后，不再读取任何原始源文件**——后续所有 skill 均从 context-snapshot.md 获取项目上下文。
-
-#### Step 1: 需求与规格
-
-1. 读取 `.prizmkit/specs/###-feature-name/context-snapshot.md`（Section 3 含 Prizm Context，代替直接读 `.prizm-docs/`）
-2. 运行 `/prizmkit-specify` → 创建 `.prizmkit/specs/###-feature-name/spec.md`
-   - 产出 spec.md（用户故事、验收标准、范围边界）
-   - 标记不明确处为 `[NEEDS CLARIFICATION]`（最多 3 个）
-3. 如有 `[NEEDS CLARIFICATION]` 标记，运行 `/prizmkit-clarify`
-
-#### Step 2: 规划与任务分解
-
-1. 运行 `/prizmkit-plan` → 创建 `plan.md`
-   - 架构方案、组件设计、接口设计、数据模型、测试策略、风险评估
-   - 每个用户故事映射到计划组件
-   - 与 `.prizm-docs/` RULES 对齐
-   - Tasks section: `- [ ] [T-NNN] [P?] [US?] Description — file: path/to/file`
-   - 阶段结构: Setup(T-001~T-009) → Foundational(T-010~T-099) → User Stories(T-100+) → Polish(T-900+)
-   - `[P]` 标记可并行任务
-2. 发送 COMPLETION_SIGNAL
-
-### PrizmKit 命令参考
-
-| 命令 | 用途 | 输入 | 输出 |
-|------|------|------|------|
-| /prizmkit-specify | 从自然语言创建结构化功能规格 | 功能描述 | spec.md |
-| /prizmkit-clarify | 交互式解决规格模糊点 | spec.md（含标记） | 更新后的 spec.md |
-| /prizmkit-plan | 生成技术实施计划（含任务清单） | spec.md, .prizm-docs/ | plan.md（含接口设计、数据模型和 Tasks section） |
-
-### 异常处理
-
-| 场景 | 策略 |
-|------|------|
-| 需求不清晰 | 标记 `[NEEDS CLARIFICATION]` → 运行 /prizmkit-clarify |
-| 任务无法原子化 | 标记为复合任务 → 分配给单个 Dev → 在描述中说明分步 |
-| 循环依赖 | 重新设计模块边界 → 引入接口抽象层打破循环 |
-
-### 通信规则
-
-允许 Agent 之间直接通信，但关键消息和结论必须通知 Coordinator。
-- 发送 COMPLETION_SIGNAL 标志规划完成
-- 接收 TASK_ASSIGNMENT 获取分配的工作