flow-comet 1.6.1 → 1.6.3
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/.flow-comet/skills/flow-comet/INSTALLED_VERSION +1 -1
- package/.flow-comet/skills/flow-comet/SKILL.md +94 -46
- package/.flow-comet/skills/flow-comet/reference/KNOWN-ISSUES-template.md +1 -1
- package/.flow-comet/skills/flow-comet/reference/commit-discipline.md +32 -0
- package/.flow-comet/skills/flow-comet/reference/dirty-worktree.md +1 -1
- package/.flow-comet/skills/flow-comet/{GUIDANCE.md → reference/entry-detail.md} +22 -30
- package/.flow-comet/skills/flow-comet/reference/fix-loop.md +57 -0
- package/.flow-comet/skills/flow-comet/reference/platform-facts.md +58 -0
- package/.flow-comet/skills/flow-comet/reference/replan.md +23 -0
- package/.flow-comet/skills/flow-comet/reference/workflow-protocol.json +1 -1
- package/.flow-comet/skills/flow-comet/scripts/comet-check.mjs +5 -4
- package/.flow-comet/skills/flow-comet/scripts/comet-hook-guard.mjs +260 -17
- package/.flow-comet/skills/flow-comet/scripts/context-init.mjs +129 -3
- package/.flow-comet/skills/flow-comet/scripts/context-scan.mjs +396 -0
- package/.flow-comet/skills/flow-comet/scripts/evolve.mjs +778 -0
- package/.flow-comet/skills/flow-comet/scripts/guard-self-test.mjs +5432 -194
- package/.flow-comet/skills/flow-comet/scripts/health.mjs +664 -0
- package/.flow-comet/skills/flow-comet/scripts/route-node.mjs +51 -4
- package/.flow-comet/skills/flow-comet/scripts/state-schema.mjs +68 -0
- package/.flow-comet/skills/flow-comet/scripts/system-test.mjs +1479 -11
- package/.flow-comet/skills/flow-comet/scripts/time-utils.mjs +133 -0
- package/.flow-comet/skills/flow-comet/scripts/workflow-guard.mjs +197 -5
- package/.flow-comet/skills/flow-comet/scripts/workflow-handoff.mjs +115 -6
- package/.flow-comet/skills/flow-comet/scripts/workflow-state.mjs +261 -29
- package/.flow-comet/skills/flow-comet-archive/SKILL.md +10 -19
- package/.flow-comet/skills/flow-comet-change/SKILL.md +10 -1
- package/.flow-comet/skills/flow-comet-compose/SKILL.md +1 -1
- package/.flow-comet/skills/flow-comet-design/SKILL.md +8 -6
- package/.flow-comet/skills/flow-comet-evolve/SKILL.md +46 -11
- package/.flow-comet/skills/flow-comet-execute/SKILL.md +58 -16
- package/.flow-comet/skills/flow-comet-health/SKILL.md +57 -16
- package/.flow-comet/skills/flow-comet-integration/SKILL.md +8 -5
- package/.flow-comet/skills/flow-comet-open/SKILL.md +5 -1
- package/.flow-comet/skills/flow-comet-plan/GUIDANCE.md +1 -1
- package/.flow-comet/skills/flow-comet-plan/SKILL.md +8 -8
- package/.flow-comet/skills/flow-comet-review/SKILL.md +9 -12
- package/.flow-comet/skills/flow-comet-subagent-execute/SKILL.md +59 -16
- package/.flow-comet/skills/flow-comet-task/SKILL.md +3 -2
- package/.flow-comet/skills/flow-comet-ui-design/SKILL.md +29 -4
- package/.flow-comet/skills/flow-comet-verify/SKILL.md +8 -17
- package/README.md +5 -5
- package/package.json +1 -1
- package/scripts/dsh-bridge.mjs +59 -26
- package/scripts/prepare-env.mjs +165 -1
- package/.flow-comet/skills/flow-comet/reference/TEST-MATRIX.md +0 -116
- package/.flow-comet/skills/flow-comet/reference/composition-report.md +0 -65
- package/.flow-comet/skills/flow-comet/reference/dsh-platform.md +0 -184
- package/.flow-comet/skills/flow-comet/reference/resolved-skills.json +0 -661
- package/.flow-comet/skills/flow-comet/reference/skill-review.md +0 -13
- package/.flow-comet/skills/flow-comet/reference/subagents/script-author.md +0 -7
- package/.flow-comet/skills/flow-comet/reference/worktree-notes.md +0 -70
|
@@ -1,661 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": 1,
|
|
3
|
-
"resolvedSkills": [
|
|
4
|
-
{
|
|
5
|
-
"query": "flow-comet-open",
|
|
6
|
-
"preferenceIndex": 0,
|
|
7
|
-
"status": "available",
|
|
8
|
-
"sources": [
|
|
9
|
-
{
|
|
10
|
-
"name": "flow-comet-open",
|
|
11
|
-
"preferenceIndex": 0,
|
|
12
|
-
"platform": "claude-code",
|
|
13
|
-
"scope": "project",
|
|
14
|
-
"origin": "project",
|
|
15
|
-
"factory": {
|
|
16
|
-
"query": "flow-comet-open"
|
|
17
|
-
},
|
|
18
|
-
"root": ".flow-comet/skills/flow-comet-open",
|
|
19
|
-
"description": "Open node for flow-comet: produces CHANGE.md + REQUIREMENT.md via structured questioning and AC derivation. First node in the flow — no upstream artifacts needed. Do not use for ordinary standalone tasks.",
|
|
20
|
-
"skillMd": "---\nname: flow-comet-open\ndescription: \"Open node for flow-comet: produces CHANGE.md + REQUIREMENT.md via structured questioning and AC derivation. First node in the flow — no upstream artifacts needed. Do not use for ordinary standalone tasks.\"\n---\n\n# Open\n\n## Node Goal\n\nThis node transforms a vague user intent into a concrete change proposal (CHANGE.md) and verifiable requirements (REQUIREMENT.md). It is the entry point of the flow-comet workflow, combining the CHANGE and REQUIREMENT phases into a single node. The output artifacts serve as the foundation for all downstream design, planning, and implementation work.\n\n## Guidance\n\n### Prerequisites\n\n- No upstream artifacts required — this is the first node in the flow.\n- If `.specs/<change-id>/` already exists for the proposed id, the agent must auto-increment (`<id>-2`, `<id>-3`) to avoid collision.\n- If `.specs/ARCHITECTURE.md` exists, it should be read for context but is not a blocking prerequisite.\n\n### Steps\n\n1. **Auto-generate change-id**: Extract 2-4 kebab-case keywords from user description. Check `.specs/<id>/` does not exist. Declare the id to the user in the first message. User does not need to confirm unless they want to change it.\n\n2. **Architecture change detection (0.4)**: Evaluate against 5 criteria (module structure impact, ADR conflict, public contract change, capacity boundary, cross-service orchestration). If hit: present 3 options (run A-architect first / continue with architecture impact statement / re-classify). If ARCHITECTURE.md missing + hit: warn user. If not hit (90% of cases): skip silently.\n\n3. **Frontend project identification (0.5)**: Check if description contains frontend keywords (website/web/page/UI/app/dashboard etc.). If yes: mark as frontend project and proceed to 0.6. If not: skip to step 4.\n\n4. **Visual tone preselection (0.6, frontend only)**: Present 9 style cards (from ui-ux-pro-max if installed, else from `flow-kit/reference/ui-aesthetics.md`). Give 1 preferred + 1 backup recommendation. Exclude 1-3 unsuitable styles with reasons. Wait for user selection before proceeding.\n\n5. **Structured questioning (step 1)**: Ask \"why / who / what problem / when is done\" in max 3 questions per round. Never skip this — do not assume requirements. Do not mix with tone cards in the same message.\n\n6. **Impact assessment (step 2)**: Determine if new/modified REQUIREMENT.md needed, if architecture touched, if existing ACs affected.\n\n7. **Scope exclusion (step 3)**: Explicitly write what this change will NOT do. At least 1 item required.\n\n8. **Generate CHANGE.md (step 4)**: Use `flow-kit/templates/CHANGE.md` template. Save to `.specs/<change-id>/CHANGE.md`. Must contain: Why / What / Impact / Scope exclusion / Acceptance line. No implementation details allowed.\n\n9. **Path recommendation (step 5)**: Based on impact, recommend full / medium / shortest path with reasoning.\n\n10. **REQUIREMENT phase**: After user confirms CHANGE.md:\n - Write ACs in Given/When/Then format — each must be verifiable by one command or one manual operation.\n - Scope split: v1 (must do) / v2 (next time) / out (never). At least 1 item in v2 and 1 in out.\n - Extract terminology to `.specs/CONTEXT.md` (glossary + locked decisions + defaults).\n - List non-functional requirements explicitly (write \"none\" if none).\n - Stop and ask if any AC cannot be verified in one sentence.\n\n11. **LESSONS scan**: Grep `.specs/LESSONS.md` for keywords related to this change. If active lessons hit, declare \"difference is X\" or \"still applies, will not retry\".\n\nThe full questioning protocol, anti-patterns, and templates are in:\n- `flow-kit/prompts/0-change.md` (CHANGE phase)\n- `flow-kit/prompts/1-requirement.md` (REQUIREMENT phase)\n\n### Completion reasoning\n\nThis node is truly done when:\n- `.specs/<change-id>/CHANGE.md` exists and user has confirmed it.\n- `.specs/<change-id>/REQUIREMENT.md` exists with all ACs in Given/When/Then format.\n- `.specs/CONTEXT.md` has been updated with at least 1 new term or decision.\n- v1/v2/out scope split is populated in REQUIREMENT.md.\n- At least 1 \"out of scope\" item exists in CHANGE.md.\n- User has confirmed both artifacts.\n\n### Red flags\n\n- **Agent thought**: \"User said enough, I can infer the rest.\" **Actual risk**: Skipping structured questioning leads to wrong requirements. Always ask, never assume.\n- **Agent thought**: \"CHANGE.md should describe how to implement.\" **Actual risk**: CHANGE.md is a proposal, not a design doc. Implementation details belong in DESIGN.md. Violates R3 role boundary.\n- **Agent thought**: \"No need for out-of-scope items, the scope is obvious.\" **Actual risk**: Without explicit scope exclusion, downstream phases will expand scope unchecked. At least 1 \"out of scope\" item is mandatory.\n- **Agent thought**: \"Architecture change detection is optional.\" **Actual risk**: Skipping 0.4 means a service-split or DB-migration-level change enters the flow without ADR alignment, causing DESIGN.md section 0.5 to be self-contradictory.\n- **Agent thought**: \"AC '界面要好看' is good enough.\" **Actual risk**: Non-verifiable ACs cannot be tested. Must stop and ask for measurable criteria.\n\n## Entry Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs entry open\n```\n\n## Skill Implementation\n\nThe open node loads `flow-comet-change` for the CHANGE phase (structured questioning, change-id generation, architecture detection, visual tone preselection) and `flow-comet-requirement` for the REQUIREMENT phase (AC derivation, scope split, terminology extraction). It produces two artifacts in `.specs/<change-id>/` and updates the project-level `.specs/CONTEXT.md`.\n\n## Required Skill Calls\n\n| Skill | Enforcement | Reason |\n|-------|-------------|--------|\n| `flow-comet-change` | Required before CHANGE.md generation | Provides structured questioning protocol, architecture detection, and tone preselection |\n| `flow-comet-requirement` | Required before REQUIREMENT.md generation | Provides AC format (Given/When/Then), scope split, and terminology extraction rules |\n\n## Output Schemas\n\nSchema: `flowkit.intake.v1`\n\n| Schema ID | Artifact Kind | Required | Path |\n|-----------|--------------|----------|------|\n| `change-doc` | file | yes | `.specs/<change-id>/CHANGE.md` |\n| `requirement-doc` | file | yes | `.specs/<change-id>/REQUIREMENT.md` |\n| `context-update` | file | yes | `.specs/CONTEXT.md` (append/update) |\n\nEvidence: `intake-summary` (required)\n\n## Evidence Record\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-state.mjs record open '{\"summary\":\"CHANGE.md + REQUIREMENT.md generated, user confirmed\"}'\n```\n\n## Guardrails\n\n| Guardrail ID | Label | Validation Type |\n|--------------|-------|-----------------|\n| `intake-artifacts` | CHANGE.md + REQUIREMENT.md exist | artifact-exists |\n| `context-updated` | CONTEXT.md has new terms/decisions | artifact-exists |\n| `scope-exclusion` | At least 1 out-of-scope item in CHANGE.md | content-check |\n\n## Exit Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs exit open --apply\n```\n\nIf the script prints `SKILL: flow-comet-design`, load that Skill next.\n\n## Recovery\n\n1. Re-run entry check to confirm workflow state.\n2. Read `.specs/<change-id>/CHANGE.md` — if exists and confirmed, skip CHANGE phase.\n3. Read `.specs/<change-id>/REQUIREMENT.md` — if exists and confirmed, skip REQUIREMENT phase.\n4. Resume from the first incomplete artifact. Do not repeat confirmed phases.\n5. If CHANGE.md exists but REQUIREMENT.md does not, continue from REQUIREMENT phase only.\n",
|
|
21
|
-
"references": [],
|
|
22
|
-
"scripts": [],
|
|
23
|
-
"hash": "08e035fbfc8ad5f27894d6e8618d8bc00cc799517a74334b4a9207f5c3f57c20"
|
|
24
|
-
}
|
|
25
|
-
]
|
|
26
|
-
},
|
|
27
|
-
{
|
|
28
|
-
"query": "flow-comet-change",
|
|
29
|
-
"preferenceIndex": 1,
|
|
30
|
-
"status": "available",
|
|
31
|
-
"sources": [
|
|
32
|
-
{
|
|
33
|
-
"name": "flow-comet-change",
|
|
34
|
-
"preferenceIndex": 1,
|
|
35
|
-
"platform": "claude-code",
|
|
36
|
-
"scope": "project",
|
|
37
|
-
"origin": "project",
|
|
38
|
-
"factory": {
|
|
39
|
-
"query": "flow-comet-change"
|
|
40
|
-
},
|
|
41
|
-
"root": ".flow-comet/skills/flow-comet-change",
|
|
42
|
-
"description": "flow-kit CHANGE 阶段协议:反问澄清、change-id 自动生成、架构级变更检测、视觉调性预选。Comet open 阶段的 flow-kit 增强。",
|
|
43
|
-
"skillMd": "---\nname: flow-comet-change\ndescription: \"flow-kit CHANGE 阶段协议:反问澄清、change-id 自动生成、架构级变更检测、视觉调性预选。Comet open 阶段的 flow-kit 增强。\"\n---\n\n# flow-kit CHANGE Protocol\n\n本 Skill 为 Comet open 阶段提供 flow-kit 的 CHANGE 反问协议。\n\n## 加载\n\n读取 `flow-kit/prompts/0-change.md` 并按其执行。关键步骤:\n\n1. **自动生成 change-id**(kebab-case,2~4 词,检查 `.specs/<id>/` 不冲突)\n2. **架构级变更检测**(步骤 0.4):命中 5 类信号时暂停,引导先跑 A-architect\n3. **前端项目识别**(步骤 0.5):关键词判定是否为前端项目\n4. **视觉调性预选**(步骤 0.6,仅前端):9 张调性卡片 + 推荐\n5. **结构化反问**(步骤 1):每轮最多 3 个问题\n6. **影响面判定 + 范围排除**\n7. **生成 CHANGE.md**(使用 `flow-kit/templates/CHANGE.md`)\n8. **路径建议**:完整/中等/最短\n\n## 产物\n\n- `.specs/<change-id>/CHANGE.md`\n\n## Comet 集成\n\nCHANGE.md 生成后,由 Comet open 阶段接管状态推进。不需要手动维护 STATE.md。\n",
|
|
44
|
-
"references": [],
|
|
45
|
-
"scripts": [],
|
|
46
|
-
"hash": "362596a7105f9d1a181cbdbe30c4627611918be194c00038fc3cc2af392ebb49"
|
|
47
|
-
}
|
|
48
|
-
]
|
|
49
|
-
},
|
|
50
|
-
{
|
|
51
|
-
"query": "flow-comet-requirement",
|
|
52
|
-
"preferenceIndex": 2,
|
|
53
|
-
"status": "available",
|
|
54
|
-
"sources": [
|
|
55
|
-
{
|
|
56
|
-
"name": "flow-comet-requirement",
|
|
57
|
-
"preferenceIndex": 2,
|
|
58
|
-
"platform": "claude-code",
|
|
59
|
-
"scope": "project",
|
|
60
|
-
"origin": "project",
|
|
61
|
-
"factory": {
|
|
62
|
-
"query": "flow-comet-requirement"
|
|
63
|
-
},
|
|
64
|
-
"root": ".flow-comet/skills/flow-comet-requirement",
|
|
65
|
-
"description": "flow-kit REQUIREMENT 阶段协议:AC(Given/When/Then)+ v1·v2·out 范围切分 + 术语提取。Comet open 阶段的 flow-kit 增强。",
|
|
66
|
-
"skillMd": "---\nname: flow-comet-requirement\ndescription: \"flow-kit REQUIREMENT 阶段协议:AC(Given/When/Then)+ v1·v2·out 范围切分 + 术语提取。Comet open 阶段的 flow-kit 增强。\"\n---\n\n# flow-kit REQUIREMENT Protocol\n\n本 Skill 为 Comet open 阶段提供 flow-kit 的 REQUIREMENT 需求分析。\n\n## 加载\n\n读取 `flow-kit/prompts/1-requirement.md` 并按其执行。关键步骤:\n\n1. **AC 编写**:每条 AC 使用 Given/When/Then 格式\n2. **v1·v2·out 切分**:v1 本次必做 / v2 可推迟 / out 明确不做\n3. **术语提取**:域语言表,写入 `.specs/CONTEXT.md`\n4. **非功能性需求**:性能/安全/兼容性预算\n5. **生成 REQUIREMENT.md**(使用 `flow-kit/templates/REQUIREMENT.md`)\n\n## 产物\n\n- `.specs/<change-id>/REQUIREMENT.md`\n- `.specs/CONTEXT.md`(首次或需更新时)\n\n## Comet 集成\n\nREQUIREMENT.md 是 Comet design 阶段的前置依赖。由 Comet guard 检查产物完整性。\n",
|
|
67
|
-
"references": [],
|
|
68
|
-
"scripts": [],
|
|
69
|
-
"hash": "dcee43d192744c4b8f1be0dfe0ac42efe844fdbf364ba40b3242595b2998e472"
|
|
70
|
-
}
|
|
71
|
-
]
|
|
72
|
-
},
|
|
73
|
-
{
|
|
74
|
-
"query": "flow-comet-design",
|
|
75
|
-
"preferenceIndex": 3,
|
|
76
|
-
"status": "available",
|
|
77
|
-
"sources": [
|
|
78
|
-
{
|
|
79
|
-
"name": "flow-comet-design",
|
|
80
|
-
"preferenceIndex": 3,
|
|
81
|
-
"platform": "claude-code",
|
|
82
|
-
"scope": "project",
|
|
83
|
-
"origin": "project",
|
|
84
|
-
"factory": {
|
|
85
|
-
"query": "flow-comet-design"
|
|
86
|
-
},
|
|
87
|
-
"root": ".flow-comet/skills/flow-comet-design",
|
|
88
|
-
"description": "Design node for flow-comet: produces DESIGN.md (and UI-DESIGN.md for frontend) via tech stack selection, ADR, and architecture alignment. Do not use for ordinary standalone tasks.",
|
|
89
|
-
"skillMd": "---\nname: flow-comet-design\ndescription: \"Design node for flow-comet: produces DESIGN.md (and UI-DESIGN.md for frontend) via tech stack selection, ADR, and architecture alignment. Do not use for ordinary standalone tasks.\"\n---\n\n# Design\n\n## Node Goal\n\nThis node transforms requirements into an actionable technical design. It produces DESIGN.md with tech stack decisions, architecture alignment with existing modules, ADRs for reversible decisions, data flow diagrams, and risk assessment. For frontend projects, it additionally produces UI-DESIGN.md with design tokens and visual specifications. The output artifacts serve as the blueprint for task decomposition and implementation.\n\n## Guidance\n\n### Prerequisites\n\n- `.specs/<change-id>/CHANGE.md` must exist (produced by open node).\n- `.specs/<change-id>/REQUIREMENT.md` must exist (produced by open node).\n- If `.specs/ARCHITECTURE.md` exists, it should be read (sections 2, 3, 4) for module boundaries, ADR conflicts, and cross-module contracts.\n- `flow-kit/reference/tech-stacks.md` must be accessible for tech stack card selection.\n\n### Steps\n\n1. **Architecture change pre-check (0-)**: If CHANGE.md already has \"Architecture Impact Statement\" or \"Post A-architect\" marker, skip. Otherwise re-evaluate against the 5 criteria from `0-change.md` step 0.4.1. If hit + ARCHITECTURE.md exists: check ADR conflict. If hit + no ARCHITECTURE.md: present 3 options to user. If not hit: proceed.\n\n2. **Tech stack preselection (section 0)**: Load `flow-kit/reference/tech-stacks.md`. Filter to 5-6 cards matching project type. Present with 1 preferred + 1 backup (reasoning from REQUIREMENT ACs + non-functional requirements). Exclude 1-2 with reasons. Wait for user selection. Exception: if CONTEXT.md has locked tech decisions, use those directly.\n\n3. **Existing architecture alignment (section 0.5, brownfield only)**: This is the most critical step for existing projects:\n - **0.5.1 Touched modules**: Grep (not guess) actual modules that will be touched. List: existing modules to modify, existing modules to reuse, new modules to create, forbidden modules (DO NOT TOUCH).\n - **0.5.2 Align existing abstractions**: For each capability needed, check if existing code already provides it. Table format: \"Need X | Existing Y exists | Decision: reuse\" or \"Need X | None exists | Decision: create (reason: first time)\".\n - **0.5.3 Reuse vs new patterns**: For each key decision, declare \"reuse\" (with reference) or \"introduce new\" (with justification). New patterns require explicit reason.\n - **0.5.4 Write to DESIGN.md section 0.5**: All of the above goes into DESIGN.md.\n\n4. **Technical decisions (section 1)**: Each decision must have: decision + alternatives + selection reason + trade-off cost. \"Use best practice\" is forbidden — must be specific.\n\n5. **Data flow / architecture diagram (section 2)**: ASCII or Mermaid diagram showing data/event flow, key state machines, boundaries.\n\n6. **ADR (section 3)**: For any decision that could be reversed later, write ADR to `.specs/adr/<NNN>-<title>.md` with Context / Decision / Consequences structure.\n\n7. **Risk assessment (section 4)**: At least 3 risks (implementation / launch / long-term debt), each with mitigation.\n\n8. **Out of scope (section 5)**: Explicitly list what this design does NOT solve but will need future attention.\n\n9. **Architecture sedimentation suggestions (section 9)**: If this change introduces project-level reusable value (new abstractions, tech decisions, cross-module contracts, dependency changes, forbidden-list updates), fill section 9. Otherwise write \"No architecture sedimentation suggestions for this change.\"\n\n10. **UI-DESIGN.md (frontend only)**: If project is frontend, load `flow-comet-ui-design` skill. Produce design tokens (OKLCH colors, fonts, spacing, animation), anti-AI-slop check, visual north star.\n\n11. **LESSONS scan**: Grep `.specs/LESSONS.md` for keywords related to touched modules or tech decisions. If active lessons hit, declare difference or confirm still applies.\n\nThe full design protocol, templates, and anti-patterns are in:\n- `flow-kit/prompts/2-design.md` (DESIGN phase)\n- `flow-kit/prompts/2a-ui-design.md` (UI-DESIGN phase, frontend only)\n\n### Completion reasoning\n\nThis node is truly done when:\n- `.specs/<change-id>/DESIGN.md` exists with section 0 (tech stack selected) populated.\n- Section 0.5 (existing architecture alignment) is populated for brownfield projects.\n- Each technical decision has alternatives + reason + trade-off.\n- At least 1 data flow / architecture diagram exists.\n- Risk section has at least 3 items with mitigations.\n- User has confirmed tech stack and key decisions.\n- For frontend: `.specs/<change-id>/UI-DESIGN.md` exists with design tokens.\n\n### Red flags\n\n- **Agent thought**: \"Tech stack is obvious from the project, no need to ask.\" **Actual risk**: Choosing tech stack without user confirmation violates the interactive protocol. Always present cards and wait.\n- **Agent thought**: \"I know the module boundaries from memory.\" **Actual risk**: Not grepping actual module boundaries leads to DESIGN.md section 0.5 referencing non-existent paths or missing real touched modules. Must grep, not guess.\n- **Agent thought**: \"Section 0.5 is optional for small changes.\" **Actual risk**: Even small changes on brownfield projects can accidentally touch forbidden modules. Section 0.5 is mandatory when CONTEXT.md exists.\n- **Agent thought**: \"ADR is only for big decisions.\" **Actual risk**: Any decision that could be reversed later needs an ADR. Missing ADRs mean future changes cannot trace why the current approach was chosen.\n- **Agent thought**: \"DESIGN.md can include full code implementations.\" **Actual risk**: Violates R3.1 (Architect does not write implementation code). Pseudocode and function signatures are OK; full function bodies are not.\n\n## Entry Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs entry design\n```\n\n## Skill Implementation\n\nThe design node reads CHANGE.md and REQUIREMENT.md, then produces DESIGN.md through interactive tech stack selection, architecture alignment (grepping actual modules), technical decisions with ADRs, and risk assessment. For frontend projects, it additionally loads `flow-comet-ui-design` to produce UI-DESIGN.md with design tokens and visual specifications.\n\n## Required Skill Calls\n\n| Skill | Enforcement | Reason |\n|-------|-------------|--------|\n| `flow-comet-ui-design` | Required for frontend projects | Produces UI-DESIGN.md with design tokens, anti-AI-slop check, visual north star |\n\n## Output Schemas\n\nSchema: `flowkit.design.v1`\n\n| Schema ID | Artifact Kind | Required | Path |\n|-----------|--------------|----------|------|\n| `design-doc` | file | yes | `.specs/<change-id>/DESIGN.md` or `.specs/<change-id>/DESIGN-lite.md` |\n| `ui-design-doc` | file | yes (frontend) | `.specs/<change-id>/UI-DESIGN.md` |\n| `adr-docs` | file | no | `.specs/adr/<NNN>-<title>.md` (0-N files) |\n\nEvidence: `design-summary` (required)\n\n## Evidence Record\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-state.mjs record design '{\"summary\":\"DESIGN.md produced with tech stack, architecture alignment, ADRs, risks\"}'\n```\n\n## Guardrails\n\n| Guardrail ID | Label | Validation Type |\n|--------------|-------|-----------------|\n| `design-artifacts` | DESIGN.md exists with section 0 | artifact-exists |\n| `architecture-aligned` | Section 0.5 populated for brownfield | content-check |\n| `ui-design-artifacts` | UI-DESIGN.md exists for frontend projects | artifact-exists (conditional) |\n\n## Exit Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs exit design --apply\n```\n\nIf the script prints `SKILL: flow-comet-plan`, load that Skill next.\n\n## Recovery\n\n1. Re-run entry check to confirm workflow state.\n2. Read `.specs/<change-id>/DESIGN.md` — if exists with section 0 populated and user confirmed, design phase is done.\n3. If DESIGN.md exists but incomplete, resume from the first missing section (check 0, 0.5, 1-5, 9).\n4. If frontend project: check `.specs/<change-id>/UI-DESIGN.md` existence.\n5. Do not repeat confirmed decisions. Resume from the first incomplete artifact.\n",
|
|
90
|
-
"references": [],
|
|
91
|
-
"scripts": [],
|
|
92
|
-
"hash": "2de0b6f8b49bcaf18a4d37dd8d2791c52f6392332caea32a68714a77df600197"
|
|
93
|
-
}
|
|
94
|
-
]
|
|
95
|
-
},
|
|
96
|
-
{
|
|
97
|
-
"query": "flow-comet-ui-design",
|
|
98
|
-
"preferenceIndex": 4,
|
|
99
|
-
"status": "available",
|
|
100
|
-
"sources": [
|
|
101
|
-
{
|
|
102
|
-
"name": "flow-comet-ui-design",
|
|
103
|
-
"preferenceIndex": 4,
|
|
104
|
-
"platform": "claude-code",
|
|
105
|
-
"scope": "project",
|
|
106
|
-
"origin": "project",
|
|
107
|
-
"factory": {
|
|
108
|
-
"query": "flow-comet-ui-design"
|
|
109
|
-
},
|
|
110
|
-
"root": ".flow-comet/skills/flow-comet-ui-design",
|
|
111
|
-
"description": "flow-kit 2a UI-DESIGN 阶段协议:美学方向 + design tokens + 反 AI-slop 自检。仅前端项目触发。",
|
|
112
|
-
"skillMd": "---\nname: flow-comet-ui-design\ndescription: \"flow-kit 2a UI-DESIGN 阶段协议:美学方向 + design tokens + 反 AI-slop 自检。仅前端项目触发。\"\n---\n\n# flow-kit UI-DESIGN Protocol\n\n本 Skill 为前端项目提供 flow-kit 的 2a UI-DESIGN 阶段。\n\n## 加载\n\n读取 `flow-kit/prompts/2a-ui-design.md` 并按其执行。\n\n## 关键检查\n\n- `flow-kit/reference/ui-anti-patterns.md`(75 行可全读)\n- `flow-kit/reference/ui-aesthetics.md`(仅查「5 维度」+ 「给 AI 的模板」节)\n- 装了 ui-ux-pro-max / impeccable 时优先用它们\n\n## 产物\n\n- `.specs/<change-id>/UI-DESIGN.md`(含 design tokens frontmatter)\n\n## Comet 集成\n\n仅前端项目触发。非前端项目跳过。\n",
|
|
113
|
-
"references": [],
|
|
114
|
-
"scripts": [],
|
|
115
|
-
"hash": "5b0fc7335e98fcd485c513a8bf104088ac6661f6e6d583f426acbfe84ffd9a1e"
|
|
116
|
-
}
|
|
117
|
-
]
|
|
118
|
-
},
|
|
119
|
-
{
|
|
120
|
-
"query": "flow-comet-task",
|
|
121
|
-
"preferenceIndex": 5,
|
|
122
|
-
"status": "available",
|
|
123
|
-
"sources": [
|
|
124
|
-
{
|
|
125
|
-
"name": "flow-comet-task",
|
|
126
|
-
"preferenceIndex": 5,
|
|
127
|
-
"platform": "claude-code",
|
|
128
|
-
"scope": "project",
|
|
129
|
-
"origin": "project",
|
|
130
|
-
"factory": {
|
|
131
|
-
"query": "flow-comet-task"
|
|
132
|
-
},
|
|
133
|
-
"root": ".flow-comet/skills/flow-comet-task",
|
|
134
|
-
"description": "flow-kit TASK 阶段协议:拆原子任务(XML 格式)、read_files/write_files 边界、波次划分、并行标记 [P]。Comet plan producer 的 flow-kit 实现。",
|
|
135
|
-
"skillMd": "---\nname: flow-comet-task\ndescription: \"flow-kit TASK 阶段协议:拆原子任务(XML 格式)、read_files/write_files 边界、波次划分、并行标记 [P]。Comet plan producer 的 flow-kit 实现。\"\n---\n\n# flow-kit TASK Protocol\n\n本 Skill 替代 Comet plan 阶段的默认实现,使用 flow-kit 的 TASK 拆解流程。\n\n## 加载\n\n读取 `flow-kit/prompts/3-task.md` 并按其执行。关键步骤:\n\n1. **Artifact Preflight**:检查 REQUIREMENT.md + DESIGN.md 存在\n2. **拆解原则**:\n - 大小:fresh context 2~10 分钟可完成\n - 粒度:按文件冲突切(垂直切片),不按层切\n - 并行标记 `[P]`:互不冲突的任务\n - 依赖:`depends_on: <task-id>`\n3. **每任务 7 字段**:id / name / read_files / write_files / action / verify / done\n4. **波次划分**:同层并行,跨层串行\n5. **XML 格式**:便于 AI 解析与执行\n\n## 产物\n\n- `.specs/<change-id>/TASK.md`(XML 格式任务列表 + 波次划分图)\n\n## Comet 集成\n\n本 Skill 满足 `comet.plan.v1` Output Schema。TASK.md 完成后由 Comet 推进到 execute 阶段。\nComet 的 subagent-driven-development 可利用波次划分实现并行执行。\n",
|
|
136
|
-
"references": [],
|
|
137
|
-
"scripts": [],
|
|
138
|
-
"hash": "fd60fb76c1a50b1e5c1d6e9ad7eae77aad15269471e3d2b60468228182a2b0a8"
|
|
139
|
-
}
|
|
140
|
-
]
|
|
141
|
-
},
|
|
142
|
-
{
|
|
143
|
-
"query": "flow-comet-execute",
|
|
144
|
-
"preferenceIndex": 6,
|
|
145
|
-
"status": "available",
|
|
146
|
-
"sources": [
|
|
147
|
-
{
|
|
148
|
-
"name": "flow-comet-execute",
|
|
149
|
-
"preferenceIndex": 6,
|
|
150
|
-
"platform": "claude-code",
|
|
151
|
-
"scope": "project",
|
|
152
|
-
"origin": "project",
|
|
153
|
-
"factory": {
|
|
154
|
-
"query": "flow-comet-execute"
|
|
155
|
-
},
|
|
156
|
-
"root": ".flow-comet/skills/flow-comet-execute",
|
|
157
|
-
"description": "Execute node for flow-comet: iterates through pending tasks in TASK.md, applying TDD, LESSONS scan, diff boundary check, and atomic commits for each. Do not use for ordinary standalone tasks.",
|
|
158
|
-
"skillMd": "---\nname: flow-comet-execute\ndescription: \"Execute node for flow-comet: iterates through pending tasks in TASK.md, applying TDD, LESSONS scan, diff boundary check, and atomic commits for each. Do not use for ordinary standalone tasks.\"\n---\n\n# Execute\n\n## Node Goal\n\nThis node executes all pending tasks from TASK.md one by one, applying the full dev protocol for each: TDD (RED/GREEN/REFACTOR), LESSONS scan, existing abstraction grep, self-review, diff boundary verification, and atomic commits. It produces a SUMMARY.md per task and marks each task as done in TASK.md. This is the core implementation node where code is actually written.\n\n## Guidance\n\n### Prerequisites\n\n- `.specs/<change-id>/TASK.md` must exist with at least one `status=\"pending\"` task.\n- `.specs/<change-id>/DESIGN.md` or `DESIGN-lite.md` must exist — agent must read section 0 (tech stack) and section 0.5 (architecture alignment).\n- `.specs/LESSONS.md` must exist (or be created from template if missing).\n- For frontend/UI tasks: `.specs/<change-id>/UI-DESIGN.md` must exist.\n\n### Steps\n\nFor each pending task in TASK.md, execute the following sequence:\n\n1. **Read task block**: Extract the `<task>` XML block. Read `action`, `read_files`, `write_files`, `verify`, `done`. If ambiguous, stop and ask — do not guess.\n\n2. **Grep existing abstractions (R6.4)**: Before writing any code, grep the project for each capability mentioned in `action`. Check: HTTP clients, date formatting, state management, repository patterns, error handling, custom hooks. Use the actual grep commands from `4-dev.md` section 1.4.1. Record results in SUMMARY.md \"6-dimension self-check\" section.\n\n3. **Scan LESSONS (R1.8)**: Grep `.specs/LESSONS.md` using keywords from task files and action. For each active hit: declare \"Reviewed L-NNN, difference is X\" or \"Reviewed L-NNN, still applies, will not retry\". If plan matches an active lesson exactly — stop and answer \"difference from last time is X\".\n\n4. **UI task extra check (1.6)**: If task involves `.css`/`.tsx`/`.vue`/`.html` files or UI keywords: load UI-DESIGN.md, load `ui-anti-patterns.md`, load `frontend-engineer-rules.md` (sections 1, 2, 10 mandatory). Declare each hit from anti-patterns. Colors/fonts/spacing must come from CSS variables derived from UI-DESIGN.md frontmatter — no hardcoded values.\n\n5. **Schema migration check (R4.5, section 1.7)**: If task involves table/field changes: declare schema diff, select migration mechanism (detect Prisma/Alembic/Rails/Knex/Flyway/Liquibase), generate reversible migration with up+down, detect DB credentials to decide whether to execute now or defer.\n\n6. **Breaking change check (R4.6, section 1.8)**: If task deletes >= 5 lines, changes public exports, changes public API, or deletes files: grep reference graph, list impact, ask user for handling approach (direct delete + sync / deprecation period / codemod / abort).\n\n7. **TDD (section 2)**: RED (write failing test from AC/done) -> confirm failure -> GREEN (minimal code to pass) -> confirm pass -> REFACTOR (improve under test protection). Exception: pure doc/config tasks can skip TDD with explanation in SUMMARY.\n\n8. **Run verify (section 3)**: Execute the `<verify>` command. Paste real output into SUMMARY.md. Only proceed if verify passes.\n\n9. **Self-review (section 4)**: If brooks-lint installed: run `/brooks-review`. Critical must be fixed before commit. Otherwise: 6-dimension quick check (R1 Cognitive Overload, R2 Change Propagation, R3 Knowledge Duplication, R4 Accidental Complexity, R5 Dependency Disorder, R6 Domain Model Distortion).\n\n10. **Diff boundary check (R6.5, section 5)**: Run `git diff --name-only HEAD` and `git status --short`. Compare against TASK.md `write_files`. Any out-of-boundary files must be reverted or explicitly approved. Record in SUMMARY.md \"boundary check\" section.\n\n11. **Atomic commit (R4.1, section 5.5)**: Format: `<type>(<change-id>): <task-id> <subject>`. Code + test in same commit.\n\n12. **Write SUMMARY.md (section 6)**: Use `flow-kit/templates/SUMMARY.md` template. Save to `.specs/<change-id>/<task-id>-SUMMARY.md`. Must include: what changed, which files, verify output, 6-dimension self-check, boundary check.\n\n13. **Mark done (section 7)**: Update TASK.md task status to \"done\" with timestamp.\n\n14. **Move to next pending task**: Repeat from step 1.\n\n15. **All done**: Run exit check.\n\nThe full dev protocol, templates, and constraints are in:\n- `flow-kit/prompts/4-dev.md` (DEV phase)\n\n### Completion reasoning\n\nThis node is truly done when:\n- All tasks in TASK.md have `status=\"done\"`.\n- Every done task has a corresponding `<task-id>-SUMMARY.md` in `.specs/<change-id>/`.\n- Every SUMMARY.md contains: verify output (real, not fabricated), 6-dimension self-check, boundary check.\n- No REQUIREMENT.md or DESIGN.md has been modified during execution.\n- No out-of-boundary files have been changed without explicit approval.\n\n### Red flags\n\n- **Agent thought**: \"I'll write the code first, then grep for existing abstractions.\" **Actual risk**: Writing code without grepping first (R6.4 violation) leads to duplicate implementations. Must grep BEFORE writing.\n- **Agent thought**: \"LESSONS scan is optional for simple tasks.\" **Actual risk**: Skipping LESSONS scan (R1.8 violation) means repeating known failures. Even simple tasks can hit documented pitfalls.\n- **Agent thought**: \"verify passed in my head, marking done.\" **Actual risk**: Marking done without running verify (R2.4 violation) means untested code enters review. Must paste real output.\n- **Agent thought**: \"I see a bug in an adjacent file, let me fix it along the way.\" **Actual risk**: \"Fixing along the way\" without a new task or CHANGE violates R7.1 (scope control). Must stop and create a new task or CHANGE.\n- **Agent thought**: \"This task is taking long, let me skip the self-review.\" **Actual risk**: Skipping self-review defers quality issues to the review node, where they become Critical items requiring fix tasks. Better to catch early.\n\n## Entry Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs entry execute\n```\n\n## Skill Implementation\n\nThe execute node loads `flow-comet-dev` for each task execution. It iterates through all pending tasks in TASK.md, applying the full dev protocol: TDD, LESSONS scan, existing abstraction grep, self-review (brooks-lint or 6-dimension quick check), diff boundary verification, and atomic commits. Each task produces a SUMMARY.md and is marked done in TASK.md.\n\n## Required Skill Calls\n\n| Skill | Enforcement | Reason |\n|-------|-------------|--------|\n| `flow-comet-dev` | Required for each task execution | Provides TDD protocol, LESSONS scan, 6-dimension self-check, diff boundary rules, schema migration, breaking change protocol |\n\n## Output Schemas\n\nSchema: `flowkit.execution.v1`\n\n| Schema ID | Artifact Kind | Required | Path |\n|-----------|--------------|----------|------|\n| `task-summaries` | file | yes | `.specs/<change-id>/*-SUMMARY.md` (one per task) |\n| `task-plan-updated` | file | yes | `.specs/<change-id>/TASK.md` (status=\"done\" for all) |\n\nEvidence: `implementation-summary` (required)\n\n## Evidence Record\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-state.mjs record execute '{\"summary\":\"All N tasks completed, each with SUMMARY.md and verify output\"}'\n```\n\n## Guardrails\n\n| Guardrail ID | Label | Validation Type |\n|--------------|-------|-----------------|\n| `build-evidence` | At least one SUMMARY.md produced | artifact-exists |\n| `all-tasks-done` | All tasks in TASK.md have status=\"done\" | content-check |\n| `verify-output-real` | Every SUMMARY.md has verify output (not fabricated) | content-check |\n| `no-design-changes` | REQUIREMENT.md and DESIGN.md not modified | file-unchanged |\n\n## Exit Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs exit execute --apply\n```\n\nAfter exit, run `node .claude/skills/flow-comet/scripts/workflow-state.mjs next` to get the next node.\n\n## Recovery\n\n1. Re-run entry check to confirm workflow state.\n2. Read `.specs/<change-id>/TASK.md` — find first `status=\"pending\"` task.\n3. Read any existing `<task-id>-SUMMARY.md` files to confirm completed progress.\n4. Check for `<task-id>-PROGRESS.md` files — if found, read \"excluded solutions\" section to avoid repeating failures (R1.6).\n5. Resume from the first pending task. Do not repeat completed tasks.\n6. If a PROGRESS.md exists for the current task, delete it after completion and migrate useful info to SUMMARY.md.\n",
|
|
159
|
-
"references": [],
|
|
160
|
-
"scripts": [],
|
|
161
|
-
"hash": "8afca756495b43947e3e2bd4d0d9d284976a881d1022c6264a1011c0a9ea4d84"
|
|
162
|
-
}
|
|
163
|
-
]
|
|
164
|
-
},
|
|
165
|
-
{
|
|
166
|
-
"query": "flow-comet-dev",
|
|
167
|
-
"preferenceIndex": 7,
|
|
168
|
-
"status": "available",
|
|
169
|
-
"sources": [
|
|
170
|
-
{
|
|
171
|
-
"name": "flow-comet-dev",
|
|
172
|
-
"preferenceIndex": 7,
|
|
173
|
-
"platform": "claude-code",
|
|
174
|
-
"scope": "project",
|
|
175
|
-
"origin": "project",
|
|
176
|
-
"factory": {
|
|
177
|
-
"query": "flow-comet-dev"
|
|
178
|
-
},
|
|
179
|
-
"root": ".flow-comet/skills/flow-comet-dev",
|
|
180
|
-
"description": "flow-kit DEV 阶段协议:TDD + 6 维自查 + diff 边界 verify + LESSONS 扫描 + R4.5 Schema 迁移 + R4.6 破坏性变更。Comet execute/subagent-execute 的 flow-kit 增强。",
|
|
181
|
-
"skillMd": "---\nname: flow-comet-dev\ndescription: \"flow-kit DEV 阶段协议:TDD + 6 维自查 + diff 边界 verify + LESSONS 扫描 + R4.5 Schema 迁移 + R4.6 破坏性变更。Comet execute/subagent-execute 的 flow-kit 增强。\"\n---\n\n# flow-kit DEV Protocol\n\n本 Skill 为 Comet execute 阶段提供 flow-kit 的完整开发规则集。\n\n## 加载\n\n读取 `flow-kit/prompts/4-dev.md` 并按其执行。以下是核心规则摘要(完整内容以 prompt 文件为准):\n\n### 必跑检查\n\n1. **沿用既有抽象 grep(R6.4)**:写代码前 grep 同类抽象,找到了 import 用\n2. **LESSONS 扫描(R1.8)**:grep `.specs/LESSONS.md`,命中 active 条目必须声明差异\n3. **TDD(RED→GREEN→REFACTOR)**:先写失败测试,再写最少代码通过\n4. **6 维自查**:brooks-lint 已装则 `/brooks-review`,未装则内置 R1~R6 快查\n5. **diff 边界 verify(R6.5)**:`git diff --name-only` 与 TASK write_files 比对,越界必须回滚\n6. **原子提交**:`<type>(<change-id>): <task-id> <subject>`\n\n### 条件检查\n\n7. **Schema 迁移协议(R4.5)**:涉及 ORM model 变更时,必须生成迁移文件(含 up/down)\n8. **破坏性变更协议(R4.6)**:删 ≥5 行 / 改公共接口时,grep 引用图 + 反问用户\n\n### 上下文恢复\n\n- **断点恢复**:新会话时 `workflow-state.mjs status` 自动检测当前 change 和 pending task,从上次断点继续\n- **反重复检查**:恢复后读 `.specs/LESSONS.md` 确认不在已排除方案里(R1.8)\n- **进度记录**:TASK.md 的 `status=\"done|pending\"` + SUMMARY.md 就是进度,不需要额外的 PROGRESS.md 或 STATE.md\n\n## 产物\n\n- 代码改动\n- `.specs/<change-id>/<task-id>-SUMMARY.md`(使用 `flow-kit/templates/SUMMARY.md`)\n\n## Comet 集成\n\n每个 task 通过 Comet execute 或 subagent-execute 执行。子代理执行时必须加载本 Skill 并回传 evidence。\n",
|
|
182
|
-
"references": [],
|
|
183
|
-
"scripts": [],
|
|
184
|
-
"hash": "de5a1e001001645d1a4632f45f21638f1a010b8af0570d4636ec9afa1d3550cf"
|
|
185
|
-
}
|
|
186
|
-
]
|
|
187
|
-
},
|
|
188
|
-
{
|
|
189
|
-
"query": "flow-comet-subagent-execute",
|
|
190
|
-
"preferenceIndex": 8,
|
|
191
|
-
"status": "available",
|
|
192
|
-
"sources": [
|
|
193
|
-
{
|
|
194
|
-
"name": "flow-comet-subagent-execute",
|
|
195
|
-
"preferenceIndex": 8,
|
|
196
|
-
"platform": "claude-code",
|
|
197
|
-
"scope": "project",
|
|
198
|
-
"origin": "project",
|
|
199
|
-
"factory": {
|
|
200
|
-
"query": "flow-comet-subagent-execute"
|
|
201
|
-
},
|
|
202
|
-
"root": ".flow-comet/skills/flow-comet-subagent-execute",
|
|
203
|
-
"description": "Subagent Execute node for flow-comet: delegates parallel (parallel=true) tasks to subagents with flow-comet-dev loaded, collecting handoff evidence. Do not use for ordinary standalone tasks.",
|
|
204
|
-
"skillMd": "---\nname: flow-comet-subagent-execute\ndescription: \"Subagent Execute node for flow-comet: delegates parallel (parallel=true) tasks to subagents with flow-comet-dev loaded, collecting handoff evidence. Do not use for ordinary standalone tasks.\"\n---\n\n# Subagent Execute\n\n## Node Goal\n\nThis node parallelizes execution by delegating independent tasks (marked `parallel=\"true\"` in TASK.md) to separate subagents. Each subagent loads the full `flow-comet-dev` protocol and operates within its task's `read_files`/`write_files` boundaries. This node produces handoff evidence for each delegated task and marks them done in TASK.md after all subagents complete. It exists to exploit parallelism when tasks have no file conflicts.\n\n## Guidance\n\n### Prerequisites\n\n- `.specs/<change-id>/TASK.md` must exist with at least one task marked `parallel=\"true\"` and `status=\"pending\"`.\n- `.specs/<change-id>/DESIGN.md` or `DESIGN-lite.md` must exist.\n- `.specs/LESSONS.md` must exist (or be created).\n- The orchestrating agent must have the `Agent` tool available for spawning subagents.\n\n### Steps\n\n1. **Identify parallel tasks**: Read TASK.md and find all tasks with `parallel=\"true\"` and `status=\"pending\"`. Verify they are genuinely independent (no file conflicts between them — check `write_files` do not overlap).\n\n2. **For each parallel task, create handoff request**: Use `workflow-handoff.mjs request <task-id>` to register the handoff. The handoff prompt must include:\n - The task's full XML block from TASK.md.\n - DESIGN.md sections 0 and 0.5 for context.\n - REQUIREMENT.md ACs relevant to this task.\n - Explicit instruction to load `flow-comet-dev` and follow its full protocol.\n - The task's `read_files` and `write_files` boundaries.\n - Instruction to produce `<task-id>-SUMMARY.md` in `.specs/<change-id>/`.\n\n3. **Delegate to subagents**: Use the `Agent` tool with `isolation: \"worktree\"` for each parallel task. Each subagent:\n - Reads TASK.md for its specific task block.\n - Executes the full TDD protocol (RED/GREEN/REFACTOR).\n - Greps existing abstractions (R6.4).\n - Scans LESSONS (R1.8).\n - Runs verify command and records real output.\n - Performs self-review (brooks-lint or 6-dimension quick check).\n - Performs diff boundary check (R6.5).\n - Makes atomic commit with format `<type>(<change-id>): <task-id> <subject>`.\n - Writes `<task-id>-SUMMARY.md` to `.specs/<change-id>/`.\n - Returns evidence via `workflow-handoff.mjs result <task-id>`.\n\n4. **Collect evidence**: After all subagents complete, verify each returned:\n - SUMMARY.md exists in `.specs/<change-id>/`.\n - Verify output is real (not fabricated).\n - Handoff evidence is recorded.\n\n5. **Mark done**: Update TASK.md — set `status=\"done\"` for all completed parallel tasks.\n\n6. **Record overall evidence**: Run workflow-state.mjs to record completion.\n\n7. **Exit check**: Run exit check.\n\n### Completion reasoning\n\nThis node is truly done when:\n- All delegated parallel tasks have `status=\"done\"` in TASK.md.\n- Every delegated task has a `<task-id>-SUMMARY.md` in `.specs/<change-id>/`.\n- Handoff evidence (request + result) is recorded for each task.\n- No subagent exceeded its `write_files` boundary.\n- No serial tasks were delegated (only `parallel=\"true\"` tasks).\n\n### Red flags\n\n- **Agent thought**: \"This task looks independent, I'll delegate it.\" **Actual risk**: Delegating tasks that are not marked `parallel=\"true\"` bypasses the wave division logic. Only tasks explicitly marked parallel should be delegated.\n- **Agent thought**: \"Subagent can figure out what to do from context.\" **Actual risk**: Subagent not loading `flow-comet-dev` means it skips TDD, LESSONS scan, diff boundary check, and self-review. The handoff prompt must explicitly require flow-comet-dev.\n- **Agent thought**: \"Subagent might need to touch related files for context.\" **Actual risk**: Subagent exceeding `write_files` boundaries creates merge conflicts with other parallel subagents. Strict boundary enforcement is mandatory.\n- **Agent thought**: \"One subagent finished, mark it done immediately.\" **Actual risk**: Marking tasks done before all subagents complete can cause issues if a later subagent fails and needs to reference completed work. Wait for all, then batch mark.\n\n## Entry Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs entry subagent-execute\n```\n\n## Skill Implementation\n\nThe subagent-execute node identifies all `parallel=\"true\"` pending tasks in TASK.md, creates handoff requests via `workflow-handoff.mjs`, and delegates each to an isolated subagent (worktree isolation) with `flow-comet-dev` loaded. Each subagent executes the full dev protocol independently. The orchestrator collects evidence and marks tasks done after all subagents complete.\n\n## Required Skill Calls\n\n| Skill | Enforcement | Reason |\n|-------|-------------|--------|\n| `flow-comet-dev` | Required in each subagent's prompt | Provides TDD, LESSONS scan, diff boundary, self-review protocol for each parallel task |\n| `superpowers:subagent-driven-development` | Required for delegation pattern | Provides the Agent tool invocation pattern for parallel task execution |\n\n## Output Schemas\n\nSchema: `flowkit.handoff.v1`\n\n| Schema ID | Artifact Kind | Required | Path |\n|-----------|--------------|----------|------|\n| `task-summaries` | file | yes | `.specs/<change-id>/*-SUMMARY.md` (one per delegated task) |\n| `handoff-evidence` | evidence | yes | Recorded via workflow-handoff.mjs |\n\nEvidence: `handoff-request` (required per task), `handoff-result` (required per task)\n\n## Evidence Record\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-state.mjs record subagent-execute '{\"summary\":\"N parallel tasks delegated and completed, handoff evidence recorded for each\"}'\n```\n\n## Guardrails\n\n| Guardrail ID | Label | Validation Type |\n|--------------|-------|-----------------|\n| `handoff-evidence` | Handoff evidence recorded for each task | evidence-only |\n| `parallel-only` | Only parallel=\"true\" tasks delegated | content-check |\n| `boundary-safe` | No subagent exceeded write_files | content-check |\n| `summaries-exist` | SUMMARY.md exists for each delegated task | artifact-exists |\n\n## Exit Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs exit subagent-execute --apply\n```\n\nIf the script prints `SKILL: flow-comet-review`, load that Skill next.\n\n## Recovery\n\n1. Re-run entry check to confirm workflow state.\n2. Read `.specs/<change-id>/TASK.md` — identify which parallel tasks are still `status=\"pending\"`.\n3. Check for existing `<task-id>-SUMMARY.md` files — tasks with summaries are done even if TASK.md not updated.\n4. Re-delegate only the remaining pending parallel tasks.\n5. If a subagent failed mid-execution, check for `<task-id>-PROGRESS.md` and use its \"excluded solutions\" to avoid repeating failures.\n",
|
|
205
|
-
"references": [],
|
|
206
|
-
"scripts": [],
|
|
207
|
-
"hash": "045cad1fd0d844d6faab14e4d340beb8feae3bc60e2d1342bdb8a09182b9cc0e"
|
|
208
|
-
}
|
|
209
|
-
]
|
|
210
|
-
},
|
|
211
|
-
{
|
|
212
|
-
"query": "flow-comet-review",
|
|
213
|
-
"preferenceIndex": 9,
|
|
214
|
-
"status": "available",
|
|
215
|
-
"sources": [
|
|
216
|
-
{
|
|
217
|
-
"name": "flow-comet-review",
|
|
218
|
-
"preferenceIndex": 9,
|
|
219
|
-
"platform": "claude-code",
|
|
220
|
-
"scope": "project",
|
|
221
|
-
"origin": "project",
|
|
222
|
-
"factory": {
|
|
223
|
-
"query": "flow-comet-review"
|
|
224
|
-
},
|
|
225
|
-
"root": ".flow-comet/skills/flow-comet-review",
|
|
226
|
-
"description": "Review node for flow-comet: performs 4-round review (spec compliance, code quality 6-dimension decay, UI visual, optional debt assessment) and produces REVIEW.md. Do not use for ordinary standalone tasks.",
|
|
227
|
-
"skillMd": "---\nname: flow-comet-review\ndescription: \"Review node for flow-comet: performs 4-round review (spec compliance, code quality 6-dimension decay, UI visual, optional debt assessment) and produces REVIEW.md. Do not use for ordinary standalone tasks.\"\n---\n\n# Review\n\n## Node Goal\n\nThis node performs a structured multi-round review of the implemented change, checking spec compliance, code quality across 6 decay dimensions, UI visual consistency (frontend only), and optional tech debt assessment. It produces REVIEW.md and generates fix tasks (T-FIX-NN) for any Critical or Major findings. The review node is the quality gate before integration — nothing enters verify without passing this node's checks.\n\n## Guidance\n\n### Prerequisites\n\n- All tasks in TASK.md must have `status=\"done\"`.\n- `<task-id>-SUMMARY.md` must exist for every completed task.\n- `.specs/<change-id>/REQUIREMENT.md`, `DESIGN.md`, `TASK.md` must exist.\n- `.specs/<change-id>/TEST.md` must exist (from 5-test or produced during review).\n- For frontend projects: `.specs/<change-id>/UI-DESIGN.md` must exist.\n- The reviewer agent must NOT modify code directly (R3.3) — only produce reports and fix tasks.\n\n### Steps\n\n1. **Round 1 — Spec compliance**: For each AC in REQUIREMENT.md:\n - Check if implemented (link to code/file).\n - Check if tested (link to TEST.md).\n - Check no out-of-scope content was introduced.\n - Check no unplanned features were added.\n - Check no DESIGN.md architecture was violated.\n\n2. **Round 2 — Code quality (6 decay risks)**: Diagnose the diff across 6 dimensions from brooks-lint:\n - **R1 Cognitive Overload**: Is the code hard to understand? (>50 line functions, >3 nesting levels)\n - **R2 Change Propagation**: Does changing one thing break unrelated parts?\n - **R3 Knowledge Duplication**: Is the same business rule/constant expressed in multiple places? (Conceptual, not literal code duplication)\n - **R4 Accidental Complexity**: Is the code more complex than the problem requires?\n - **R5 Dependency Disorder**: Do dependencies flow consistently (high -> low layer)?\n - **R6 Domain Model Distortion**: Does the code faithfully reflect the business domain?\n\n If brooks-lint installed: run `/brooks-review` and paste output verbatim. Otherwise: diagnose with 4-element format (Symptom/Source/Consequence/Remedy) with file:line references and book citations.\n\n3. **Round 2.0 — TEST.md 5-round pyramid completeness**: Before code quality, verify TEST.md:\n - All 5 rounds have clear status (no unfilled).\n - Skipped rounds have reasons.\n - Round 1 (functional): every AC has coverage.\n - Round 2 (performance): if required, has actual/budget/baseline columns.\n - Round 3 (security): if required, has dependency/secret/SAST/OWASP records.\n - Round 4 (compatibility): if required, has browser matrix/migration/cross-version.\n - Round 5 (observability): if required, has log/metric/alert/health check.\n - Any gap -> mark Critical, return to 5-test first.\n\n4. **Round 2.2 — Architecture dependency check (large changes)**: If change adds top-level modules, has dangerous imports, introduces new middleware/services, or spans >= 5 modules: run `/brooks-audit` (or draw simplified Mermaid dependency graph). Check for circular dependencies, reverse dependencies, cross-boundary imports.\n\n5. **Round 3 — UI visual review (frontend only)**: If change has UI-DESIGN.md or touches UI files:\n - **3.1 Design tokens**: All colors from UI-DESIGN.md CSS variables? No hardcoded hex/font-size/spacing?\n - **3.2 Anti-pattern scan**: Check against `ui-anti-patterns.md` (fonts, colors, shadows, borders, animations, layout, copy, components).\n - **3.3 Visual north star**: If you only saw the implementation screenshot, would you recognize the declared visual tone?\n - **3.4 Accessibility quick check**: WCAG 2.1 AA contrast, keyboard reachable, focus ring visible, reduced-motion support, form label association, image alt text.\n\n6. **Round 4 — Optional supplements**:\n - **4.1 Tech debt assessment**: If milestone/quarterly release, run `/brooks-debt`. Categorize findings into Critical (fix now) / Scheduled (next 1-3 iterations) / Monitored (record only).\n - **4.2 Cross-model spot-check**: If involves security/auth/concurrency/single function >80 lines/coverage drop: run same review with another model, record divergence.\n\n7. **Severity grading**: Each finding gets:\n - Critical (must fix: data corruption, security, AC not met)\n - Major (should fix: design issues, significant regression)\n - Minor (optional: naming, style, small refactor)\n\n8. **Generate fix tasks**: For all Critical and decided-to-fix Major findings, append to TASK.md as `T-FIX-NN` with full 7 fields, then trigger return to execute node.\n\nThe full review protocol, templates, and checklists are in:\n- `flow-kit/prompts/6-review.md` (REVIEW phase)\n- `flow-kit/prompts/5-test.md` (TEST phase, for test pyramid completeness)\n\n### Completion reasoning\n\nThis node is truly done when:\n- `.specs/<change-id>/REVIEW.md` exists with all 3 mandatory rounds completed.\n- Every finding has a severity label and file:line reference.\n- All Critical items are either fixed (fix tasks generated) or explicitly accepted with user confirmation.\n- 0 unacknowledged Critical items remain.\n- TEST.md 5-round pyramid completeness has been verified.\n- No code was directly modified by the reviewer (R3.3).\n\n### Red flags\n\n- **Agent thought**: \"Code looks good, no issues found.\" **Actual risk**: Concluding without file:line references means the review was superficial. Every finding must point to specific code.\n- **Agent thought**: \"TEST.md exists, that's enough.\" **Actual risk**: Not checking test pyramid completeness means gaps in test coverage go undetected. Must verify all 5 rounds have clear status.\n- **Agent thought**: \"I'll fix this small issue directly.\" **Actual risk**: Reviewer modifying code violates R3.3. Must generate fix tasks instead.\n- **Agent thought**: \"Round 3 (UI) is optional.\" **Actual risk**: For frontend projects with UI changes, Round 3 is mandatory. Only non-frontend projects skip it.\n- **Agent thought**: \"6-dimension review is just a checklist.\" **Actual risk**: Without file:line references and book citations (when using built-in path), the review lacks rigor and fixability.\n\n## Entry Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs entry review\n```\n\n## Skill Implementation\n\nThe review node performs a structured 4-round review: spec compliance (Round 1), code quality with 6 decay dimensions + TEST.md completeness + architecture dependency check (Round 2), UI visual review for frontend (Round 3), and optional tech debt/cross-model supplements (Round 4). It produces REVIEW.md and generates fix tasks for Critical/Major findings. The reviewer does not modify code directly.\n\n## Required Skill Calls\n\n| Skill | Enforcement | Reason |\n|-------|-------------|--------|\n| `flow-comet-test` | Required for test pyramid completeness check | Verifies TEST.md 5-round status before code quality review |\n| `/brooks-review` | Preferred if installed | Provides book-backed 6-dimension code quality diagnosis |\n| `/brooks-audit` | Conditional (large changes) | Provides architecture dependency graph with cycle detection |\n| `/brooks-debt` | Conditional (milestones) | Provides tech debt prioritization with Pain x Spread |\n\n## Output Schemas\n\nSchema: `flowkit.review.v1`\n\n| Schema ID | Artifact Kind | Required | Path |\n|-----------|--------------|----------|------|\n| `review-doc` | file | yes | `.specs/<change-id>/REVIEW.md` |\n| `fix-tasks` | file | conditional | `.specs/<change-id>/TASK.md` (T-FIX-NN appended) |\n\nEvidence: `review-summary` (required)\n\n## Evidence Record\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-state.mjs record review '{\"summary\":\"REVIEW.md produced: N Critical, M Major, K Minor. X fix tasks generated.\"}'\n```\n\n## Guardrails\n\n| Guardrail ID | Label | Validation Type |\n|--------------|-------|-----------------|\n| `review-evidence` | REVIEW.md exists | artifact-exists |\n| `critical-resolved` | 0 unacknowledged Critical items | content-check |\n| `no-code-changes` | Reviewer did not modify code files | file-unchanged |\n| `test-pyramid-checked` | TEST.md 5-round completeness verified | content-check |\n\n## Exit Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs exit review --apply\n```\n\nIf the script prints `SKILL: flow-comet-verify`, load that Skill next.\n\n## Recovery\n\n1. Re-run entry check to confirm workflow state.\n2. Read `.specs/<change-id>/REVIEW.md` — if exists with all rounds completed and Critical resolved, review is done.\n3. If REVIEW.md exists but incomplete, check which rounds are missing and resume from there.\n4. If Critical items were found but fix tasks not yet generated, generate them now.\n5. If fix tasks were generated but not executed, return to execute node.\n6. Do not repeat completed review rounds.\n",
|
|
228
|
-
"references": [],
|
|
229
|
-
"scripts": [],
|
|
230
|
-
"hash": "2f2897318e927a0349699ff785a152cf70e939f1d1f2fc9c0e3f92d26ccc3844"
|
|
231
|
-
}
|
|
232
|
-
]
|
|
233
|
-
},
|
|
234
|
-
{
|
|
235
|
-
"query": "flow-comet-test",
|
|
236
|
-
"preferenceIndex": 10,
|
|
237
|
-
"status": "available",
|
|
238
|
-
"sources": [
|
|
239
|
-
{
|
|
240
|
-
"name": "flow-comet-test",
|
|
241
|
-
"preferenceIndex": 10,
|
|
242
|
-
"platform": "claude-code",
|
|
243
|
-
"scope": "project",
|
|
244
|
-
"origin": "project",
|
|
245
|
-
"factory": {
|
|
246
|
-
"query": "flow-comet-test"
|
|
247
|
-
},
|
|
248
|
-
"root": ".flow-comet/skills/flow-comet-test",
|
|
249
|
-
"description": "flow-kit TEST 阶段协议:5 轮测试金字塔(功能/性能/安全/兼容/可观测)+ 测试质量 6 维自检。Comet execute 阶段的 flow-kit 增强。",
|
|
250
|
-
"skillMd": "---\nname: flow-comet-test\ndescription: \"flow-kit TEST 阶段协议:5 轮测试金字塔(功能/性能/安全/兼容/可观测)+ 测试质量 6 维自检。Comet execute 阶段的 flow-kit 增强。\"\n---\n\n# flow-kit TEST Protocol\n\n本 Skill 为 Comet execute 阶段提供 flow-kit 的 5 轮测试金字塔。\n\n## 加载\n\n读取 `flow-kit/prompts/5-test.md` 并按其执行。\n\n### 5 轮测试金字塔\n\n| 轮次 | 内容 | 适用性 |\n|------|------|--------|\n| 第 1 轮 · 功能 | AC→测试映射 + 覆盖率 + 边界用例 + T1~T6 测试质量自检 | ✅ 必跑 |\n| 第 2 轮 · 性能 | Lighthouse / k6 / locust + 慢查询审计 + N+1 检测 | 按项目 |\n| 第 3 轮 · 安全 | 依赖漏洞 + 秘钥扫描 + SAST + OWASP Top 10 | 按项目 |\n| 第 4 轮 · 兼容 | 跨浏览器 + 数据迁移验证 + 跨版本 | 按项目 |\n| 第 5 轮 · 可观测 | 日志 + 指标 + 告警 + 健康检查 | 按项目 |\n\n### 测试质量 6 维自检(T1~T6)\n\n| 编号 | 风险 | 来源 |\n|------|------|------|\n| T1 | Test Obscurity 测试晦涩 | xUnit Test Patterns |\n| T2 | Test Brittleness 测试脆弱 | The Art of Unit Testing |\n| T3 | Test Duplication 测试重复 | How Google Tests Software |\n| T4 | Mock Abuse Mock 滥用 | Working Effectively with Legacy Code |\n| T5 | Coverage Illusion 覆盖率幻觉 | xUnit Test Patterns |\n| T6 | Architecture Mismatch 架构错配 | How Google Tests Software |\n\n## 产物\n\n- `.specs/<change-id>/TEST.md`(使用 `flow-kit/templates/TEST.md`)\n\n## Comet 集成\n\nTEST.md 完成后触发 review 阶段。brooks-lint 已装时用 `/brooks-test`,未装时用内置清单。\n",
|
|
251
|
-
"references": [],
|
|
252
|
-
"scripts": [],
|
|
253
|
-
"hash": "14ceed973ae4b55d88d8433128308d297defd04f76a5855d0c4b59d156e89eac"
|
|
254
|
-
}
|
|
255
|
-
]
|
|
256
|
-
},
|
|
257
|
-
{
|
|
258
|
-
"query": "flow-comet-verify",
|
|
259
|
-
"preferenceIndex": 11,
|
|
260
|
-
"status": "available",
|
|
261
|
-
"sources": [
|
|
262
|
-
{
|
|
263
|
-
"name": "flow-comet-verify",
|
|
264
|
-
"preferenceIndex": 11,
|
|
265
|
-
"platform": "claude-code",
|
|
266
|
-
"scope": "project",
|
|
267
|
-
"origin": "project",
|
|
268
|
-
"factory": {
|
|
269
|
-
"query": "flow-comet-verify"
|
|
270
|
-
},
|
|
271
|
-
"root": ".flow-comet/skills/flow-comet-verify",
|
|
272
|
-
"description": "Verify node for flow-comet: runs full automation (tests + type check + build), guides human UAT, performs failure diagnosis with max 3 auto-retries, and produces UAT.md. Do not use for ordinary standalone tasks.",
|
|
273
|
-
"skillMd": "---\nname: flow-comet-verify\ndescription: \"Verify node for flow-comet: runs full automation (tests + type check + build), guides human UAT, performs failure diagnosis with max 3 auto-retries, and produces UAT.md. Do not use for ordinary standalone tasks.\"\n---\n\n# Verify\n\n## Node Goal\n\nThis node performs the final integration verification: running all automated tests, type checks, and builds, then guiding the human through UAT scripts from TEST.md. It produces UAT.md with pass/fail results for each item. If failures occur, it diagnoses root causes, generates fix tasks, and auto-retries up to 3 rounds before pausing for human decision. This node is the final quality gate before archiving.\n\n## Guidance\n\n### Prerequisites\n\n- `.specs/<change-id>/REVIEW.md` must exist (from review node).\n- All Critical items from REVIEW.md must be resolved (fixed or explicitly accepted).\n- `.specs/<change-id>/TEST.md` must exist with UAT scripts.\n- `.specs/<change-id>/REQUIREMENT.md` must exist for AC reference.\n\n### Steps\n\n1. **Run full automation**: Execute all automated checks and paste real output:\n - Full unit tests: `pytest tests/ -q` (or equivalent).\n - Integration/e2e tests: if available.\n - Type check: `tsc --noEmit` / `mypy` / equivalent.\n - Build: `npm run build` / `vite build` / equivalent.\n - Any failure -> immediately enter failure diagnosis (step 3).\n\n2. **Guide human UAT**: Read TEST.md UAT scripts one by one. For each UAT item:\n - Present the scenario, preconditions, steps, and expected results.\n - Ask user: \"Pass / Fail / Describe issue\".\n - Record result in `.specs/<change-id>/UAT.md`.\n\n3. **Failure diagnosis**: For any failure (automated test or UAT):\n - Switch to \"Diagnose sub-role\" — identify root cause, not symptom.\n - Produce fix-plan: append to TASK.md as `T-FIX-XX` with full 7 fields and verify command.\n - Return to execute node for fix execution.\n - Re-run verification after fix.\n\n4. **Auto-retry limit (R2.6)**: Maximum 3 rounds of automatic retry. After 3rd round failure, pause and require human decision. Do not auto-retry beyond 3 rounds.\n\n5. **LESSONS nomination**: Before archiving, scan all `*-SUMMARY.md` \"decisions and deviations\" sections and any `*-PROGRESS.md` \"excluded solutions\" sections. Apply nomination criteria:\n - Debugging/trial-and-error took > 30 minutes -> nominate.\n - Error is not task-specific, other tasks would hit it too -> nominate.\n - Reasonable probability of retry within 6 months -> nominate.\n - Otherwise do not nominate (avoid pollution).\n - Add qualifying lessons to `.specs/LESSONS.md` with next L-NNN number.\n - Check existing active lessons for superseded/deprecated status.\n\nThe full verification protocol, UAT format, and failure diagnosis are in:\n- `flow-kit/prompts/7-integration.md` (INTEGRATION phase, verification + UAT sections)\n- `flow-kit/prompts/5-test.md` (TEST phase, for UAT script format)\n\n### Completion reasoning\n\nThis node is truly done when:\n- All automated checks pass with real output pasted.\n- All UAT items have pass/fail recorded in `.specs/<change-id>/UAT.md`.\n- No more than 3 auto-retry rounds were used.\n- All failures have been diagnosed and fix tasks generated.\n- LESSONS have been nominated from SUMMARY.md files.\n\n### Red flags\n\n- **Agent thought**: \"Tests passed last time, no need to run again.\" **Actual risk**: Claiming pass without pasting real output (R4.4 violation) means failures go undetected. Must run and paste.\n- **Agent thought**: \"This UAT item is similar to the last one, marking pass.\" **Actual risk**: UAT must be executed by the human, not assumed. Each item needs explicit human confirmation.\n- **Agent thought**: \"Auto-retry 4th time, maybe it'll work now.\" **Actual risk**: Beyond 3 retries (R2.6 violation), the problem is likely systematic, not transient. Must pause for human decision.\n- **Agent thought**: \"Fix the failure directly, no need for a fix task.\" **Actual risk**: Bypassing the fix-task -> execute -> re-verify cycle means the fix is not properly tracked or tested. Must go through the proper loop.\n\n## Entry Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs entry verify\n```\n\n## Skill Implementation\n\nThe verify node loads `flow-comet-integration` for the verification protocol. It runs all automated checks (tests, type check, build), guides the human through UAT scripts from TEST.md, performs failure diagnosis with max 3 auto-retries, and produces UAT.md. It also nominates lessons from SUMMARY.md files before the archive step.\n\n## Required Skill Calls\n\n| Skill | Enforcement | Reason |\n|-------|-------------|--------|\n| `flow-comet-integration` | Required for verification protocol | Provides automation execution, UAT guidance, failure diagnosis, LESSONS nomination |\n\n## Output Schemas\n\nSchema: `flowkit.verify.v1`\n\n| Schema ID | Artifact Kind | Required | Path |\n|-----------|--------------|----------|------|\n| `uat-doc` | file | yes | `.specs/<change-id>/UAT.md` |\n| `test-doc` | file | yes | `.specs/<change-id>/TEST.md` (must already exist) |\n| `lessons-updated` | file | yes | `.specs/LESSONS.md` (nominated lessons added) |\n\nEvidence: `verification-result` (required)\n\n## Evidence Record\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-state.mjs record verify '{\"summary\":\"All automation passed, N UAT items verified (X pass, Y fail), Z lessons nominated\"}'\n```\n\n## Guardrails\n\n| Guardrail ID | Label | Validation Type |\n|--------------|-------|-----------------|\n| `verify-evidence` | UAT.md exists with results | artifact-exists |\n| `automation-passed` | All automated checks pass (real output) | content-check |\n| `retry-limit` | No more than 3 auto-retry rounds | process-check |\n| `lessons-nominated` | LESSONS.md updated with new entries | artifact-exists |\n\n## Exit Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs exit verify --apply\n```\n\nIf the script prints `SKILL: flow-comet-archive`, load that Skill next.\n\n## Recovery\n\n1. Re-run entry check to confirm workflow state.\n2. Read `.specs/<change-id>/UAT.md` — check which items have results.\n3. If UAT.md exists with all items passing, verification is done.\n4. If UAT.md has failures, check if fix tasks were generated in TASK.md.\n5. If fix tasks exist but not executed, return to execute node.\n6. Count previous auto-retry rounds from UAT.md to enforce R2.6 limit.\n7. Resume from the first incomplete verification step.\n",
|
|
274
|
-
"references": [],
|
|
275
|
-
"scripts": [],
|
|
276
|
-
"hash": "9e95fd4c63c157c3008001ba9dcd168abf7df286c47ea6d593f39eb48267a9ce"
|
|
277
|
-
}
|
|
278
|
-
]
|
|
279
|
-
},
|
|
280
|
-
{
|
|
281
|
-
"query": "flow-comet-integration",
|
|
282
|
-
"preferenceIndex": 12,
|
|
283
|
-
"status": "available",
|
|
284
|
-
"sources": [
|
|
285
|
-
{
|
|
286
|
-
"name": "flow-comet-integration",
|
|
287
|
-
"preferenceIndex": 12,
|
|
288
|
-
"platform": "claude-code",
|
|
289
|
-
"scope": "project",
|
|
290
|
-
"origin": "project",
|
|
291
|
-
"factory": {
|
|
292
|
-
"query": "flow-comet-integration"
|
|
293
|
-
},
|
|
294
|
-
"root": ".flow-comet/skills/flow-comet-integration",
|
|
295
|
-
"description": "flow-kit INTEGRATION 阶段协议:集成验证 + UAT + 失败诊断(≤3 轮)+ LESSONS 提名 + 归档。Comet verify/archive 阶段的 flow-kit 增强。",
|
|
296
|
-
"skillMd": "---\nname: flow-comet-integration\ndescription: \"flow-kit INTEGRATION 阶段协议:集成验证 + UAT + 失败诊断(≤3 轮)+ LESSONS 提名 + 归档。Comet verify/archive 阶段的 flow-kit 增强。\"\n---\n\n# flow-kit INTEGRATION Protocol\n\n本 Skill 为 Comet verify 和 archive 阶段提供 flow-kit 的集成验证和归档流程。\n\n## 加载\n\n读取 `flow-kit/prompts/7-integration.md` 并按其执行。\n\n### 集成验证(verify 阶段)\n\n1. **跑全套自动化**:全量单测 + 集成测试 + 类型检查 + 构建\n2. **引导人工 UAT**:逐条执行 TEST.md 中的 UAT 脚本\n3. **失败诊断**:root cause → fix-plan → 回到 execute 修复 → 重跑\n - **自动重试 ≤ 3 轮**(R2.6),超限暂停等人工决策\n\n### LESSONS 提名(archive 前必跑)\n\n扫描本次 change 的所有 `*-SUMMARY.md` 和遗留 `*-PROGRESS.md`,按提名条件筛选:\n- 调试/试错耗时 > 30 分钟 → 提名\n- 错因不限于本任务 → 提名\n- 6 个月内有合理概率被再次尝试 → 提名\n\n追加到 `.specs/LESSONS.md`,编号续 `L-NNN`。\n\n### 归档(archive 阶段)\n\n1. `.specs/<change-id>/` → `.specs/archive/<YYYY-MM-DD>-<change-id>/`\n2. `.specs/CHANGELOG.md` 追加一行\n3. **不归档** `.specs/LESSONS.md`(项目级常驻)\n4. DESIGN.md § 9 架构沉淀建议留待 A-evolve 批量同步\n\n## 产物\n\n- `.specs/<change-id>/UAT.md`\n- `.specs/archive/<YYYY-MM-DD>-<change-id>/`\n- 更新的 `.specs/CHANGELOG.md` 和 `.specs/LESSONS.md`\n\n## Comet 集成\n\n归档操作必须用户确认后才执行。失败诊断的自动重试由 Comet verify 阶段的自动修复循环管理。\n",
|
|
297
|
-
"references": [],
|
|
298
|
-
"scripts": [],
|
|
299
|
-
"hash": "f25aa9342e6ce1441f79d2027ca031432be169ca743d623e1be498f4330a5de5"
|
|
300
|
-
}
|
|
301
|
-
]
|
|
302
|
-
},
|
|
303
|
-
{
|
|
304
|
-
"query": "flow-comet-archive",
|
|
305
|
-
"preferenceIndex": 13,
|
|
306
|
-
"status": "available",
|
|
307
|
-
"sources": [
|
|
308
|
-
{
|
|
309
|
-
"name": "flow-comet-archive",
|
|
310
|
-
"preferenceIndex": 13,
|
|
311
|
-
"platform": "claude-code",
|
|
312
|
-
"scope": "project",
|
|
313
|
-
"origin": "project",
|
|
314
|
-
"factory": {
|
|
315
|
-
"query": "flow-comet-archive"
|
|
316
|
-
},
|
|
317
|
-
"root": ".flow-comet/skills/flow-comet-archive",
|
|
318
|
-
"description": "Archive node for flow-comet: scans SUMMARY.md files for lessons, adds qualifying lessons to .specs/LESSONS.md, moves change to .specs/archive/, and updates CHANGELOG.md. Do not use for ordinary standalone tasks.",
|
|
319
|
-
"skillMd": "---\nname: flow-comet-archive\ndescription: \"Archive node for flow-comet: scans SUMMARY.md files for lessons, adds qualifying lessons to .specs/LESSONS.md, moves change to .specs/archive/, and updates CHANGELOG.md. Do not use for ordinary standalone tasks.\"\n---\n\n# Archive\n\n## Node Goal\n\nThis node finalizes a completed change by extracting reusable lessons from the development process, archiving the change artifacts, and updating the project changelog. It ensures that hard-won knowledge (debugging > 30min, cross-task applicability, 6-month retry probability) is preserved in the project-level LESSONS.md, while change-specific artifacts are moved to the archive for future reference. This is the final node in the flow-comet workflow.\n\n## Guidance\n\n### Prerequisites\n\n- `.specs/<change-id>/UAT.md` must exist with all items passed (from verify node).\n- All `*-SUMMARY.md` files must exist for completed tasks.\n- `.specs/<change-id>/REVIEW.md` must exist with all Critical resolved.\n- The archive operation is irreversible (file move) — requires user confirmation before execution.\n\n### Steps\n\n1. **Scan SUMMARY.md files for lessons**: Read all `<task-id>-SUMMARY.md` files in `.specs/<change-id>/`. Focus on \"decisions and deviations\" sections. Also check any remaining `<task-id>-PROGRESS.md` \"excluded solutions\" sections.\n\n2. **Apply nomination criteria**: For each potential lesson:\n - Debugging/trial-and-error took > 30 minutes -> nominate.\n - Error is not task-specific, other tasks would hit it too -> nominate.\n - Reasonable probability of retry within 6 months -> nominate.\n - Otherwise do not nominate (avoid pollution of LESSONS.md).\n\n3. **Add qualifying lessons to LESSONS.md**: For each nominated lesson:\n - Assign next `L-NNN` number (continuing from existing).\n - Fill required fields: label, keywords, applicable tech stack, status (active).\n - Save to `.specs/LESSONS.md`.\n - **Do NOT archive LESSONS.md** — it is a project-level permanent file that accumulates across changes.\n\n4. **Check existing lessons for superseded/deprecated**: Scan existing active lessons in `.specs/LESSONS.md`. If this change's lessons or outcomes supersede or deprecate existing entries, update their status accordingly.\n\n5. **Move change to archive**: After user confirmation:\n - Move `.specs/<change-id>/` to `.specs/archive/<YYYY-MM-DD>-<change-id>/`.\n - Date format: YYYY-MM-DD of the archive date.\n - Verify the move completed successfully (source no longer exists, destination has all files).\n\n6. **Update CHANGELOG.md**: Append one line to `.specs/CHANGELOG.md`:\n - Format: `| YYYY-MM-DD | <change-id> | one-line summary | PR link | new L-NNN entries |`\n - If CHANGELOG.md does not exist, create it from template.\n\n7. **Update STATE.md**: Clear the active change field in the repository root `STATE.md`.\n\n8. **Notify user of architecture sedimentation**: Check DESIGN.md section 9 for sedimentation suggestions. If N > 0 suggestions exist, tell user:\n ```\n Archived to .specs/archive/<YYYY-MM-DD>-<change-id>/\n This change's DESIGN section 9 has N architecture sedimentation candidates, deferred for batch sync.\n Recommended: run A-evolve workflow after >= 5 changes or 60 days to batch-review and patch CONTEXT.md.\n ```\n\n9. **Record evidence**: Run workflow-state.mjs to record archive completion.\n\n10. **Exit check**: Run exit check.\n\nThe full archive protocol and templates are in:\n- `flow-kit/prompts/7-integration.md` (INTEGRATION phase, archive + LESSONS sections)\n\n### Completion reasoning\n\nThis node is truly done when:\n- `.specs/<change-id>/` has been moved to `.specs/archive/<YYYY-MM-DD>-<change-id>/`.\n- `.specs/CHANGELOG.md` has been updated with the change entry.\n- `.specs/LESSONS.md` has been updated with any qualifying new lessons.\n- STATE.md has been updated (active change cleared).\n- User has confirmed the archive operation.\n- LESSONS.md has NOT been moved or archived (it remains project-level).\n\n### Red flags\n\n- **Agent thought**: \"Archive is just moving files, no need to ask.\" **Actual risk**: Archiving without user confirmation is irreversible — if the user wanted to add something or the change is not actually complete, the archive operation cannot be undone. Always ask first.\n- **Agent thought**: \"LESSONS.md is part of the change, archive it too.\" **Actual risk**: Archiving LESSONS.md with the change removes project-level knowledge that should persist across changes. LESSONS.md is permanent and must stay in `.specs/`.\n- **Agent thought**: \"No lessons to nominate, skip the scan.\" **Actual risk**: Even if no lessons qualify, the scan must be performed and documented. Skipping means potentially valuable knowledge is lost.\n- **Agent thought**: \"Update CONTEXT.md with DESIGN section 9 suggestions during archive.\" **Actual risk**: Directly updating CONTEXT.md during archive violates the A-evolve workflow. Section 9 suggestions are deferred for batch sync, not applied immediately.\n\n## Entry Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs entry archive\n```\n\n## Skill Implementation\n\nThe archive node scans all SUMMARY.md files for lessons (applying > 30min debugging / cross-task applicability / 6-month retry criteria), adds qualifying lessons to `.specs/LESSONS.md`, moves the change directory to `.specs/archive/`, updates `.specs/CHANGELOG.md`, and clears STATE.md. It requires user confirmation before the irreversible file move.\n\n## Required Skill Calls\n\n| Skill | Enforcement | Reason |\n|-------|-------------|--------|\n| `flow-comet-integration` | Required for LESSONS nomination protocol | Provides nomination criteria and LESSONS.md format |\n\n## Output Schemas\n\nSchema: `flowkit.archive.v1`\n\n| Schema ID | Artifact Kind | Required | Path |\n|-----------|--------------|----------|------|\n| `archive-dir` | directory | yes | `.specs/archive/<YYYY-MM-DD>-<change-id>/` |\n| `changelog-entry` | file | yes | `.specs/CHANGELOG.md` (appended) |\n| `lessons-updated` | file | conditional | `.specs/LESSONS.md` (if new lessons nominated) |\n\nEvidence: `archive-summary` (required)\n\n## Evidence Record\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-state.mjs record archive '{\"summary\":\"Change archived to .specs/archive/<date>-<id>/, N lessons added, CHANGELOG updated\"}'\n```\n\n## Guardrails\n\n| Guardrail ID | Label | Validation Type |\n|--------------|-------|-----------------|\n| `archive-evidence` | Archive directory exists, source removed | state-transition |\n| `changelog-updated` | CHANGELOG.md has new entry | content-check |\n| `lessons-preserved` | LESSONS.md still in .specs/ (not archived) | file-exists |\n| `user-confirmed` | User confirmed archive before execution | process-check |\n\n## Exit Check\n\n```bash\nnode .claude/skills/flow-comet/scripts/workflow-guard.mjs exit archive --apply\n```\n\nIf the script prints `NEXT: done`, summarize the workflow evidence and stop. The change is complete.\n\n## Recovery\n\n1. Re-run entry check to confirm workflow state.\n2. Check if `.specs/<change-id>/` still exists (not yet archived) or if `.specs/archive/<YYYY-MM-DD>-<change-id>/` exists (already archived).\n3. If not yet archived: resume from the first incomplete step (lessons scan, archive move, CHANGELOG update).\n4. If already archived but CHANGELOG not updated: update CHANGELOG.md manually.\n5. If already archived but LESSONS not updated: scan SUMMARY.md files in the archive directory and update LESSONS.md.\n6. If partially archived (source removed but destination incomplete): investigate and complete the move.\n",
|
|
320
|
-
"references": [],
|
|
321
|
-
"scripts": [],
|
|
322
|
-
"hash": "b266a9492d7cdfa01d2894596db8a19506e0cc6c98f33537f2fbadc27783ea98"
|
|
323
|
-
}
|
|
324
|
-
]
|
|
325
|
-
}
|
|
326
|
-
],
|
|
327
|
-
"sourceSummaries": [
|
|
328
|
-
{
|
|
329
|
-
"name": "flow-comet-open",
|
|
330
|
-
"query": "flow-comet-open",
|
|
331
|
-
"description": "Open node for flow-comet: produces CHANGE.md + REQUIREMENT.md via structured questioning and AC derivation. First node in the flow — no upstream artifacts needed. Do not use for ordinary standalone tasks.",
|
|
332
|
-
"platform": "claude-code",
|
|
333
|
-
"scope": "project",
|
|
334
|
-
"origin": "project",
|
|
335
|
-
"references": []
|
|
336
|
-
},
|
|
337
|
-
{
|
|
338
|
-
"name": "flow-comet-change",
|
|
339
|
-
"query": "flow-comet-change",
|
|
340
|
-
"description": "flow-kit CHANGE 阶段协议:反问澄清、change-id 自动生成、架构级变更检测、视觉调性预选。Comet open 阶段的 flow-kit 增强。",
|
|
341
|
-
"platform": "claude-code",
|
|
342
|
-
"scope": "project",
|
|
343
|
-
"origin": "project",
|
|
344
|
-
"references": []
|
|
345
|
-
},
|
|
346
|
-
{
|
|
347
|
-
"name": "flow-comet-requirement",
|
|
348
|
-
"query": "flow-comet-requirement",
|
|
349
|
-
"description": "flow-kit REQUIREMENT 阶段协议:AC(Given/When/Then)+ v1·v2·out 范围切分 + 术语提取。Comet open 阶段的 flow-kit 增强。",
|
|
350
|
-
"platform": "claude-code",
|
|
351
|
-
"scope": "project",
|
|
352
|
-
"origin": "project",
|
|
353
|
-
"references": []
|
|
354
|
-
},
|
|
355
|
-
{
|
|
356
|
-
"name": "flow-comet-design",
|
|
357
|
-
"query": "flow-comet-design",
|
|
358
|
-
"description": "Design node for flow-comet: produces DESIGN.md (and UI-DESIGN.md for frontend) via tech stack selection, ADR, and architecture alignment. Do not use for ordinary standalone tasks.",
|
|
359
|
-
"platform": "claude-code",
|
|
360
|
-
"scope": "project",
|
|
361
|
-
"origin": "project",
|
|
362
|
-
"references": []
|
|
363
|
-
},
|
|
364
|
-
{
|
|
365
|
-
"name": "flow-comet-ui-design",
|
|
366
|
-
"query": "flow-comet-ui-design",
|
|
367
|
-
"description": "flow-kit 2a UI-DESIGN 阶段协议:美学方向 + design tokens + 反 AI-slop 自检。仅前端项目触发。",
|
|
368
|
-
"platform": "claude-code",
|
|
369
|
-
"scope": "project",
|
|
370
|
-
"origin": "project",
|
|
371
|
-
"references": []
|
|
372
|
-
},
|
|
373
|
-
{
|
|
374
|
-
"name": "flow-comet-task",
|
|
375
|
-
"query": "flow-comet-task",
|
|
376
|
-
"description": "flow-kit TASK 阶段协议:拆原子任务(XML 格式)、read_files/write_files 边界、波次划分、并行标记 [P]。Comet plan producer 的 flow-kit 实现。",
|
|
377
|
-
"platform": "claude-code",
|
|
378
|
-
"scope": "project",
|
|
379
|
-
"origin": "project",
|
|
380
|
-
"references": []
|
|
381
|
-
},
|
|
382
|
-
{
|
|
383
|
-
"name": "flow-comet-execute",
|
|
384
|
-
"query": "flow-comet-execute",
|
|
385
|
-
"description": "Execute node for flow-comet: iterates through pending tasks in TASK.md, applying TDD, LESSONS scan, diff boundary check, and atomic commits for each. Do not use for ordinary standalone tasks.",
|
|
386
|
-
"platform": "claude-code",
|
|
387
|
-
"scope": "project",
|
|
388
|
-
"origin": "project",
|
|
389
|
-
"references": []
|
|
390
|
-
},
|
|
391
|
-
{
|
|
392
|
-
"name": "flow-comet-dev",
|
|
393
|
-
"query": "flow-comet-dev",
|
|
394
|
-
"description": "flow-kit DEV 阶段协议:TDD + 6 维自查 + diff 边界 verify + LESSONS 扫描 + R4.5 Schema 迁移 + R4.6 破坏性变更。Comet execute/subagent-execute 的 flow-kit 增强。",
|
|
395
|
-
"platform": "claude-code",
|
|
396
|
-
"scope": "project",
|
|
397
|
-
"origin": "project",
|
|
398
|
-
"references": []
|
|
399
|
-
},
|
|
400
|
-
{
|
|
401
|
-
"name": "flow-comet-subagent-execute",
|
|
402
|
-
"query": "flow-comet-subagent-execute",
|
|
403
|
-
"description": "Subagent Execute node for flow-comet: delegates parallel (parallel=true) tasks to subagents with flow-comet-dev loaded, collecting handoff evidence. Do not use for ordinary standalone tasks.",
|
|
404
|
-
"platform": "claude-code",
|
|
405
|
-
"scope": "project",
|
|
406
|
-
"origin": "project",
|
|
407
|
-
"references": []
|
|
408
|
-
},
|
|
409
|
-
{
|
|
410
|
-
"name": "flow-comet-review",
|
|
411
|
-
"query": "flow-comet-review",
|
|
412
|
-
"description": "Review node for flow-comet: performs 4-round review (spec compliance, code quality 6-dimension decay, UI visual, optional debt assessment) and produces REVIEW.md. Do not use for ordinary standalone tasks.",
|
|
413
|
-
"platform": "claude-code",
|
|
414
|
-
"scope": "project",
|
|
415
|
-
"origin": "project",
|
|
416
|
-
"references": []
|
|
417
|
-
},
|
|
418
|
-
{
|
|
419
|
-
"name": "flow-comet-test",
|
|
420
|
-
"query": "flow-comet-test",
|
|
421
|
-
"description": "flow-kit TEST 阶段协议:5 轮测试金字塔(功能/性能/安全/兼容/可观测)+ 测试质量 6 维自检。Comet execute 阶段的 flow-kit 增强。",
|
|
422
|
-
"platform": "claude-code",
|
|
423
|
-
"scope": "project",
|
|
424
|
-
"origin": "project",
|
|
425
|
-
"references": []
|
|
426
|
-
},
|
|
427
|
-
{
|
|
428
|
-
"name": "flow-comet-verify",
|
|
429
|
-
"query": "flow-comet-verify",
|
|
430
|
-
"description": "Verify node for flow-comet: runs full automation (tests + type check + build), guides human UAT, performs failure diagnosis with max 3 auto-retries, and produces UAT.md. Do not use for ordinary standalone tasks.",
|
|
431
|
-
"platform": "claude-code",
|
|
432
|
-
"scope": "project",
|
|
433
|
-
"origin": "project",
|
|
434
|
-
"references": []
|
|
435
|
-
},
|
|
436
|
-
{
|
|
437
|
-
"name": "flow-comet-integration",
|
|
438
|
-
"query": "flow-comet-integration",
|
|
439
|
-
"description": "flow-kit INTEGRATION 阶段协议:集成验证 + UAT + 失败诊断(≤3 轮)+ LESSONS 提名 + 归档。Comet verify/archive 阶段的 flow-kit 增强。",
|
|
440
|
-
"platform": "claude-code",
|
|
441
|
-
"scope": "project",
|
|
442
|
-
"origin": "project",
|
|
443
|
-
"references": []
|
|
444
|
-
},
|
|
445
|
-
{
|
|
446
|
-
"name": "flow-comet-archive",
|
|
447
|
-
"query": "flow-comet-archive",
|
|
448
|
-
"description": "Archive node for flow-comet: scans SUMMARY.md files for lessons, adds qualifying lessons to .specs/LESSONS.md, moves change to .specs/archive/, and updates CHANGELOG.md. Do not use for ordinary standalone tasks.",
|
|
449
|
-
"platform": "claude-code",
|
|
450
|
-
"scope": "project",
|
|
451
|
-
"origin": "project",
|
|
452
|
-
"references": []
|
|
453
|
-
}
|
|
454
|
-
],
|
|
455
|
-
"workflow": {
|
|
456
|
-
"kind": "workflow-kernel",
|
|
457
|
-
"nodes": [
|
|
458
|
-
{
|
|
459
|
-
"id": "open",
|
|
460
|
-
"label": "Open",
|
|
461
|
-
"implementation": {
|
|
462
|
-
"skill": "flow-comet-open",
|
|
463
|
-
"operation": "require",
|
|
464
|
-
"scope": "main",
|
|
465
|
-
"enforcement": "guarded"
|
|
466
|
-
},
|
|
467
|
-
"requiredSkillCalls": [
|
|
468
|
-
{
|
|
469
|
-
"skill": "flow-comet-change",
|
|
470
|
-
"operation": "require",
|
|
471
|
-
"scope": "main",
|
|
472
|
-
"enforcement": "guarded",
|
|
473
|
-
"reason": "CHANGE 反问协议"
|
|
474
|
-
},
|
|
475
|
-
{
|
|
476
|
-
"skill": "flow-comet-requirement",
|
|
477
|
-
"operation": "require",
|
|
478
|
-
"scope": "main",
|
|
479
|
-
"enforcement": "guarded",
|
|
480
|
-
"reason": "REQUIREMENT 需求分析"
|
|
481
|
-
}
|
|
482
|
-
],
|
|
483
|
-
"outputSchemas": [
|
|
484
|
-
"flowkit.intake.v1"
|
|
485
|
-
]
|
|
486
|
-
},
|
|
487
|
-
{
|
|
488
|
-
"id": "design",
|
|
489
|
-
"label": "Design",
|
|
490
|
-
"implementation": {
|
|
491
|
-
"skill": "flow-comet-design",
|
|
492
|
-
"operation": "require",
|
|
493
|
-
"scope": "main",
|
|
494
|
-
"enforcement": "guarded"
|
|
495
|
-
},
|
|
496
|
-
"requiredSkillCalls": [
|
|
497
|
-
{
|
|
498
|
-
"skill": "flow-comet-design",
|
|
499
|
-
"operation": "require",
|
|
500
|
-
"scope": "main",
|
|
501
|
-
"enforcement": "guarded",
|
|
502
|
-
"reason": "技术栈选型 + ADR"
|
|
503
|
-
},
|
|
504
|
-
{
|
|
505
|
-
"skill": "flow-comet-ui-design",
|
|
506
|
-
"operation": "require",
|
|
507
|
-
"scope": "main",
|
|
508
|
-
"enforcement": "guarded",
|
|
509
|
-
"reason": "UI-DESIGN(仅前端)"
|
|
510
|
-
}
|
|
511
|
-
],
|
|
512
|
-
"outputSchemas": [
|
|
513
|
-
"flowkit.design.v1"
|
|
514
|
-
]
|
|
515
|
-
},
|
|
516
|
-
{
|
|
517
|
-
"id": "plan",
|
|
518
|
-
"label": "Plan",
|
|
519
|
-
"implementation": {
|
|
520
|
-
"skill": "flow-comet-task",
|
|
521
|
-
"operation": "require",
|
|
522
|
-
"scope": "main",
|
|
523
|
-
"enforcement": "guarded"
|
|
524
|
-
},
|
|
525
|
-
"requiredSkillCalls": [
|
|
526
|
-
{
|
|
527
|
-
"skill": "flow-comet-task",
|
|
528
|
-
"operation": "require",
|
|
529
|
-
"scope": "main",
|
|
530
|
-
"enforcement": "guarded",
|
|
531
|
-
"reason": "拆原子任务"
|
|
532
|
-
}
|
|
533
|
-
],
|
|
534
|
-
"outputSchemas": [
|
|
535
|
-
"flowkit.plan.v1"
|
|
536
|
-
]
|
|
537
|
-
},
|
|
538
|
-
{
|
|
539
|
-
"id": "execute",
|
|
540
|
-
"label": "Execute",
|
|
541
|
-
"implementation": {
|
|
542
|
-
"skill": "flow-comet-execute",
|
|
543
|
-
"operation": "require",
|
|
544
|
-
"scope": "main",
|
|
545
|
-
"enforcement": "guarded"
|
|
546
|
-
},
|
|
547
|
-
"requiredSkillCalls": [
|
|
548
|
-
{
|
|
549
|
-
"skill": "flow-comet-dev",
|
|
550
|
-
"operation": "require",
|
|
551
|
-
"scope": "main",
|
|
552
|
-
"enforcement": "guarded",
|
|
553
|
-
"reason": "TDD + 6 维自查 + R4.5 + R4.6"
|
|
554
|
-
}
|
|
555
|
-
],
|
|
556
|
-
"outputSchemas": [
|
|
557
|
-
"flowkit.execution.v1"
|
|
558
|
-
]
|
|
559
|
-
},
|
|
560
|
-
{
|
|
561
|
-
"id": "subagent-execute",
|
|
562
|
-
"label": "Subagent Execute",
|
|
563
|
-
"implementation": {
|
|
564
|
-
"skill": "flow-comet-subagent-execute",
|
|
565
|
-
"operation": "require",
|
|
566
|
-
"scope": "main",
|
|
567
|
-
"enforcement": "guarded"
|
|
568
|
-
},
|
|
569
|
-
"requiredSkillCalls": [
|
|
570
|
-
{
|
|
571
|
-
"skill": "flow-comet-dev",
|
|
572
|
-
"operation": "require",
|
|
573
|
-
"scope": "handoff",
|
|
574
|
-
"enforcement": "handoff-guarded",
|
|
575
|
-
"reason": "子代理加载 DEV 规则并回传 evidence"
|
|
576
|
-
}
|
|
577
|
-
],
|
|
578
|
-
"outputSchemas": [
|
|
579
|
-
"flowkit.handoff.v1"
|
|
580
|
-
]
|
|
581
|
-
},
|
|
582
|
-
{
|
|
583
|
-
"id": "review",
|
|
584
|
-
"label": "Review",
|
|
585
|
-
"implementation": {
|
|
586
|
-
"skill": "flow-comet-review",
|
|
587
|
-
"operation": "require",
|
|
588
|
-
"scope": "main",
|
|
589
|
-
"enforcement": "guarded"
|
|
590
|
-
},
|
|
591
|
-
"requiredSkillCalls": [
|
|
592
|
-
{
|
|
593
|
-
"skill": "flow-comet-review",
|
|
594
|
-
"operation": "require",
|
|
595
|
-
"scope": "main",
|
|
596
|
-
"enforcement": "guarded",
|
|
597
|
-
"reason": "3 轮审查"
|
|
598
|
-
},
|
|
599
|
-
{
|
|
600
|
-
"skill": "flow-comet-test",
|
|
601
|
-
"operation": "require",
|
|
602
|
-
"scope": "main",
|
|
603
|
-
"enforcement": "guarded",
|
|
604
|
-
"reason": "测试金字塔完整性"
|
|
605
|
-
}
|
|
606
|
-
],
|
|
607
|
-
"outputSchemas": [
|
|
608
|
-
"flowkit.review.v1"
|
|
609
|
-
]
|
|
610
|
-
},
|
|
611
|
-
{
|
|
612
|
-
"id": "verify",
|
|
613
|
-
"label": "Verify",
|
|
614
|
-
"implementation": {
|
|
615
|
-
"skill": "flow-comet-verify",
|
|
616
|
-
"operation": "require",
|
|
617
|
-
"scope": "main",
|
|
618
|
-
"enforcement": "guarded"
|
|
619
|
-
},
|
|
620
|
-
"requiredSkillCalls": [
|
|
621
|
-
{
|
|
622
|
-
"skill": "flow-comet-integration",
|
|
623
|
-
"operation": "require",
|
|
624
|
-
"scope": "main",
|
|
625
|
-
"enforcement": "guarded",
|
|
626
|
-
"reason": "集成验证 + UAT + LESSONS 提名"
|
|
627
|
-
}
|
|
628
|
-
],
|
|
629
|
-
"outputSchemas": [
|
|
630
|
-
"flowkit.verify.v1"
|
|
631
|
-
]
|
|
632
|
-
},
|
|
633
|
-
{
|
|
634
|
-
"id": "archive",
|
|
635
|
-
"label": "Archive",
|
|
636
|
-
"implementation": {
|
|
637
|
-
"skill": "flow-comet-archive",
|
|
638
|
-
"operation": "require",
|
|
639
|
-
"scope": "main",
|
|
640
|
-
"enforcement": "guarded"
|
|
641
|
-
},
|
|
642
|
-
"requiredSkillCalls": [
|
|
643
|
-
{
|
|
644
|
-
"skill": "flow-comet-integration",
|
|
645
|
-
"operation": "require",
|
|
646
|
-
"scope": "main",
|
|
647
|
-
"enforcement": "guarded",
|
|
648
|
-
"reason": "归档 + LESSONS"
|
|
649
|
-
}
|
|
650
|
-
],
|
|
651
|
-
"outputSchemas": [
|
|
652
|
-
"flowkit.archive.v1"
|
|
653
|
-
]
|
|
654
|
-
}
|
|
655
|
-
]
|
|
656
|
-
},
|
|
657
|
-
"preference": {
|
|
658
|
-
"requiredSkills": [],
|
|
659
|
-
"warnings": []
|
|
660
|
-
}
|
|
661
|
-
}
|