guild-agents 1.4.0 → 2.0.0

package/src/templates/skills/build-feature/SKILL.md

@@ -11,19 +11,11 @@ workflow:
       requires: [feature-description]
       produces: [evaluation-report, verdict]
       model-tier: reasoning
-      on-failure: abort
-    - id: specify
-      role: product-owner
-      intent: "Break the feature into concrete tasks with verifiable acceptance criteria. Estimate effort and suggest implementation order."
-      requires: [feature-description, evaluation-report]
-      produces: [task-list, acceptance-criteria]
-      model-tier: reasoning
-      condition: step.evaluate.verdict != rejected
     - id: design
       role: tech-lead
-      intent: "Define implementation approach: files to modify, patterns to follow, interfaces, and technical risks."
-      requires: [task-list, acceptance-criteria]
-      produces: [technical-plan]
+      intent: "Break the feature into concrete tasks with acceptance criteria. Define implementation approach: files to modify, patterns to follow, interfaces, and technical risks."
+      requires: [feature-description, evaluation-report]
+      produces: [task-list, acceptance-criteria, technical-plan]
       model-tier: reasoning
     - id: implement
       role: developer
@@ -34,13 +26,11 @@ workflow:
     - id: gate-pre-review
       role: system
       intent: "Run project tests and lint. Both must pass before review."
-      commands: [npm test, npm run lint]
       gate: true
       produces: [gate-pre-review-result]
-      on-failure: goto:implement
-    - id: checkpoint-phase4
+    - id: checkpoint
       role: system
-      intent: "Create checkpoint commit and write partial pipeline trace (phases 1-4) to spec file."
+      intent: "Create checkpoint commit and write partial pipeline trace to spec file."
       requires: [implementation, gate-pre-review-result]
       produces: [checkpoint-commit]
       gate: true
@@ -50,56 +40,29 @@ workflow:
       requires: [implementation, gate-pre-review-result]
       produces: [review-report]
       model-tier: reasoning
-      retry:
-        max: 2
-        on: has-blockers
     - id: fix-review-blockers
       role: developer
       intent: "Fix blocker findings from code review. Run tests after fixing."
       requires: [review-report]
       produces: [implementation]
       model-tier: execution
-      condition: step.review.has-blockers
-      on-failure: goto:review
     - id: qa-phase
-      role: system
-      intent: "Run QA validation with bugfix cycles."
-      delegates-to: qa-cycle
+      role: qa
+      intent: "Validate acceptance criteria, test edge cases, run bugfix cycles if needed."
       requires: [acceptance-criteria, implementation]
       produces: [qa-report]
-      retry:
-        max: 2
-        on: has-bugs
-    - id: post-qa-review
-      role: code-reviewer
-      intent: "Review changes introduced during QA bugfix cycles."
-      requires: [qa-report, implementation]
-      produces: [post-qa-review-report]
-      model-tier: reasoning
-      condition: step.qa-phase.had-significant-changes
-      retry:
-        max: 2
-        on: has-blockers
+      model-tier: execution
     - id: gate-final
       role: system
       intent: "Run project tests and lint as final verification. Both must pass."
-      commands: [npm test, npm run lint]
       gate: true
       produces: [final-gate-result]
-      on-failure: goto:qa-phase
     - id: completion
       role: system
-      intent: "Write complete pipeline trace to spec file. Update SESSION.md. Present summary to user."
+      intent: "Update SESSION.md. Present summary to user."
       requires: [final-gate-result, review-report, qa-report]
-      produces: [pipeline-trace, session-update]
+      produces: [session-update]
       gate: true
-    - id: extract-learnings
-      role: learnings-extractor
-      intent: "Extract compound learnings from this pipeline execution."
-      requires: [pipeline-trace]
-      produces: [updated-learnings]
-      model-tier: routine
-      blocking: false
 ---
 
 # Build Feature
@@ -131,19 +94,18 @@ git worktree remove .claude/worktrees/[branch-name]
 
 When running a single build-feature, a simple `git checkout -b` is sufficient.
 
-## 6-Phase Pipeline
+## 5-Phase Pipeline
 
 ### Progress Display
 
 At the start of each phase, display a progress indicator to the user before any agent output:
 
 ```text
-[1/6] Advisor (opus) — Evaluating feature...
-[2/6] Product Owner (opus) — Defining spec...
-[3/6] Tech Lead (opus) — Defining technical approach...
-[4/6] Developer (sonnet) — Implementing...
-[5/6] Code Reviewer (opus) — Reviewing changes...
-[6/6] QA (sonnet) — Validating acceptance criteria...
+[1/5] Advisor (opus) — Evaluating feature...
+[2/5] Tech Lead (opus) — Defining spec and technical approach...
+[3/5] Developer (sonnet) — Implementing...
+[4/5] Code Reviewer (opus) — Reviewing changes...
+[5/5] QA (sonnet) — Validating acceptance criteria...
 ```
 
 Model names are resolved from the step's `model-tier` using the `max` profile: reasoning=opus, execution=sonnet, routine=haiku. System/gate steps do not show a model name.
@@ -151,15 +113,15 @@ Model names are resolved from the step's `model-tier` using the `max` profile: r
 When a phase loops (review-fix or QA-review cycles), show the iteration:
 
 ```text
-[5/6 · round 2] Code Reviewer (opus) — Re-reviewing after fixes...
-[4/6 · round 2] Developer (sonnet) — Fixing review blockers...
+[4/5 · round 2] Code Reviewer (opus) — Re-reviewing after fixes...
+[3/5 · round 2] Developer (sonnet) — Fixing review blockers...
 ```
 
 This indicator MUST be displayed before spawning the agent for that phase.
 
 ### Phase 1 — Evaluation (Advisor)
 
-**Progress:** `[1/6] Advisor (opus) — Evaluating feature...`
+**Progress:** `[1/5] Advisor (opus) — Evaluating feature...`
 **Agent:** Reads `.claude/agents/advisor.md` via Task tool with `model: "opus"`
 **Input:** The feature description provided by the user
 **Process:**
@@ -172,39 +134,26 @@ This indicator MUST be displayed before spawning the agent for that phase.
 **Trace data:** Verdict (Approved/Rejected/Approved with conditions), risks identified, conditions if any
 **Exit condition:** If the Advisor rejects the feature, the pipeline stops here. Inform the user of the reason and suggest adjustments if any.
 
-### Phase 2 — Specification (Product Owner)
-
-**Progress:** `[2/6] Product Owner (opus) — Defining spec...`
-**Agent:** Reads `.claude/agents/product-owner.md` via Task tool with `model: "opus"`
-**Input:** The feature approved by the Advisor + their observations
-**Process:**
+### Phase 2 — Specification & Technical Approach (Tech Lead)
 
-1. The Product Owner breaks the feature into concrete tasks
-2. Defines verifiable acceptance criteria for each task
-3. Estimates effort and suggests implementation order
-
-**Output:** Task list with acceptance criteria, estimation, and order
-**Trace data:** Tasks defined count, acceptance criteria count, estimated effort
-
-### Phase 3 — Technical Approach (Tech Lead)
-
-**Progress:** `[3/6] Tech Lead (opus) — Defining technical approach...`
+**Progress:** `[2/5] Tech Lead (opus) — Defining spec and technical approach...`
 **Agent:** Reads `.claude/agents/tech-lead.md` via Task tool with `model: "opus"`
-**Input:** Product Owner tasks + acceptance criteria
+**Input:** The feature approved by the Advisor + their observations
 **Process:**
 
-1. The Tech Lead defines the implementation approach
-2. Identifies files to modify, patterns to follow, interfaces
+1. The Tech Lead breaks the feature into concrete tasks with verifiable acceptance criteria
+2. Defines the implementation approach: files to modify, patterns to follow, interfaces
 3. Anticipates technical risks and proposes mitigations
+4. Estimates effort and suggests implementation order
 
-**Output:** Technical plan with files, patterns, interfaces, and risks
-**Trace data:** Key patterns identified, files to modify, technical risks
+**Output:** Task list with acceptance criteria + technical plan with files, patterns, interfaces, and risks
+**Trace data:** Tasks defined count, acceptance criteria count, key patterns identified, files to modify, technical risks
 
-### Phase 4 — Implementation (Developer)
+### Phase 3 — Implementation (Developer)
 
-**Progress:** `[4/6] Developer (sonnet) — Implementing...`
+**Progress:** `[3/5] Developer (sonnet) — Implementing...`
 **Agent:** Reads `.claude/agents/developer.md` via Task tool with `model: "sonnet"`
-**Input:** Tech Lead technical plan + PO acceptance criteria
+**Input:** Tech Lead technical plan + acceptance criteria
 **Process:**
 
 1. The Developer implements following the technical plan
@@ -217,7 +166,7 @@ This indicator MUST be displayed before spawning the agent for that phase.
 
 ### Pre-Review Gate (mandatory)
 
-Before advancing to Phase 5, run automated verification:
+Before advancing to Phase 4, run automated verification:
 
 1. Run the project test commands (e.g., `npm test`) — if it fails, the Developer must fix before advancing
 2. Run the project lint commands (e.g., `npm run lint`) — if it fails, the Developer must fix before advancing
@@ -227,9 +176,9 @@ This gate CANNOT be skipped, even if the user requested phase skipping. The spec
 
 **Trace data:** Tests pass/fail, lint pass/fail
 
-### Phase 5 — Review (Code Reviewer)
+### Phase 4 — Review (Code Reviewer)
 
-**Progress:** `[5/6] Code Reviewer (opus) — Reviewing changes...`
+**Progress:** `[4/5] Code Reviewer (opus) — Reviewing changes...`
 **Agent:** Reads `.claude/agents/code-reviewer.md` via Task tool with `model: "opus"`
 **Input:** The implemented changes (git diff)
 **Process:**
@@ -239,13 +188,13 @@ This gate CANNOT be skipped, even if the user requested phase skipping. The spec
 
 **Output:** Review report with classified findings
 **Trace data:** Blockers count, warnings count, suggestions count, review-fix loops
-**Loop condition:** If there are Blocker findings, return to **Phase 4** for the Developer to fix them. Maximum 2 review-fix iterations.
+**Loop condition:** If there are Blocker findings, return to **Phase 3** for the Developer to fix them. Maximum 2 review-fix iterations.
 
-### Phase 6 — QA (delegates to /qa-cycle)
+### Phase 5 — QA (delegates to /qa-cycle)
 
-**Progress:** `[6/6] QA (sonnet) — Validating acceptance criteria...`
+**Progress:** `[5/5] QA (sonnet) — Validating acceptance criteria...`
 
-Runs the `/qa-cycle` skill passing the PO acceptance criteria as context. The qa-cycle handles:
+Runs the `/qa-cycle` skill passing the acceptance criteria as context. The qa-cycle handles:
 
 1. Running project tests and lint
 2. Validating acceptance criteria
@@ -253,7 +202,7 @@ Runs the `/qa-cycle` skill passing the PO acceptance criteria as context. The qa
 4. Bugfix cycle if issues arise (maximum 3 cycles)
 
 **Trace data:** Acceptance criteria verified count, bugs found, QA cycles
-**Additional loop condition:** If the qa-cycle bugfix introduces significant changes, return to **Phase 5** (Review) for verification. Maximum 2 review-QA cycles.
+**Additional loop condition:** If the qa-cycle bugfix introduces significant changes, return to **Phase 4** (Review) for verification. Maximum 2 review-QA cycles.
 
 ## Checkpoint Commits
 
@@ -267,11 +216,10 @@ git commit -m "wip: [feature-name] phase N complete — [phase-name]"
 Pattern for each phase:
 
 - After Phase 1: `wip: [feature] phase 1 — advisor approved`
-- After Phase 2: `wip: [feature] phase 2 — PO spec ready`
-- After Phase 3: `wip: [feature] phase 3 — tech approach defined`
-- After Phase 4: `wip: [feature] phase 4 — implementation done` -- also write partial trace (phases 1-4) to spec and update status to `implementing`
-- After Phase 5: `wip: [feature] phase 5 — review passed`
-- After Phase 6: `wip: [feature] phase 6 — QA passed`
+- After Phase 2: `wip: [feature] phase 2 — spec and tech approach defined`
+- After Phase 3: `wip: [feature] phase 3 — implementation done` -- also write partial trace (phases 1-3) to spec and update status to `implementing`
+- After Phase 4: `wip: [feature] phase 4 — review passed`
+- After Phase 5: `wip: [feature] phase 5 — QA passed`
 
 Also update SESSION.md at each phase transition:
 
@@ -325,7 +273,7 @@ Append this section to the spec file:
 
 pipeline-start: [YYYY-MM-DD]
 pipeline-end: [YYYY-MM-DD]
-phases-completed: [N]/6
+phases-completed: [N]/5
 review-fix-loops: [N]
 qa-cycles: [N]
 final-gate: pass | fail
@@ -335,19 +283,16 @@ final-gate: pass | fail
 - **Verdict**: [Approved/Rejected/Approved with conditions]
 - **Risks identified**: [list or "None"]
 
-### Phase 2 — Specification
+### Phase 2 — Specification & Technical Approach
 
 - **Tasks defined**: [N]
 - **Acceptance criteria**: [N]
-- **Estimated effort**: [summary]
-
-### Phase 3 — Technical Approach
-
 - **Key patterns**: [list]
 - **Files to modify**: [list]
 - **Technical risks**: [list or "None"]
+- **Estimated effort**: [summary]
 
-### Phase 4 — Implementation
+### Phase 3 — Implementation
 
 - **Files created/modified**: [list]
 - **Tests added**: [N]
@@ -358,14 +303,14 @@ final-gate: pass | fail
 - **Tests**: pass | fail
 - **Lint**: pass | fail
 
-### Phase 5 — Review
+### Phase 4 — Review
 
 - **Blockers**: [N]
 - **Warnings**: [N]
 - **Suggestions**: [N]
 - **Review-fix loops**: [N]
 
-### Phase 6 — QA
+### Phase 5 — QA
 
 - **Acceptance criteria verified**: [N]/[total]
 - **Bugs found**: [N]
@@ -380,15 +325,15 @@ final-gate: pass | fail
 
 ### When to write the trace
 
-- **Phase 4 checkpoint:** Write a partial trace covering phases 1-4 to the spec file. Set status to `implementing`. Include the spec file in the checkpoint commit.
+- **Phase 3 checkpoint:** Write a partial trace covering phases 1-3 to the spec file. Set status to `implementing`. Include the spec file in the checkpoint commit.
 - **Pipeline completion:** Write the complete trace (all phases) to the spec file. Set status to `implemented`. Include the spec file in the final checkpoint commit.
 
 ## Final Gate (mandatory before Completion)
 
 Before declaring the pipeline as complete, run final verification:
 
-1. Run project tests — if it fails, return to Phase 6 (QA/Bugfix)
-2. Run project lint — if it fails, return to Phase 4 (Developer)
+1. Run project tests — if it fails, return to Phase 5 (QA/Bugfix)
+2. Run project lint — if it fails, return to Phase 3 (Developer)
 3. Both must pass with exit code 0
 
 This gate is the last safety net. It CANNOT be skipped under any circumstances.
@@ -423,7 +368,7 @@ When spawning agents via the Task tool, use these `subagent_type` values:
 
 | Guild Agent Role | subagent_type to use |
 | --- | --- |
-| advisor, product-owner, tech-lead | `"general-purpose"` |
+| advisor, tech-lead | `"general-purpose"` |
 | developer, bugfix | `"general-purpose"` |
 | code-reviewer, qa | `"general-purpose"` |
 
@@ -445,22 +390,19 @@ The `model` parameter is resolved from the step's `model-tier`: reasoning→`"op
 ```text
 User: /build-feature add dark mode toggle to settings page
 
-[1/6] Advisor (opus) — Evaluating feature...
+[1/5] Advisor (opus) — Evaluating feature...
   Approved. Low risk, aligns with UX roadmap.
 
-[2/6] Product Owner (opus) — Defining spec...
-  3 tasks defined with acceptance criteria.
-
-[3/6] Tech Lead (opus) — Defining technical approach...
-  Use CSS variables + context provider pattern.
+[2/5] Tech Lead (opus) — Defining spec and technical approach...
+  3 tasks defined. Use CSS variables + context provider pattern.
 
-[4/6] Developer (sonnet) — Implementing...
+[3/5] Developer (sonnet) — Implementing...
   Implemented ThemeContext, toggle component, CSS vars.
 
-[5/6] Code Reviewer (opus) — Reviewing changes...
+[4/5] Code Reviewer (opus) — Reviewing changes...
   Passed. 1 suggestion (memoize context value).
 
-[6/6] QA (sonnet) — Validating acceptance criteria...
+[5/5] QA (sonnet) — Validating acceptance criteria...
   All 3 acceptance criteria verified. 0 bugs.
 
 Feature complete. PR ready for merge.
@@ -468,7 +410,7 @@ Feature complete. PR ready for merge.
 
 ## Notes
 
-- If the user wants to skip phases (e.g., "already evaluated, implement directly"), allow skipping to Phase 4 but warn that validation is lost. Verification gates (pre-Review and final) are NEVER skipped
+- If the user wants to skip phases (e.g., "already evaluated, implement directly"), allow skipping to Phase 3 but warn that validation is lost. Verification gates (pre-Review and final) are NEVER skipped
 - The pipeline is sequential: each phase depends on the output of the previous one
 - Review/QA loops have limits to prevent infinite cycles
 - In v1.x, parallel pipeline execution (multiple build-features via worktrees) is best-effort and depends on the host environment supporting concurrent agents

package/src/templates/skills/build-feature/evals/evals.json

@@ -3,10 +3,9 @@
   "evals": [
     {
       "id": "bf-has-core-phases",
-      "description": "Plan contains evaluate, specify, design, implement phases",
+      "description": "Plan contains evaluate, design, implement phases",
       "expectations": [
         { "text": "Has evaluate step", "assertion": "step-exists:evaluate" },
-        { "text": "Has specify step", "assertion": "step-exists:specify" },
         { "text": "Has design step", "assertion": "step-exists:design" },
         { "text": "Has implement step", "assertion": "step-exists:implement" }
       ]
@@ -44,9 +43,9 @@
     },
     {
       "id": "bf-minimum-steps",
-      "description": "Plan has at least 10 steps",
+      "description": "Plan has at least 8 steps",
       "expectations": [
-        { "text": "At least 10 steps", "assertion": "step-count:10" }
+        { "text": "At least 8 steps", "assertion": "step-count:8" }
       ]
     }
   ]

package/src/templates/skills/council/SKILL.md

@@ -11,33 +11,24 @@ workflow:
       requires: [user-question]
       produces: [council-type, participant-roles]
       gate: true
-    - id: workspace-context
-      role: system
-      intent: "Detect workspace membership. If in a workspace, collect context from sibling repos (CLAUDE.md, PROJECT.md, SESSION.md) and build workspace context block."
-      requires: [council-type]
-      produces: [workspace-context]
-      condition: in-workspace
     - id: agent-1
       role: dynamic
-      intent: "Analyze the question from specialized perspective. State position with concrete arguments."
-      requires: [user-question, council-type, workspace-context]
+      intent: "Analyze the question from specialized perspective. State position with concrete arguments. Spawn via Agent tool IN PARALLEL with agent-2 and agent-3."
+      requires: [user-question, council-type]
       produces: [perspective-1]
       model-tier: reasoning
-      parallel: [agent-2, agent-3]
     - id: agent-2
       role: dynamic
       intent: "Analyze the question from specialized perspective. State position with concrete arguments."
-      requires: [user-question, council-type, workspace-context]
+      requires: [user-question, council-type]
       produces: [perspective-2]
       model-tier: reasoning
-      parallel: [agent-1, agent-3]
     - id: agent-3
       role: dynamic
       intent: "Analyze the question from specialized perspective. State position with concrete arguments."
-      requires: [user-question, council-type, workspace-context]
+      requires: [user-question, council-type]
       produces: [perspective-3]
       model-tier: reasoning
-      parallel: [agent-1, agent-2]
     - id: synthesize
       role: system
       intent: "Synthesize debate: points of agreement, disagreement, risks. Present options to user."
@@ -49,7 +40,6 @@ workflow:
       intent: "After user decides, write spec document to docs/specs/."
       requires: [synthesis, user-decision]
       produces: [spec-document]
-      condition: user-wants-spec
       gate: true
 ---
 
@@ -87,13 +77,13 @@ Invokes all 3 agents IN PARALLEL using Task tool:
 
 ### 2. Council Feature-Scope
 
-**Participants:** Advisor + Product Owner + Tech Lead
+**Participants:** Advisor + Developer + Tech Lead
 **When it applies:** Defining feature scope, prioritizing functionality, evaluating product proposals
 
 Invokes all 3 agents IN PARALLEL using Task tool:
 
 - Task 1: Reads `.claude/agents/advisor.md` — domain and strategic vision perspective
-- Task 2: Reads `.claude/agents/product-owner.md` — user value and scope perspective
+- Task 2: Reads `.claude/agents/developer.md` — implementability and pragmatism perspective
 - Task 3: Reads `.claude/agents/tech-lead.md` — technical feasibility and effort perspective
 
 ### 3. Council Tech-Debt

package/src/templates/skills/council/evals/evals.json

@@ -2,15 +2,12 @@
   "skill": "council",
   "evals": [
     {
-      "id": "council-three-parallel-agents",
-      "description": "Council has 3 agent steps in parallel",
+      "id": "council-three-agents",
+      "description": "Council has 3 agent steps",
       "expectations": [
         { "text": "Agent-1 exists", "assertion": "step-exists:agent-1" },
         { "text": "Agent-2 exists", "assertion": "step-exists:agent-2" },
-        { "text": "Agent-3 exists", "assertion": "step-exists:agent-3" },
-        { "text": "Agent-1 is parallel", "assertion": "step-parallel:agent-1" },
-        { "text": "Agent-2 is parallel", "assertion": "step-parallel:agent-2" },
-        { "text": "Agent-3 is parallel", "assertion": "step-parallel:agent-3" }
+        { "text": "Agent-3 exists", "assertion": "step-exists:agent-3" }
       ]
     },
     {
@@ -29,13 +26,6 @@
         { "text": "Synthesize step exists", "assertion": "step-exists:synthesize" },
         { "text": "Synthesize has gate", "assertion": "gate-exists:synthesize" }
       ]
-    },
-    {
-      "id": "council-workspace-context",
-      "description": "Workspace context step exists with condition",
-      "expectations": [
-        { "text": "Workspace-context step exists", "assertion": "step-exists:workspace-context" }
-      ]
     }
   ]
 }

package/src/templates/skills/create-pr/SKILL.md

@@ -8,12 +8,10 @@ workflow:
     - id: verify-branch
       role: system
       intent: "Verify not on main/develop, check for uncommitted changes, get commits ahead of main."
-      commands: [git branch --show-current, git status, git log main..HEAD --oneline]
       produces: [branch-name, branch-state, commit-list]
     - id: gather-context
       role: system
       intent: "Collect diff stats, run tests and lint for PR description context."
-      commands: [git diff main..HEAD --stat, npm test, npm run lint]
       requires: [branch-state]
       produces: [diff-summary, test-result, lint-result]
     - id: generate-description
@@ -25,7 +23,6 @@ workflow:
     - id: create-pr
       role: system
       intent: "Push branch to origin and create PR via gh CLI."
-      commands: [git push -u origin, gh pr create]
       requires: [pr-description, pr-title, branch-name]
       produces: [pr-url]
     - id: post-creation
@@ -102,7 +99,7 @@ Build a structured PR description:
 1. Display the PR URL
 2. Suggest next steps:
    - "Request review from a teammate"
-   - "Run `/review` for an AI code review"
+   - "Run `/code-review` for an AI code review"
    - "Merge when ready with `gh pr merge [number]`"
 
 ## Example Session
@@ -121,7 +118,7 @@ https://github.com/org/repo/pull/42
 
 Next steps:
 - Request review from a teammate
-- Run /review for AI code review
+- Run /code-review for AI code review
 - Merge when ready
 ```
 

package/src/templates/skills/guild-specialize/SKILL.md

@@ -8,12 +8,10 @@ workflow:
     - id: read-base
       role: system
       intent: "Read CLAUDE.md, PROJECT.md, and SESSION.md for current Guild configuration."
-      commands: [cat CLAUDE.md, cat PROJECT.md, cat SESSION.md]
       produces: [claude-md, project-md, session-md]
     - id: explore-project
       role: system
       intent: "Scan project structure, dependency files, configs, CI, and documentation to detect stack and architecture."
-      commands: [ls -R src/, cat package.json]
       produces: [detected-stack, detected-architecture, detected-conventions]
       gate: true
     - id: enrich-claude-md
@@ -37,7 +35,6 @@ workflow:
     - id: commit-enrichment
       role: system
       intent: "Commit enriched CLAUDE.md and agent files as an atomic commit."
-      commands: [git add CLAUDE.md .claude/agents/*.md, git commit]
       requires: [enriched-claude-md, specialized-agents]
       produces: [enrichment-commit]
 ---
@@ -126,13 +123,10 @@ Invoke the Tech Lead agent using Task tool with `model: "sonnet"` (execution tie
 
 - **advisor.md**: real project domain, target users
 - **tech-lead.md**: specific stack, detected patterns, architecture decisions
-- **product-owner.md**: existing functionality, visible backlog
 - **developer.md**: code conventions, main framework, file structure
 - **code-reviewer.md**: lint rules, project patterns, anti-patterns to watch
 - **qa.md**: testing framework, commands to run tests, current coverage
 - **bugfix.md**: debugging stack, logs, available tools
-- **db-migration.md**: ORM, migration tool, current schema (if applicable)
-- **platform-expert.md**: Claude Code version, known permission bugs, hook configuration
 
 When specializing agents, append a zone at the bottom of each agent file:
 
@@ -168,7 +162,7 @@ Architecture:
 Updated agents:
 - [list of agents with their applied specialization]
 
-Run /status to see the full state.
+Run /session-start to see the full state.
 ```
 
 ### Step 6 — Commit enrichment immediately
@@ -204,9 +198,8 @@ Tech Lead (sonnet) — Specializing agents...
 Agents updated:
 - developer.md: Specialized for Next.js + TypeScript
 - qa.md: Configured for Vitest + Playwright
-- db-migration.md: Configured for Prisma
 
-Run /status to see the full state.
+Run /session-start to see the full state.
 ```
 
 ## Important Notes

package/src/templates/skills/qa-cycle/SKILL.md

@@ -8,7 +8,6 @@ workflow:
     - id: gate-pre-qa
       role: system
       intent: "Run project tests and lint before QA validation."
-      commands: [npm test, npm run lint]
       gate: true
       produces: [test-result, lint-result]
     - id: qa-validate
@@ -17,21 +16,15 @@ workflow:
       requires: [acceptance-criteria, test-result, lint-result]
       produces: [qa-report]
       model-tier: execution
-      retry:
-        max: 3
-        on: has-bugs
     - id: bugfix
       role: bugfix
       intent: "Diagnose and fix bugs reported by QA. Run tests after fixing."
       requires: [qa-report]
       produces: [bugfix-result]
       model-tier: execution
-      condition: step.qa-validate.has-bugs
-      on-failure: goto:qa-validate
     - id: gate-post-qa
       role: system
       intent: "Run project tests and lint after QA cycle completes."
-      commands: [npm test, npm run lint]
       gate: true
       produces: [final-test-result, final-lint-result]
 ---

package/src/templates/skills/re-specialize/SKILL.md

@@ -8,12 +8,10 @@ workflow:
     - id: read-current
       role: system
       intent: "Read current CLAUDE.md and agent files to identify existing zones."
-      commands: [cat CLAUDE.md]
       produces: [current-claude-md, current-agents]
     - id: explore-project
       role: system
       intent: "Scan project for current stack, dependencies, architecture, conventions."
-      commands: [ls -R src/, cat package.json]
       produces: [detected-stack, detected-architecture, detected-conventions]
       gate: true
     - id: check-zones
@@ -43,7 +41,6 @@ workflow:
     - id: commit
       role: system
       intent: "Commit re-specialized files."
-      commands: [git add CLAUDE.md .claude/agents/*.md, git commit -m "chore: re-specialize via guild-re-specialize"]
       requires: [updated-claude-md, updated-agents, confirmation]
       produces: [re-specialize-commit]
 ---