@delorenj/pjangler 1.1.5 → 1.2.2

package/templates/commonproject/.claude/commands/bmad/bmm/workflows/testarch-framework.md

@@ -1,13 +0,0 @@
----
-description: 'Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/framework/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/bmm/workflows/testarch-nfr.md

@@ -1,13 +0,0 @@
----
-description: 'Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/bmm/workflows/testarch-test-design.md

@@ -1,13 +0,0 @@
----
-description: 'Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-design/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/bmm/workflows/testarch-test-review.md

@@ -1,13 +0,0 @@
----
-description: 'Review test quality using comprehensive knowledge base and best practices validation'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-review/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/bmm/workflows/testarch-trace.md

@@ -1,13 +0,0 @@
----
-description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/trace/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/bmm/workflows/workflow-init.md

@@ -1,13 +0,0 @@
----
-description: 'Initialize a new BMM project by determining level, type, and creating workflow path'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/init/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/bmm/workflows/workflow-status.md

@@ -1,13 +0,0 @@
----
-description: 'Lightweight status checker - answers ""what should I do now?"" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/cis/agents/brainstorming-coach.md

@@ -1,14 +0,0 @@
----
-name: 'brainstorming-coach'
-description: 'brainstorming-coach agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/cis/agents/brainstorming-coach.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/templates/commonproject/.claude/commands/bmad/cis/agents/creative-problem-solver.md

@@ -1,14 +0,0 @@
----
-name: 'creative-problem-solver'
-description: 'creative-problem-solver agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/cis/agents/creative-problem-solver.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/templates/commonproject/.claude/commands/bmad/cis/agents/design-thinking-coach.md

@@ -1,14 +0,0 @@
----
-name: 'design-thinking-coach'
-description: 'design-thinking-coach agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/cis/agents/design-thinking-coach.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/templates/commonproject/.claude/commands/bmad/cis/agents/innovation-strategist.md

@@ -1,14 +0,0 @@
----
-name: 'innovation-strategist'
-description: 'innovation-strategist agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/cis/agents/innovation-strategist.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/templates/commonproject/.claude/commands/bmad/cis/agents/presentation-master.md

@@ -1,14 +0,0 @@
----
-name: 'presentation-master'
-description: 'presentation-master agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/cis/agents/presentation-master.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/templates/commonproject/.claude/commands/bmad/cis/agents/storyteller.md

@@ -1,14 +0,0 @@
----
-name: 'storyteller'
-description: 'storyteller agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/cis/agents/storyteller/storyteller.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/templates/commonproject/.claude/commands/bmad/cis/workflows/design-thinking.md

@@ -1,13 +0,0 @@
----
-description: 'Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/design-thinking/workflow.yaml
-3. Pass the yaml path _bmad/cis/workflows/design-thinking/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/cis/workflows/innovation-strategy.md

@@ -1,13 +0,0 @@
----
-description: 'Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/innovation-strategy/workflow.yaml
-3. Pass the yaml path _bmad/cis/workflows/innovation-strategy/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/cis/workflows/problem-solving.md

@@ -1,13 +0,0 @@
----
-description: 'Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/problem-solving/workflow.yaml
-3. Pass the yaml path _bmad/cis/workflows/problem-solving/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/cis/workflows/storytelling.md

@@ -1,13 +0,0 @@
----
-description: 'Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/storytelling/workflow.yaml
-3. Pass the yaml path _bmad/cis/workflows/storytelling/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/templates/commonproject/.claude/commands/bmad/core/agents/bmad-master.md

@@ -1,14 +0,0 @@
----
-name: 'bmad-master'
-description: 'bmad-master agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/core/agents/bmad-master.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/templates/commonproject/.claude/commands/bmad/core/tasks/index-docs.md

@@ -1,9 +0,0 @@
----
-description: 'Generates or updates an index.md of all documents in the specified directory'
----
-
-# Index Docs
-
-LOAD and execute the task at: _bmad/core/tasks/index-docs.xml
-
-Follow all instructions in the task file exactly as written.

package/templates/commonproject/.claude/commands/bmad/core/tasks/shard-doc.md

@@ -1,9 +0,0 @@
----
-description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections'
----
-
-# Shard Document
-
-LOAD and execute the task at: _bmad/core/tasks/shard-doc.xml
-
-Follow all instructions in the task file exactly as written.

package/templates/commonproject/.claude/commands/bmad/core/workflows/brainstorming.md

@@ -1,5 +0,0 @@
----
-description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/commonproject/.claude/commands/bmad/core/workflows/party-mode.md

@@ -1,5 +0,0 @@
----
-description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/commonproject/.claude/commands/bmad/custom/workflows/ticket-lifecycle.md

@@ -1,5 +0,0 @@
----
-description: 'Autonomous multi-agent ticket lifecycle: triage, AC refinement, implementation, and QA verification via Plane + Bloodbank (tri-modal: create, validate, edit)'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/custom/workflows/ticket-lifecycle/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/hermes-agent/docs/scrum-master-sentinel.md

@@ -1,17 +0,0 @@
-# Scrum Master role and the ticket sentinel
-
-The Scrum Master is a Hermes agent role whose core loop is a provider-agnostic
-ticket sentinel with an autonomous adversarial review (act, do not wait). The
-full documentation has moved to a dedicated handoff guide.
-
-This page is kept as a stable pointer so existing links keep working.
-
-## Where the docs live now
-
-- [Scrum Master handoff overview](scrum-master/README.md): start here.
-- [Architecture](scrum-master/architecture.md): the watch loop, the provider
-  abstraction, and the autonomous adversarial review.
-- [Providers](scrum-master/providers.md): the adapter contract and how to add or
-  verify a provider.
-- [Development guide](scrum-master/development.md): editing, validating,
-  provisioning, propagating, the Drumjangler cutover record, and the roadmap.

package/templates/hermes-agent/template/.scripts/75-scrum-master.sh

@@ -1,117 +0,0 @@
-#!/usr/bin/env bash
-# Install the Scrum Master continuous-ticket sentinel: systemd timer + runner,
-# and stage the engine docs + enforcement tools into the role dir.
-# Only meaningful for role: scrum-master (copier guards the _tasks call).
-# shellcheck source=_lib.sh
-source "$(dirname "$0")/_lib.sh"
-load_role_env
-
-if [[ "$ROLE" != "scrum-master" ]]; then
-  log "[75] role is '$ROLE', not scrum-master — skipping sentinel install"; exit 0
-fi
-if already_done 75-scrum-master && [[ "${FORCE_SENTINEL:-0}" != "1" ]]; then
-  log "[75] scrum master sentinel already installed — skipping"; exit 0
-fi
-
-RUNTIME="$ROLE_DIR/runtime"
-PROFILE_HOME="$(profile_or_runtime_home)"
-REPO_ROOT="$(project_repo_path)"
-RUNNER="$ROLE_DIR/.scripts/scrum-master/continuous-ticket-sentinel.sh"
-SYS_DIR="$HOME/.config/systemd/user"
-mkdir -p "$SYS_DIR" "$PROFILE_HOME/logs"
-
-[[ -f "$RUNNER" ]] || die "[75] runner missing: $RUNNER (template render incomplete)"
-chmod +x "$RUNNER" "$ROLE_DIR/.scripts/scrum-master/"*.sh 2>/dev/null || true
-chmod +x "$ROLE_DIR/.scripts/scrum-master/bin/"*.sh 2>/dev/null || true
-
-LOG="$PROFILE_HOME/logs/continuous-ticket-sentinel.log"
-ENV_FILE="$HOME/.hermes/${AGENT_ID}.env"
-
-if [[ "$(uname -s)" == "Darwin" ]]; then
-  # macOS: a launchd LaunchAgent that runs the sentinel every 60 seconds. It
-  # sources the per-agent env file (ticket-provider keys) and exports them.
-  LA_DIR="$HOME/Library/LaunchAgents"
-  mkdir -p "$LA_DIR"
-  LABEL="com.hermes.${AGENT_ID}.sentinel"
-  PLIST="$LA_DIR/$LABEL.plist"
-  cat > "$PLIST" <<PLIST
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-<plist version="1.0">
-<dict>
-  <key>Label</key><string>$LABEL</string>
-  <key>ProgramArguments</key>
-  <array>
-    <string>/bin/sh</string>
-    <string>-lc</string>
-    <string>set -a; [ -f "$ENV_FILE" ] &amp;&amp; . "$ENV_FILE"; set +a; exec "$RUNNER"</string>
-  </array>
-  <key>StartInterval</key><integer>60</integer>
-  <key>RunAtLoad</key><true/>
-  <key>WorkingDirectory</key><string>$REPO_ROOT</string>
-  <key>EnvironmentVariables</key>
-  <dict><key>HERMES_HOME</key><string>$PROFILE_HOME</string></dict>
-  <key>StandardOutPath</key><string>$LOG</string>
-  <key>StandardErrorPath</key><string>$LOG</string>
-</dict>
-</plist>
-PLIST
-  launchctl unload "$PLIST" >/dev/null 2>&1 || true
-  if launchctl load -w "$PLIST" >/dev/null 2>&1; then
-    log "    loaded launchd agent: $LABEL"
-  else
-    warn "    launchd load failed; plist written at $PLIST"
-  fi
-else
-  # Linux: systemd --user oneshot service plus a 1-minute timer.
-  ENV_FILES="$(cat <<'ENVFILES'
-EnvironmentFile=-%h/.config/hermes-agent/env
-EnvironmentFile=-%h/.hermes/env
-EnvironmentFile=-%h/.hermes/hermes-agent.env
-ENVFILES
-)"
-  ENV_FILES="$ENV_FILES
-EnvironmentFile=-%h/.hermes/${AGENT_ID}.env"
-  SVC_UNIT="hermes-${AGENT_ID}-continuous-ticket-sentinel.service"
-  TIMER_UNIT="hermes-${AGENT_ID}-continuous-ticket-sentinel.timer"
-  cat > "$SYS_DIR/$SVC_UNIT" <<UNIT
-[Unit]
-Description=Hermes Continuous Ticket Sentinel — $DISPLAY_NAME
-After=network-online.target
-Wants=network-online.target
-
-[Service]
-Type=oneshot
-WorkingDirectory=$REPO_ROOT
-Environment=HERMES_HOME=$PROFILE_HOME
-$ENV_FILES
-ExecStart=$RUNNER
-TimeoutStartSec=45min
-StandardOutput=append:$LOG
-StandardError=append:$LOG
-UNIT
-  cat > "$SYS_DIR/$TIMER_UNIT" <<UNIT
-[Unit]
-Description=Continuous ticket sentinel for $AGENT_ID
-
-[Timer]
-OnBootSec=1min
-OnUnitInactiveSec=1min
-Unit=$SVC_UNIT
-Persistent=true
-
-[Install]
-WantedBy=timers.target
-UNIT
-  if systemd_user_available; then
-    systemctl --user daemon-reload
-    systemctl --user enable --now "$TIMER_UNIT" >/dev/null 2>&1 \
-      && log "    enabled: $TIMER_UNIT" \
-      || warn "    failed to enable: $TIMER_UNIT"
-  else
-    warn "    systemd --user not available; units installed at $SYS_DIR but not enabled"
-  fi
-fi
-
-log "[75] scrum master sentinel installed (provider: $(yaml_get ticket_provider.name))"
-mark_done 75-scrum-master

package/templates/hermes-agent/template/.scripts/90-chain-scrum-master.sh

@@ -1,45 +0,0 @@
-#!/usr/bin/env bash
-# When a PM is provisioned with with_scrum_master=yes, chain a paired Scrum
-# Master provision for the same repo + ticket provider into a sibling role dir.
-# Idempotent: skips if agents/hermes/scrum-master already exists.
-# shellcheck source=_lib.sh
-source "$(dirname "$0")/_lib.sh"
-load_role_env
-
-already_done 90-chain-scrum-master && { log "[90] scrum master already chained — skipping"; exit 0; }
-
-# Sibling path: .../agents/hermes/scrum-master  (peer of this pm role dir).
-HERMES_DIR="$(dirname "$ROLE_DIR")"
-SM_DIR="$HERMES_DIR/scrum-master"
-
-if [[ -d "$SM_DIR" ]]; then
-  log "[90] $SM_DIR already exists — not re-provisioning"; mark_done 90-chain-scrum-master; exit 0
-fi
-
-# Resolve the template source from this provision's copier answers.
-ANSWERS="$ROLE_DIR/.copier-answers.yml"
-SRC="$(yaml_get _src_path 2>/dev/null || true)"
-[[ -z "$SRC" && -f "$ANSWERS" ]] && SRC="$(python3 -c 'import sys,re,pathlib;
-t=pathlib.Path(sys.argv[1]).read_text();m=re.search(r"(?m)^_src_path:\s*(.+)$",t);print((m.group(1).strip() if m else ""))' "$ANSWERS")"
-SRC="${SRC:-gh:delorenj/hermes-agent-template}"
-
-PROVIDER="$(yaml_get ticket_provider.name)"; PROVIDER="${PROVIDER:-plane}"
-
-if ! command -v copier >/dev/null 2>&1; then
-  warn "[90] copier not on PATH; provision the Scrum Master manually:"
-  warn "     copier copy --trust $SRC $SM_DIR --data role=scrum-master --data target_repo=$REPO --data ticket_provider=$PROVIDER"
-  mark_done 90-chain-scrum-master; exit 0
-fi
-
-log "[90] chaining Scrum Master provision -> $SM_DIR (provider: $PROVIDER)"
-# --trust is REQUIRED: the hermes-agent template uses copier `tasks`, which copier
-# refuses to run unless explicitly trusted. Without it the chained provision aborts
-# with "Template uses potentially unsafe feature: tasks" and the SM is never created.
-copier copy --defaults --overwrite --trust \
-  --data role=scrum-master \
-  --data target_repo="$REPO" \
-  --data ticket_provider="$PROVIDER" \
-  "$SRC" "$SM_DIR" \
-  || warn "[90] chained scrum-master provision failed; run it manually (see command above)"
-
-mark_done 90-chain-scrum-master