claude-code-workflow 7.2.26 → 7.2.28

package/.claude/skills/ship/phases/05-pr-creation.md

@@ -0,0 +1,163 @@
+# Phase 5: PR Creation
+
+Create a pull request via GitHub CLI with a structured body, linked issues, and release metadata.
+
+## Objective
+
+- Create a PR using `gh pr create` with structured body
+- Auto-link related issues from commit messages
+- Include release summary (version, changes, test plan)
+- Output the PR URL
+
+## Gate Condition
+
+PR created successfully and URL returned.
+
+## Execution Steps
+
+### Step 1: Extract Issue References from Commits
+
+```bash
+last_tag=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
+
+if [ -n "$last_tag" ]; then
+  commits=$(git log "$last_tag"..HEAD --pretty=format:"%s" --no-merges)
+else
+  commits=$(git log --pretty=format:"%s" --no-merges -50)
+fi
+
+# Extract issue references: fixes #N, closes #N, resolves #N, refs #N
+issues=$(echo "$commits" | grep -oiE '(fix(es)?|close[sd]?|resolve[sd]?|refs?)\s*#[0-9]+' | grep -oE '#[0-9]+' | sort -u || true)
+
+echo "Referenced issues: $issues"
+```
+
+### Step 2: Determine Target Branch
+
+```bash
+# Default target: main (fallback: master)
+target_branch="main"
+if ! git rev-parse --verify "origin/$target_branch" &>/dev/null; then
+  target_branch="master"
+fi
+
+current_branch=$(git branch --show-current)
+echo "PR: $current_branch -> $target_branch"
+```
+
+### Step 3: Build PR Title
+
+Format: `release: vX.Y.Z`
+
+```bash
+pr_title="release: v${new_version}"
+```
+
+If the version context is not available, fall back to a descriptive title from the branch name.
+
+### Step 4: Build PR Body
+
+Construct the PR body using a HEREDOC for correct formatting:
+
+```bash
+# Gather change summary
+change_summary=$(git log "$merge_base"..HEAD --pretty=format:"- %s (%h)" --no-merges)
+
+# Build linked issues section
+if [ -n "$issues" ]; then
+  issues_section="## Linked Issues
+$(echo "$issues" | while read -r issue; do echo "- $issue"; done)"
+else
+  issues_section=""
+fi
+```
+
+### Step 5: Create PR via gh CLI
+
+```bash
+gh pr create --title "$pr_title" --base "$target_branch" --body "$(cat <<'EOF'
+## Summary
+Release vX.Y.Z
+
+### Changes
+- list of changes from changelog
+
+## Linked Issues
+- #N (fixes)
+- #M (closes)
+
+## Version
+- Previous: X.Y.Z-1
+- New: X.Y.Z
+- Bump type: patch|minor|major
+
+## Test Plan
+- [ ] Pre-flight checks passed (git clean, branch, tests, build)
+- [ ] AI code review completed with no critical issues
+- [ ] Version bump verified in version file
+- [ ] Changelog updated with all changes since last release
+- [ ] Release commit pushed successfully
+
+Generated with [Claude Code](https://claude.com/claude-code)
+EOF
+)"
+```
+
+**PR body sections**:
+
+| Section | Content |
+|---------|---------|
+| **Summary** | Version being released, one-line description |
+| **Changes** | Grouped changelog entries (from Phase 4) |
+| **Linked Issues** | Auto-extracted `fixes #N`, `closes #N` references |
+| **Version** | Previous version, new version, bump type |
+| **Test Plan** | Checklist confirming all phases passed |
+
+### Step 6: Capture and Report PR URL
+
+```bash
+# gh pr create outputs the PR URL on success
+pr_url=$(gh pr create ... 2>&1 | tail -1)
+echo "PR created: $pr_url"
+```
+
+## Output
+
+- **Format**: PR creation record
+- **Structure**:
+
+```json
+{
+  "phase": "pr-creation",
+  "pr_url": "https://github.com/owner/repo/pull/N",
+  "pr_title": "release: vX.Y.Z",
+  "target_branch": "main",
+  "source_branch": "feature-branch",
+  "linked_issues": ["#1", "#2"],
+  "overall": "pass|fail"
+}
+```
+
+## Completion
+
+After PR creation, output the final Completion Status:
+
+```
+## STATUS: DONE
+
+**Summary**: Released vX.Y.Z — PR created at {pr_url}
+
+### Details
+- Phases completed: 5/5
+- Version: {previous} -> {new} ({bump_type})
+- PR: {pr_url}
+- Key outputs: CHANGELOG.md updated, release commit pushed, PR created
+
+### Outputs
+- CHANGELOG.md (updated)
+- {version_file} (version bumped)
+- Release commit: {sha}
+- PR: {pr_url}
+```
+
+If there were review warnings, use `DONE_WITH_CONCERNS` and list the warnings in the Details section.

package/.claude/skills/skill-generator/templates/sequential-phase.md

@@ -80,6 +80,11 @@ Generate Phase files for Sequential execution mode, defining fixed-order executi
 
 {{quality_checklist}}
 
+## Completion Status
+
+Return one of: DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT with structured reason.
+See [Completion Status Protocol](./../_shared/SKILL-DESIGN-SPEC.md#13) for output format.
+
 ## Next Phase
 
 {{next_phase_link}}
@@ -456,6 +461,11 @@ Write(\`${workDir}/${phaseConfig.output}\`, JSON.stringify(result, null, 2));
 - [ ] Core logic executed successfully
 - [ ] Output format correct
 
+## Completion Status
+
+Return one of: DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT with structured reason.
+See [Completion Status Protocol](./../_shared/SKILL-DESIGN-SPEC.md#13) for output format.
+
 ${nextPhase ?
   `## Next Phase\n\n→ [Phase ${index + 2}: ${nextPhase.name}](${nextPhase.id}.md)` :
   '## Completion\n\nThis is the final phase.'}

package/.claude/skills/skill-generator/templates/skill-md.md

@@ -80,6 +80,10 @@ Bash(\`mkdir -p "\${workDir}"\`);
 {{output_structure}}
 \`\`\`
 
+## Completion Protocol
+
+Follow [Completion Status Protocol](./../_shared/SKILL-DESIGN-SPEC.md#13) and [Escalation Protocol](./../_shared/SKILL-DESIGN-SPEC.md#14).
+
 ## Reference Documents by Phase
 
 > **Important**: Reference documents should be organized by execution phase, clearly marking when and in what scenarios they are used. Avoid listing documents in a flat manner.

package/.claude/skills/team-arch-opt/SKILL.md

@@ -78,7 +78,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 })
 ```
 
-**Inner Loop roles** (refactorer): Set `inner_loop: true`.
+**Inner Loop roles** (refactorer): Set `inner_loop` dynamically — `true` for single mode, `false` for fan-out/independent (parallel branches).
 **Single-task roles** (analyzer, designer, validator, reviewer): Set `inner_loop: false`.
 
 ## User Commands

package/.claude/skills/team-arch-opt/roles/coordinator/commands/monitor.md

@@ -82,7 +82,9 @@ Find ready tasks, spawn workers, STOP.
 2. No ready + work in progress -> report waiting, STOP
 3. No ready + nothing in progress -> handleComplete
 4. Has ready -> for each:
-   a. Check if inner loop role with active worker -> skip (worker picks up)
+   a. Check inner_loop: parse task description `InnerLoop:` field (NOT role.md default)
+      - InnerLoop: true AND same-role worker already active -> skip (worker picks up)
+      - InnerLoop: false OR no active same-role worker -> spawn new worker
    b. TaskUpdate -> in_progress
    c. team_msg log -> task_unblocked
    d. Spawn team-worker (see SKILL.md Spawn Template):

package/.claude/skills/team-arch-opt/roles/refactorer/role.md

@@ -1,12 +1,14 @@
 ---
 role: refactorer
 prefix: REFACTOR
-inner_loop: true
+inner_loop: dynamic
 message_types: [state_update]
 ---
 
 # Code Refactorer
 
+> **inner_loop: dynamic** — Dispatch sets per-task: `true` for single mode (one REFACTOR task with iterative fix cycles), `false` for fan-out/independent modes (REFACTOR-B01..N run as separate parallel workers). When false, each branch gets its own worker.
+
 Implement architecture refactoring changes following the design plan. For FIX tasks, apply targeted corrections based on review/validation feedback.
 
 ## Modes

package/.claude/skills/team-arch-opt/specs/team-config.json

@@ -64,10 +64,10 @@
       "type": "code_generation",
       "description": "Implements architecture refactoring changes following the design plan",
       "role_spec": "roles/refactorer/role.md",
-      "inner_loop": true,
+      "inner_loop": "dynamic",
       "frontmatter": {
         "prefix": "REFACTOR",
-        "inner_loop": true,
+        "inner_loop": "dynamic",
         "additional_prefixes": ["FIX"],
         "discuss_rounds": [],
         "cli_tools": ["explore"],

package/.claude/skills/team-coordinate/SKILL.md

@@ -130,9 +130,10 @@ Execute built-in Phase 1 (task discovery) -> role-spec Phase 2-4 -> built-in Pha
 })
 ```
 
-**Inner Loop roles** (role has 2+ serial same-prefix tasks): Set `inner_loop: true`. The team-worker agent handles the loop internally.
-
-**Single-task roles**: Set `inner_loop: false`.
+**Inner Loop**: Determined per-task from task description `InnerLoop:` field, not per-role:
+- Serial chain (2+ tasks, each blockedBy previous): `inner_loop: true` — single worker loops
+- Parallel tasks (no mutual blockedBy): `inner_loop: false` — separate workers per task
+- Single-task roles: `inner_loop: false`
 
 ---
 

package/.claude/skills/team-coordinate/roles/coordinator/commands/analyze-task.md

@@ -130,7 +130,7 @@ For each role, determine frontmatter and generation hints:
 | Field | Derivation |
 |-------|------------|
 | `prefix` | From capability prefix (e.g., RESEARCH, DRAFT, IMPL) |
-| `inner_loop` | `true` if role has 2+ serial same-prefix tasks |
+| `inner_loop` | `true` if role has 2+ same-prefix tasks AND they form a serial chain (each blockedBy the previous). `false` if tasks are parallel (no mutual blockedBy) or role has only 1 task |
 | `CLI tools` | Suggested, not mandatory — coordinator may adjust based on task needs |
 | `pattern_hint` | Reference pattern name from role-spec-template (research/document/code/analysis/validation) — guides coordinator's Phase 2-4 composition, NOT a rigid template selector |
 | `output_type` | `artifact` (new files in session/artifacts/) / `codebase` (modify existing project files) / `mixed` (both) — determines verification strategy in Behavioral Traits |

package/.claude/skills/team-coordinate/roles/coordinator/commands/dispatch.md

@@ -95,9 +95,10 @@ RoleSpec: <session-folder>/role-specs/<role-name>.md
 
 | Condition | InnerLoop |
 |-----------|-----------|
-| Role has 2+ serial same-prefix tasks | true |
+| Role has 2+ same-prefix tasks forming a serial chain (each blockedBy the previous) | true |
 | Role has 1 task | false |
-| Tasks are parallel (no dependency between them) | false |
+| Role has 2+ same-prefix tasks but they are parallel (no mutual blockedBy) | false |
+| Mixed: some serial, some parallel within same role | Set per-task: true for serial chain members, false for parallel members |
 
 ### Dependency Validation
 

package/.claude/skills/team-coordinate/roles/coordinator/commands/monitor.md

@@ -144,9 +144,10 @@ Ready tasks found?
   +- NONE + work in progress -> report waiting -> STOP
   +- NONE + nothing in progress -> PIPELINE_COMPLETE -> handleComplete
   +- HAS ready tasks -> for each:
-      +- Is task owner an Inner Loop role AND that role already has an active_worker?
+      +- Parse task description `InnerLoop:` field (NOT session.roles[].inner_loop)
+      +- InnerLoop: true AND same-role worker already in active_workers?
       |   +- YES -> SKIP spawn (existing worker will pick it up via inner loop)
-      |   +- NO -> normal spawn below
+      |   +- NO -> normal spawn below (InnerLoop: false OR no active same-role worker)
       +- TaskUpdate -> in_progress
       +- team_msg log -> task_unblocked (session_id=<session-id>)
       +- Spawn team-worker (see spawn tool call below)

package/.claude/skills/team-coordinate/roles/coordinator/role.md

@@ -207,15 +207,9 @@ Regardless of complexity score or role count, coordinator MUST:
    - `project_root` = result of `Bash({ command: "pwd" })`
    - `skill_root` = `<project_root>/.claude/skills/team-coordinate`
 
-2. **Check `needs_research` flag** from task-analysis.json:
-   - If `true`: **Spawn researcher worker first** to gather codebase context
-     - Wait for researcher callback
-     - Merge research findings into task context
-     - Update task-analysis.json with enriched context
+2. **Generate session ID**: `TC-<slug>-<date>` (slug from first 3 meaningful words of task)
 
-3. **Generate session ID**: `TC-<slug>-<date>` (slug from first 3 meaningful words of task)
-
-4. **Create session folder structure**:
+3. **Create session folder structure**:
    ```
    .workflow/.team/<session-id>/
    +-- role-specs/
@@ -226,11 +220,11 @@ Regardless of complexity score or role count, coordinator MUST:
    +-- .msg/
    ```
 
-5. **Call TeamCreate** with team name derived from session ID
+4. **Call TeamCreate** with team name derived from session ID
 
-6. **Read `specs/role-spec-template.md`** for Behavioral Traits + Reference Patterns
+5. **Read `specs/role-spec-template.md`** for Behavioral Traits + Reference Patterns
 
-7. **For each role in task-analysis.json#roles**:
+6. **For each role in task-analysis.json#roles**:
    - Fill YAML frontmatter: role, prefix, inner_loop, additional_members, message_types
    - **Compose Phase 2-4 content** (NOT copy from template):
      - Phase 2: Derive input sources and context loading steps from **task description + upstream dependencies**
@@ -239,14 +233,14 @@ Regardless of complexity score or role count, coordinator MUST:
      - Reference Patterns may guide phase structure, but task description determines specific content
    - Write generated role-spec to `<session>/role-specs/<role-name>.md`
 
-8. **Register roles** in team-session.json#roles (with `role_spec` path instead of `role_file`)
+7. **Register roles** in team-session.json#roles (with `role_spec` path instead of `role_file`)
 
-9. **Initialize shared infrastructure**:
+8. **Initialize shared infrastructure**:
    - `wisdom/learnings.md`, `wisdom/decisions.md`, `wisdom/issues.md` (empty with headers)
    - `explorations/cache-index.json` (`{ "entries": [] }`)
    - `discussions/` (empty directory)
 
-10. **Initialize pipeline metadata** via team_msg:
+9. **Initialize pipeline metadata** via team_msg:
 ```typescript
 // 使用 team_msg 将 pipeline 元数据写入 .msg/meta.json
 // 注意: 此处为动态角色，执行时需将 <placeholders> 替换为 task-analysis.json 中生成的实际角色列表
@@ -265,7 +259,14 @@ mcp__ccw-tools__team_msg({
 })
 ```
 
-11. **Write team-session.json** with: session_id, task_description, status="active", roles, pipeline (empty), active_workers=[], completion_action="interactive", created_at
+10. **Write team-session.json** with: session_id, task_description, status="active", roles, pipeline (empty), active_workers=[], completion_action="interactive", created_at
+
+11. **Check `needs_research` flag** from task-analysis.json:
+    - If `true`: Spawn researcher worker (role-spec now exists from step 6) to gather codebase context
+      - Wait for researcher callback
+      - Merge research findings into task context
+      - Update task-analysis.json with enriched context
+    - If `false`: Skip, proceed to Phase 3
 
 **Success**: Session created, role-spec files generated, shared infrastructure initialized.
 

package/.claude/skills/team-coordinate/specs/pipelines.md

@@ -38,18 +38,20 @@ Phase 3-N: monitor.md
 
 ## Dependency Graph Structure
 
-task-analysis.json encodes the pipeline:
+task-analysis.json encodes the pipeline as adjacency list (task ID -> blockedBy array):
 
 ```json
 {
   "dependency_graph": {
-    "RESEARCH-001": { "role": "researcher", "blockedBy": [], "priority": "P0" },
-    "IMPL-001":     { "role": "developer",  "blockedBy": ["RESEARCH-001"], "priority": "P1" },
-    "TEST-001":     { "role": "tester",     "blockedBy": ["IMPL-001"], "priority": "P2" }
+    "RESEARCH-001": [],
+    "IMPL-001": ["RESEARCH-001"],
+    "TEST-001": ["IMPL-001"]
   }
 }
 ```
 
+Role mapping comes from `task-analysis.json#capabilities[].tasks[]`, not from the dependency graph itself.
+
 ## Role-Worker Map
 
 Dynamic — loaded from session role-specs at runtime:
@@ -64,6 +66,7 @@ Role-spec files contain YAML frontmatter:
 role: <role-name>
 prefix: <PREFIX>
 inner_loop: <true|false>
+output_tag: "[<role-name>]"
 message_types:
   success: <type>
   error: error

package/.claude/skills/team-coordinate/specs/role-spec-template.md

@@ -11,6 +11,7 @@ Template used by coordinator to generate lightweight worker role-spec files at r
 role: <role_name>
 prefix: <PREFIX>
 inner_loop: <true|false>
+output_tag: "[<role_name>]"
 CLI tools: [<CLI tool-names>]
 message_types:
   success: <prefix>_complete

package/.claude/skills/team-interactive-craft/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: team-interactive-craft
+description: Unified team skill for interactive component crafting. Vanilla JS + CSS interactive components with zero dependencies. Research -> interaction design -> build -> a11y test. Uses team-worker agent architecture. Triggers on "team interactive craft", "interactive component".
+allowed-tools: Agent, AskUserQuestion, Read, Write, Edit, Bash, Glob, Grep, TaskList, TaskGet, TaskUpdate, TaskCreate, TeamCreate, TeamDelete, SendMessage, mcp__ccw-tools__read_file, mcp__ccw-tools__write_file, mcp__ccw-tools__edit_file, mcp__ccw-tools__team_msg
+---
+
+# Team Interactive Craft
+
+Systematic interactive component pipeline: research -> interaction design -> build -> a11y test. Built on **team-worker agent architecture** -- all worker roles share a single agent definition with role-specific Phase 2-4 loaded from `roles/<role>/role.md`.
+
+## Architecture
+
+```
+Skill(skill="team-interactive-craft", args="task description")
+                    |
+         SKILL.md (this file) = Router
+                    |
+     +--------------+--------------+
+     |                             |
+  no --role flag              --role <name>
+     |                             |
+  Coordinator                  Worker
+  roles/coordinator/role.md    roles/<name>/role.md
+     |
+     +-- analyze -> dispatch -> spawn workers -> STOP
+                                    |
+                    +-------+-------+-------+-------+
+                    v       v       v       v
+           [team-worker agents, each loads roles/<role>/role.md]
+        researcher  interaction-designer  builder  a11y-tester
+```
+
+## Role Registry
+
+| Role | Path | Prefix | Inner Loop |
+|------|------|--------|------------|
+| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | -- | -- |
+| researcher | [roles/researcher/role.md](roles/researcher/role.md) | RESEARCH-* | false |
+| interaction-designer | [roles/interaction-designer/role.md](roles/interaction-designer/role.md) | INTERACT-* | false |
+| builder | [roles/builder/role.md](roles/builder/role.md) | BUILD-* | true |
+| a11y-tester | [roles/a11y-tester/role.md](roles/a11y-tester/role.md) | A11Y-* | false |
+
+## Role Router
+
+Parse `$ARGUMENTS`:
+- Has `--role <name>` -> Read `roles/<name>/role.md`, execute Phase 2-4
+- No `--role` -> `@roles/coordinator/role.md`, execute entry router
+
+## Shared Constants
+
+- **Session prefix**: `IC`
+- **Session path**: `.workflow/.team/IC-<slug>-<date>/`
+- **CLI tools**: `ccw cli --mode analysis` (read-only), `ccw cli --mode write` (modifications)
+- **Message bus**: `mcp__ccw-tools__team_msg(session_id=<session-id>, ...)`
+- **Max GC rounds**: 2
+
+## Worker Spawn Template
+
+Coordinator spawns workers using this template:
+
+```
+Agent({
+  subagent_type: "team-worker",
+  description: "Spawn <role> worker for <task-id>",
+  team_name: "interactive-craft",
+  name: "<role>",
+  run_in_background: true,
+  prompt: `## Role Assignment
+role: <role>
+role_spec: <skill_root>/roles/<role>/role.md
+session: <session-folder>
+session_id: <session-id>
+team_name: interactive-craft
+requirement: <task-description>
+inner_loop: <true|false>
+
+Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
+Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`
+})
+```
+
+## User Commands
+
+| Command | Action |
+|---------|--------|
+| `check` / `status` | View execution status graph |
+| `resume` / `continue` | Advance to next step |
+
+## Specs Reference
+
+- [specs/pipelines.md](specs/pipelines.md) -- Pipeline definitions and task registry
+- [specs/interaction-patterns.md](specs/interaction-patterns.md) -- Interaction pattern catalog
+- [specs/vanilla-constraints.md](specs/vanilla-constraints.md) -- Zero-dependency rules
+
+## Session Directory
+
+```
+.workflow/.team/IC-<slug>-<date>/
++-- .msg/
+|   +-- messages.jsonl         # Team message bus
+|   +-- meta.json              # Pipeline config + GC state
++-- research/                  # Researcher output
+|   +-- interaction-inventory.json
+|   +-- browser-api-audit.json
+|   +-- pattern-reference.json
++-- interaction/               # Interaction designer output
+|   +-- blueprints/
+|       +-- {component-name}.md
++-- build/                     # Builder output
+|   +-- components/
+|       +-- {name}.js
+|       +-- {name}.css
++-- a11y/                      # A11y tester output
+|   +-- a11y-audit-{NNN}.md
++-- wisdom/                    # Cross-task knowledge
+```
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Unknown command | Error with available command list |
+| Role not found | Error with role registry |
+| Session corruption | Attempt recovery, fallback to manual |
+| Fast-advance conflict | Coordinator reconciles on next callback |
+| Completion action fails | Default to Keep Active |
+| GC loop stuck > 2 rounds | Escalate to user: accept / retry / terminate |