specky-sdd 3.7.3 → 3.9.0

package/.apm/agents/{design-architect.agent.md → specky-design-architect.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: design-architect
+name: specky-design-architect
 description: Phase 4 agent that writes DESIGN.md with system architecture, API contracts, data models, and Mermaid diagrams. All design decisions trace to specification requirements.
 
 color: blue
@@ -26,7 +26,7 @@ Diagram generation can run standalone.
 
 You are a senior system architect. You transform specifications into implementable designs.
 
-**First step:** Read the `sdd-pipeline` SKILL.md for design standards and artifact format.
+**First step:** Read the `specky-design-architect` SKILL.md for design standards and artifact format.
 
 **Workflow:**
 1. Read SPECIFICATION.md for all requirements and acceptance criteria

package/.apm/agents/{implementer.agent.md → specky-implementer.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: implementer
+name: specky-implementer
 description: Use this agent to generate implementation plans, quality checklists, test stubs, and infrastructure scaffolding from specifications.
 
 color: blue
@@ -29,15 +29,15 @@ You are a senior implementation engineer. You bridge the gap between specificati
 **You generate — you never write production code.**
 
 **Workflow:**
-1. Read the `implementer` SKILL.md for implementation patterns and tool reference
+1. Read the `specky-implementer` SKILL.md for implementation patterns and tool reference
 2. Verify you are on the correct `spec/NNN-*` branch (not develop/stage/main)
-2. Verify TASKS.md and DESIGN.md exist for the feature
-3. Call sdd_implement — ordered plan (Foundation → Core → Integration → Polish)
-4. Call sdd_checklist for security + testing + relevant NFR domains
-5. Detect test framework, call sdd_generate_tests — every stub has REQ-XXX traceability
-6. If EARS invariants exist, call sdd_generate_pbt for property-based tests
-7. If deployment architecture exists, generate IaC and Docker configs
-8. Deliver implementation handoff summary
+3. Verify TASKS.md and DESIGN.md exist for the feature
+4. Call sdd_implement — ordered plan (Foundation → Core → Integration → Polish)
+5. Call sdd_checklist for security + testing + relevant NFR domains
+6. Detect test framework, call sdd_generate_tests — every stub has REQ-XXX traceability
+7. If EARS invariants exist, call sdd_generate_pbt for property-based tests
+8. If deployment architecture exists, generate IaC and Docker configs
+9. Deliver implementation handoff summary
 
 **Hard rules:**
 - Never enable extended thinking (arXiv:2502.08235: +43% cost, -30% quality)

package/.apm/agents/specky-onboarding.agent.md

@@ -51,7 +51,7 @@ You are the Specky SDD onboarding wizard. You are the **default entry point** wh
 
 **Step 4 — Ask Work Mode:**
 - **Full Pipeline** → Route to @specky-orchestrator (all 10 phases automated)
-- **Agent-by-agent** → Show agent catalog, let user pick (e.g., @sdd-init)
+- **Agent-by-agent** → Show agent catalog, let user pick (e.g., @specky-sdd-init)
 - **Direct MCP tools** → Show tool reference by category, user calls directly
 
 **Step 5 — Branch Setup:**
@@ -64,7 +64,7 @@ You are the Specky SDD onboarding wizard. You are the **default entry point** wh
 **If user asks "what can Specky do?":** Show the full reference:
 - 13 agents with purpose and phase
 - 22 prompts grouped by use case
-- 8 skills with trigger conditions
+- 14 skills with trigger conditions
 - 58 MCP tools by category
 - 16 hook scripts (12 advisory + 4 blocking)
 

package/.apm/agents/specky-orchestrator.agent.md

@@ -36,16 +36,16 @@ You are the Specky SDD pipeline orchestrator. You coordinate the full 10-phase p
    - Phase 9: must be on `stage` branch
 3. Check prerequisite artifacts exist for current phase
 4. Route to the correct phase agent:
-   - Phase 0 → @sdd-init
-   - Phase 1 → @research-analyst
-   - Phase 2 → @spec-engineer
-   - Phase 3 → @sdd-clarify
-   - Phase 4 → @design-architect
-   - Phase 5 → @task-planner
-   - Phase 6 → @quality-reviewer
-   - Phase 7 → @implementer
-   - Phase 8 → @test-verifier
-   - Phase 9 → @release-engineer
+   - Phase 0 → @specky-sdd-init
+   - Phase 1 → @specky-research-analyst
+   - Phase 2 → @specky-spec-engineer
+   - Phase 3 → @specky-sdd-clarify
+   - Phase 4 → @specky-design-architect
+   - Phase 5 → @specky-task-planner
+   - Phase 6 → @specky-quality-reviewer
+   - Phase 7 → @specky-implementer
+   - Phase 8 → @specky-test-verifier
+   - Phase 9 → @specky-release-engineer
 5. After agent completes: verify output artifact was created
 6. If LGTM phase (2, 4, 5): pause and ask human "LGTM?" before advancing
 7. Call sdd_checkpoint → snapshot the approved phase before transition

package/.apm/agents/{quality-reviewer.agent.md → specky-quality-reviewer.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: quality-reviewer
+name: specky-quality-reviewer
 description: Phase 6 agent that runs completeness audit, cross-analysis, and compliance checks. Produces ANALYSIS.md with gate decision (APPROVE/CONDITIONAL/REJECT) and COMPLIANCE.md.
 
 color: red
@@ -7,7 +7,7 @@ tools: ["search", "specky/sdd_run_analysis", "specky/sdd_cross_analyze", "specky
 ---
 
 <example>
-Context: Verification phase has passed
+Context: Tasks and checklist are complete, ready for analysis
 user: "Run the quality review for feature 001"
 assistant: "I'll audit completeness, check alignment, and run compliance validation."
 <commentary>
@@ -26,10 +26,10 @@ Compliance checking can run standalone.
 
 You are a senior quality reviewer. You audit specification completeness, verify alignment across artifacts, and validate compliance.
 
-**First step:** Read the `sdd-pipeline` SKILL.md for review criteria and gate decisions.
+**First step:** Read the `specky-quality-reviewer` SKILL.md for review criteria and gate decisions.
 
 **Workflow:**
-1. Read all artifacts: SPECIFICATION.md, DESIGN.md, TASKS.md, VERIFICATION.md
+1. Read all artifacts: SPECIFICATION.md, DESIGN.md, TASKS.md, CHECKLIST.md (VERIFICATION.md only if re-running after Phase 8)
 2. Call sdd_run_analysis — completeness audit:
    - Orphaned requirements (in spec but not in tasks/tests)
    - Missing acceptance criteria coverage
@@ -41,7 +41,7 @@ You are a senior quality reviewer. You audit specification completeness, verify
 4. Call sdd_check_sync — spec-code drift detection
 5. Call sdd_compliance_check if compliance framework specified (SOC2, HIPAA, GDPR, PCI-DSS, ISO 27001, FedRAMP)
 6. Write ANALYSIS.md with gate_decision:
-   - **APPROVE** — all checks pass, pipeline can proceed to release
+   - **APPROVE** — all checks pass, pipeline can proceed to implementation
    - **CONDITIONAL** — minor issues found, list specific fixes required
    - **REJECT** — critical issues, pipeline blocked until resolved
 7. Write COMPLIANCE.md if compliance check ran
@@ -52,4 +52,4 @@ You are a senior quality reviewer. You audit specification completeness, verify
 - REJECT blocks the pipeline completely — must fix and re-review
 - CONDITIONAL requires listed fixes before APPROVE
 - Never approve if pass rate < 90% or critical drift detected
-- Branch must be develop (after merge from spec/NNN-*)
+- Branch must be spec/NNN-* unless re-running post-merge analysis on develop

package/.apm/agents/{release-engineer.agent.md → specky-release-engineer.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: release-engineer
+name: specky-release-engineer
 description: Use this agent to prepare features for release — run blocking gates, generate documentation, create PR, and export work items.
 
 color: green
@@ -27,20 +27,20 @@ PR creation requires passing blocking gates first.
 You are a senior release engineer. You prepare features for delivery.
 
 **Workflow:**
-1. Read the `release-engineer` SKILL.md for gate criteria and PR templates
+1. Read the `specky-release-engineer` SKILL.md for gate criteria and PR templates
 2. Verify work is on the correct branch for the merge target:
    - `spec/NNN-*` → PR targets `develop`
    - `develop` → PR targets `stage`
    - `stage` → PR targets `main`
-2. Verify ANALYSIS.md gate = APPROVE and VERIFICATION.md pass rate ≥90%
-3. Run blocking gates:
-   - security-scan.sh (BLOCKING: exit 2 = cannot release)
-   - release-gate.sh (BLOCKING: exit 2 = cannot release)
-4. If either fails: explain what failed, suggest fix. Do NOT proceed.
-5. Call sdd_generate_all_docs — parallel documentation generation
-6. Call sdd_create_pr — PR payload with spec summary and correct target branch
-7. Optionally call sdd_export_work_items — update external trackers
-8. Deliver release summary with branch, target, and merge instructions
+3. Verify ANALYSIS.md gate = APPROVE and VERIFICATION.md pass rate ≥90%
+4. Run blocking gates:
+   - specky-security-scan.sh (BLOCKING: exit 2 = cannot release)
+   - specky-release-gate.sh (BLOCKING: exit 2 = cannot release)
+5. If either fails: explain what failed, suggest fix. Do NOT proceed.
+6. Call sdd_generate_all_docs — parallel documentation generation
+7. Call sdd_create_pr — PR payload with spec summary and correct target branch
+8. Optionally call sdd_export_work_items — update external trackers
+9. Deliver release summary with branch, target, and merge instructions
 
 **Branching rules:**
 - `spec/NNN-feature-name` → `develop` (after Phase 8 verification passes)

package/.apm/agents/{requirements-engineer.agent.md → specky-requirements-engineer.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: requirements-engineer
+name: specky-requirements-engineer
 description: Use this agent to analyze raw input and produce validated FRD and NFRD documents ready for sdd_init.
 
 color: magenta
@@ -31,14 +31,14 @@ You are a senior requirements engineer. You transform unstructured input into va
 - NFRD_{ProjectName}_v1_0_0_{YYYY-MM-DD}.md — Non-Functional Requirements Document
 
 **Workflow:**
-1. Read the `sdd-markdown-standard` SKILL.md for artifact formatting rules
+1. Read the `specky-sdd-markdown-standard` SKILL.md for artifact formatting rules
 2. Read existing workspace files for context
-2. Detect project type and domain
-3. Run gap detector — ask max 3 questions for CRITICAL gaps only
-4. Write FRD with EARS notation for every requirement
-5. Write NFRD with measurable quality constraints
-6. Run 24 validation checks — fix every failure
-7. Deliver Specky Handoff block confirming readiness for sdd_init
+3. Detect project type and domain
+4. Run gap detector — ask max 3 questions for CRITICAL gaps only
+5. Write FRD with EARS notation for every requirement
+6. Write NFRD with measurable quality constraints
+7. Run 24 validation checks — fix every failure
+8. Deliver Specky Handoff block confirming readiness for sdd_init
 
 **Hard rules:**
 - Every requirement must use EARS notation

package/.apm/agents/{research-analyst.agent.md → specky-research-analyst.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: research-analyst
+name: specky-research-analyst
 description: Use this agent to gather technical context before specification. Scans codebases, imports documents, and produces RESEARCH.md.
 
 color: cyan
@@ -27,14 +27,14 @@ Document import feeds into research context.
 You are a technical research analyst. You gather all context needed before the specification phase begins.
 
 **Workflow:**
-1. Read the `research-analyst` SKILL.md for research methodology and tool reference
+1. Read the `specky-research-analyst` SKILL.md for research methodology and tool reference
 2. Read CONSTITUTION.md for project scope and constraints
-2. For brownfield/modernization: call sdd_scan_codebase
-3. Import any external documents or transcripts
-4. Call sdd_discover — present 7 structured discovery questions
-5. Call sdd_research — investigate technical unknowns
-6. Call sdd_check_ecosystem — identify recommended MCP servers
-7. Produce RESEARCH.md with all findings
-8. Suggest handoff to specification
+3. For brownfield/modernization: call sdd_scan_codebase
+4. Import any external documents or transcripts
+5. Call sdd_discover — present 7 structured discovery questions
+6. Call sdd_research — investigate technical unknowns
+7. Call sdd_check_ecosystem — identify recommended MCP servers
+8. Produce RESEARCH.md with all findings
+9. Suggest handoff to specification
 
 **Output:** RESEARCH.md with tech stack, dependencies, API surface, integration points, and discovery findings.

package/.apm/agents/{sdd-clarify.agent.md → specky-sdd-clarify.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: sdd-clarify
+name: specky-sdd-clarify
 description: Use this agent to find and resolve ambiguities in requirements, validate EARS patterns, and produce a clarification log.
 
 color: yellow
@@ -26,9 +26,10 @@ EARS validation is a core responsibility of this agent.
 
 You are a clarification specialist. You find ambiguity in specifications and resolve it through targeted questions and EARS validation.
 
+**First step:** Read the `specky-sdd-clarify` SKILL.md for clarification workflow and EARS validation rules.
+
 **Workflow:**
-1. Read the `sdd-pipeline` SKILL.md for EARS patterns and clarification rules
-2. Read SPECIFICATION.md for the feature
+1. Read SPECIFICATION.md for the feature
 2. Call sdd_clarify — up to 5 disambiguation questions per round
 3. Present questions and wait for developer answers
 4. Call sdd_validate_ears — validate all 6 EARS patterns

package/.apm/agents/{sdd-init.agent.md → specky-sdd-init.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: sdd-init
+name: specky-sdd-init
 description: Use this agent to initialize the SDD pipeline for a new feature. Creates the .specs/ directory structure and CONSTITUTION.md.
 
 color: green
@@ -27,14 +27,14 @@ Brownfield setup needs sdd_init plus sdd_scan_codebase.
 You are the SDD pipeline initializer. Your only job is to scaffold the spec pipeline so every downstream phase has the structure it needs.
 
 **Responsibilities:**
-1. Read the `sdd-pipeline` SKILL.md for pipeline context and phase rules
+1. Read the `specky-sdd-init` SKILL.md for pipeline context and Phase 0 rules
 2. Gather feature name, project type (greenfield/brownfield/migration/API), and constraints
 3. Read existing FRD/NFRD from `docs/requirements/` if they exist
 4. Call `sdd_init` to create `.specs/NNN-feature/` with CONSTITUTION.md and .sdd-state.json
 5. Call `sdd_create_branch` to create `spec/NNN-feature-name` from `develop` for all pipeline work
 6. For brownfield projects, call `sdd_scan_codebase` to detect the tech stack
 7. Present CONSTITUTION.md to the developer for review
-8. Suggest handoff to `@research-analyst`
+8. Suggest handoff to `@specky-research-analyst`
 
 **Hard rules:**
 - Never assign your own sequence number (NNN) — let sdd_init handle it

package/.apm/agents/{spec-engineer.agent.md → specky-spec-engineer.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: spec-engineer
+name: specky-spec-engineer
 description: Phase 2 agent that writes SPECIFICATION.md using EARS notation. Every requirement gets a unique REQ-ID, one of the 6 EARS patterns, and measurable acceptance criteria.
 
 color: magenta
@@ -26,7 +26,7 @@ Incremental spec refinement is also this agent's job.
 
 You are a senior specification engineer. You transform research findings into precise, testable requirements.
 
-**First step:** Read the `sdd-pipeline` SKILL.md for EARS notation patterns and specification rules.
+**First step:** Read the `specky-spec-engineer` SKILL.md for EARS notation patterns and specification rules.
 
 **Workflow:**
 1. Read CONSTITUTION.md for project scope and constraints

package/.apm/agents/{task-planner.agent.md → specky-task-planner.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: task-planner
+name: specky-task-planner
 description: Phase 5 agent that writes TASKS.md with dependency-resolved task sequences, REQ-ID traceability, complexity estimates, and parallel markers. Also generates CHECKLIST.md.
 
 color: orange
@@ -26,7 +26,7 @@ Checklist generation can run standalone.
 
 You are a senior technical planner. You transform designs into actionable implementation plans.
 
-**First step:** Read the `sdd-pipeline` SKILL.md for task breakdown standards.
+**First step:** Read the `specky-task-planner` SKILL.md for task breakdown standards.
 
 **Workflow:**
 1. Read DESIGN.md for architecture and API contracts

package/.apm/agents/{test-verifier.agent.md → specky-test-verifier.agent.md}

@@ -1,5 +1,5 @@
 ---
-name: test-verifier
+name: specky-test-verifier
 description: Use this agent to verify test coverage, detect phantom completions, and check spec-code drift.
 
 color: yellow
@@ -27,7 +27,7 @@ Phantom detection prevents false confidence in test results.
 You are a test verification specialist. You verify that implementation satisfies specification with evidence.
 
 **Workflow:**
-1. Read the `test-verifier` SKILL.md for verification criteria and gate thresholds
+1. Read the `specky-test-verifier` SKILL.md for verification criteria and gate thresholds
 2. Call sdd_verify_tests — parse results, map to REQ-IDs, build coverage report
 3. Call sdd_verify_tasks — detect phantom completions
 4. Call sdd_check_sync — detect spec-code drift

package/.apm/hooks/scripts/{artifact-validator.sh → specky-artifact-validator.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# artifact-validator.sh — Validate prerequisite .md artifacts before tool execution
+# specky-artifact-validator.sh — Validate prerequisite .md artifacts before tool execution
 # Type: BLOCKING (exit 2) | Trigger: PreToolUse | All phases
 # Ensures required artifacts exist before a phase tool runs
 
@@ -11,7 +11,7 @@ FAILS=0
 
 if [ -z "$LATEST" ]; then
   if [ "$TOOL" != "sdd_init" ]; then
-    echo "❌ No .specs/ directory found. Run @sdd-init first."
+    echo "❌ No .specs/ directory found. Run @specky-sdd-init first."
     exit 2
   fi
   exit 0
@@ -45,24 +45,24 @@ case "$TOOL" in
     echo "  ✅ No prerequisites for sdd_init"
     ;;
   sdd_discover|sdd_research|sdd_import_document|sdd_import_transcript|sdd_batch_import)
-    check_exists "CONSTITUTION.md" "CONSTITUTION.md" "Run @sdd-init or /specky-greenfield"
+    check_exists "CONSTITUTION.md" "CONSTITUTION.md" "Run @specky-sdd-init or /specky-greenfield"
     ;;
   sdd_clarify|sdd_validate_ears)
-    check_exists "CONSTITUTION.md" "CONSTITUTION.md" "Run @sdd-init"
+    check_exists "CONSTITUTION.md" "CONSTITUTION.md" "Run @specky-sdd-init"
     ;;
   sdd_write_spec|sdd_turnkey_spec|sdd_figma_to_spec)
-    check_exists "CONSTITUTION.md" "CONSTITUTION.md" "Run @sdd-init"
+    check_exists "CONSTITUTION.md" "CONSTITUTION.md" "Run @specky-sdd-init"
     ;;
   sdd_write_design|sdd_generate_all_diagrams)
-    check_exists "SPECIFICATION.md" "SPECIFICATION.md" "Run @spec-engineer or /specky-specify"
+    check_exists "SPECIFICATION.md" "SPECIFICATION.md" "Run @specky-spec-engineer or /specky-specify"
     check_content "SPECIFICATION.md" "REQ-[A-Z]+-[0-9]+" "EARS requirements with REQ-IDs"
     ;;
   sdd_write_tasks|sdd_checklist)
-    check_exists "DESIGN.md" "DESIGN.md" "Run @design-architect or /specky-design"
+    check_exists "DESIGN.md" "DESIGN.md" "Run @specky-design-architect or /specky-design"
     check_exists "SPECIFICATION.md" "SPECIFICATION.md" "Run /specky-specify first"
     ;;
   sdd_implement|sdd_generate_tests|sdd_generate_pbt)
-    check_exists "TASKS.md" "TASKS.md" "Run @task-planner or /specky-tasks"
+    check_exists "TASKS.md" "TASKS.md" "Run @specky-task-planner or /specky-tasks"
     check_exists "DESIGN.md" "DESIGN.md" "Run /specky-design first"
     ;;
   sdd_verify_tests|sdd_verify_tasks|sdd_check_sync)
@@ -70,7 +70,7 @@ case "$TOOL" in
     check_exists "TASKS.md" "TASKS.md" "Run /specky-tasks"
     ;;
   sdd_run_analysis|sdd_cross_analyze)
-    check_exists "VERIFICATION.md" "VERIFICATION.md" "Run @test-verifier or /specky-verify"
+    check_exists "VERIFICATION.md" "VERIFICATION.md" "Run @specky-test-verifier or /specky-verify"
     check_exists "SPECIFICATION.md" "SPECIFICATION.md" "Run /specky-specify"
     check_exists "DESIGN.md" "DESIGN.md" "Run /specky-design"
     check_exists "TASKS.md" "TASKS.md" "Run /specky-tasks"
@@ -79,8 +79,8 @@ case "$TOOL" in
     check_exists "SPECIFICATION.md" "SPECIFICATION.md" "Run /specky-specify"
     ;;
   sdd_create_pr|sdd_export_work_items)
-    check_exists "ANALYSIS.md" "ANALYSIS.md" "Run @quality-reviewer"
-    check_exists "VERIFICATION.md" "VERIFICATION.md" "Run @test-verifier"
+    check_exists "ANALYSIS.md" "ANALYSIS.md" "Run @specky-quality-reviewer"
+    check_exists "VERIFICATION.md" "VERIFICATION.md" "Run @specky-test-verifier"
     ;;
   sdd_generate_all_docs|sdd_generate_docs|sdd_generate_api_docs|sdd_generate_runbook|sdd_generate_onboarding)
     check_exists "SPECIFICATION.md" "SPECIFICATION.md" "Run /specky-specify"

package/.apm/hooks/scripts/{auto-checkpoint.sh → specky-auto-checkpoint.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# auto-checkpoint.sh — Suggest checkpoint when spec artifacts are written
+# specky-auto-checkpoint.sh — Suggest checkpoint when spec artifacts are written
 # Target: Claude Code (.claude/hooks/)
 # Type: Advisory | Trigger: PostToolUse | Phase: 0,3,4,5
 # Paper: arXiv:2602.20478 — artifact preservation

package/.apm/hooks/scripts/{branch-validator.sh → specky-branch-validator.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# branch-validator.sh — Validate git branch matches expected pattern for current tool.
+# specky-branch-validator.sh — Validate git branch matches expected pattern for current tool.
 #
 # Type: Mixed (see below) | Trigger: PreToolUse | All phases
 #   • Advisory (exit 0, warn) for sdd_* pipeline tools (always).
@@ -42,13 +42,13 @@ if [[ "$TOOL" == "Write" || "$TOOL" == "Edit" || "$TOOL" == "MultiEdit" ]]; then
     local expected="$1"
     if [ "$SPECKY_GUARD_MODE" = "strict" ]; then
       echo "" >&2
-      echo "🚫 [branch-validator] BLOCKED — $TOOL on '$CURRENT_BRANCH' (phase $PHASE expects $expected) [SPECKY_GUARD=strict]" >&2
+      echo "🚫 [specky-branch-validator] BLOCKED — $TOOL on '$CURRENT_BRANCH' (phase $PHASE expects $expected) [SPECKY_GUARD=strict]" >&2
       echo "   Feature:  $FEATURE" >&2
       echo "   Fix:      git checkout $expected   (or: git checkout -b spec/$FEATURE)" >&2
       echo "   Disable:  unset SPECKY_GUARD" >&2
       exit 2
     fi
-    echo "⚠️  [branch-validator] $TOOL on '$CURRENT_BRANCH' during phase $PHASE (expected $expected). Enforce with: export SPECKY_GUARD=strict" >&2
+    echo "⚠️  [specky-branch-validator] $TOOL on '$CURRENT_BRANCH' during phase $PHASE (expected $expected). Enforce with: export SPECKY_GUARD=strict" >&2
   }
 
   case "$PHASE" in

package/.apm/hooks/scripts/{cognitive-debt-alert.sh → specky-cognitive-debt-alert.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# cognitive-debt-alert.sh — Alert when LGTM-without-modification rate is high
+# specky-cognitive-debt-alert.sh — Alert when LGTM-without-modification rate is high
 # Target: Claude Code (.claude/hooks/)
 # Type: Advisory | Trigger: PostToolUse | Phase: 8
 # Paper: arXiv:2603.22106 — cognitive surrender measurement

package/.apm/hooks/scripts/{drift-monitor.sh → specky-drift-monitor.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# drift-monitor.sh — Monitor CONSTITUTION.md drift from spec artifacts
+# specky-drift-monitor.sh — Monitor CONSTITUTION.md drift from spec artifacts
 # Target: Claude Code (.claude/hooks/)
 # Type: Advisory | Trigger: PostToolUse | Phase: 8
 # Paper: arXiv:2602.20478, arXiv:2603.22106

package/.apm/hooks/scripts/{ears-validator.sh → specky-ears-validator.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# ears-validator.sh — Validate EARS pattern compliance
+# specky-ears-validator.sh — Validate EARS pattern compliance
 # Target: Claude Code (.claude/hooks/)
 # Type: Advisory | Trigger: PostToolUse | Phase: 2,3
 # Paper: arXiv:2601.03878 — EARS quality

package/.apm/hooks/scripts/{lgtm-gate.sh → specky-lgtm-gate.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# lgtm-gate.sh — Prompt human review at LGTM checkpoints (Phases 3, 4, 5)
+# specky-lgtm-gate.sh — Prompt human review at LGTM checkpoints (Phases 3, 4, 5)
 # Type: Advisory (exit 0) | Trigger: PostToolUse | sdd_write_spec, sdd_write_design, sdd_write_tasks
 # Summarizes artifact and prompts for LGTM before phase advancement
 

package/.apm/hooks/scripts/{metrics-dashboard.sh → specky-metrics-dashboard.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# metrics-dashboard.sh — Generate metrics dashboard reminder
+# specky-metrics-dashboard.sh — Generate metrics dashboard reminder
 # Target: Claude Code (.claude/hooks/)
 # Type: Advisory | Trigger: PostToolUse | Phase: 8
 # Paper: arXiv:2507.09089 — AI productivity paradox
@@ -10,7 +10,7 @@ LATEST=$(ls -td .specs/*/ 2>/dev/null | head -1 || true)
 [ -z "$LATEST" ] && exit 0
 
 # Check if analysis is done but metrics not generated
-if [ -f "$LATEST/ANALYSIS.md" ] && [ ! -f "$LATEST/metrics-dashboard.html" ]; then
+if [ -f "$LATEST/ANALYSIS.md" ] && [ ! -f "$LATEST/specky-metrics-dashboard.html" ]; then
   echo "📊 ANALYSIS.md complete but no metrics dashboard generated."
   echo "   Run sdd_metrics to generate the HTML dashboard with:"
   echo "   - Cognitive debt score"

package/.apm/hooks/scripts/{phase-gate.sh → specky-phase-gate.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# phase-gate.sh — Validate output artifact was created after tool execution
+# specky-phase-gate.sh — Validate output artifact was created after tool execution
 # Type: BLOCKING (exit 2) | Trigger: PostToolUse | Artifact-writing tools
 # Ensures phase artifacts exist and meet minimum quality after creation
 

package/.apm/hooks/scripts/{pipeline-guard.sh → specky-pipeline-guard.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# pipeline-guard.sh — Remind about Rule #8: all work flows through @specky-orchestrator.
+# specky-pipeline-guard.sh — Remind about Rule #8: all work flows through @specky-orchestrator.
 # Target: Claude Code (.claude/hooks/) + GitHub Copilot (.github/hooks/specky/)
 # Type: ADVISORY by default (warn, exit 0) | Trigger: UserPromptSubmit
 # Phase: any — runs on every user prompt when .specs/ has an active pipeline
@@ -105,7 +105,7 @@ fi
 if echo "$PROMPT_LC" | grep -qE '(^|[^a-z0-9])(implement|create|build|write|code|fix|add|refactor|deploy|release|merge|commit|push|test|install|setup|configure)([^a-z0-9]|$)'; then
   if [ "$SPECKY_GUARD_MODE" = "strict" ]; then
     echo "" >&2
-    echo "🚫 [pipeline-guard] BLOCKED — active Specky pipeline detected (SPECKY_GUARD=strict)" >&2
+    echo "🚫 [specky-pipeline-guard] BLOCKED — active Specky pipeline detected (SPECKY_GUARD=strict)" >&2
     echo "" >&2
     echo "   Feature:    $FEATURE" >&2
     echo "   Phase:      $PHASE" >&2
@@ -125,7 +125,7 @@ if echo "$PROMPT_LC" | grep -qE '(^|[^a-z0-9])(implement|create|build|write|code
   fi
 
   # Advisory mode (default): warn but allow.
-  echo "⚠️  [pipeline-guard] active Specky pipeline ($FEATURE, phase $PHASE) — consider routing through @specky-orchestrator." >&2
+  echo "⚠️  [specky-pipeline-guard] active Specky pipeline ($FEATURE, phase $PHASE) — consider routing through @specky-orchestrator." >&2
   echo "   Enforce blocking with: export SPECKY_GUARD=strict" >&2
 fi
 

package/.apm/hooks/scripts/{release-gate.sh → specky-release-gate.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# release-gate.sh — Verify VERIFICATION.md + 90% pass rate before PR
+# specky-release-gate.sh — Verify VERIFICATION.md + 90% pass rate before PR
 # Target: Claude Code (.claude/hooks/)
 # Type: BLOCKING (exit 2) | Trigger: before sdd_create_pr | Phase: 9
 # Paper: arXiv:2601.03878 — human-in-loop gate

package/.apm/hooks/scripts/{security-scan.sh → specky-security-scan.sh}

@@ -1,11 +1,11 @@
 #!/bin/bash
-# security-scan.sh — OWASP + secrets scan
+# specky-security-scan.sh — OWASP + secrets scan
 # Target: Claude Code (.claude/hooks/)
 # Type: BLOCKING (exit 2) | Trigger: Stop | Phase: 9
 # Paper: arXiv:2503.23278 — security enforcement
 #
 # Claude Code settings.json:
-#   "hooks": { "Stop": ["bash .claude/hooks/security-scan.sh"] }
+#   "hooks": { "Stop": ["bash .claude/hooks/specky-security-scan.sh"] }
 
 set -euo pipefail
 FAILS=0

package/.apm/hooks/scripts/{session-banner.sh → specky-session-banner.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# session-banner.sh — Show Specky pipeline status at session start.
+# specky-session-banner.sh — Show Specky pipeline status at session start.
 # Target: Claude Code + GitHub Copilot
 # Type: Advisory (exit 0 always) | Trigger: SessionStart
 #
@@ -60,20 +60,20 @@ echo ""
 case "$PHASE" in
   init|discover|specify|clarify|design|tasks|analyze|implement)
     if [[ ! "$BRANCH" =~ ^spec/ ]]; then
-      echo "⚠️  [session-banner] Phase $PHASE expects branch spec/NNN-* — you are on '$BRANCH'"
+      echo "⚠️  [specky-session-banner] Phase $PHASE expects branch spec/NNN-* — you are on '$BRANCH'"
       echo "    Consider: git checkout -b spec/$FEATURE (or let @specky-orchestrator handle it)"
       echo ""
     fi
     ;;
   verify)
     if [ "$BRANCH" != "develop" ]; then
-      echo "⚠️  [session-banner] Phase 'verify' expects branch 'develop' — you are on '$BRANCH'"
+      echo "⚠️  [specky-session-banner] Phase 'verify' expects branch 'develop' — you are on '$BRANCH'"
       echo ""
     fi
     ;;
   release)
     if [ "$BRANCH" != "stage" ]; then
-      echo "⚠️  [session-banner] Phase 'release' expects branch 'stage' — you are on '$BRANCH'"
+      echo "⚠️  [specky-session-banner] Phase 'release' expects branch 'stage' — you are on '$BRANCH'"
       echo ""
     fi
     ;;

package/.apm/hooks/scripts/{spec-quality.sh → specky-spec-quality.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# spec-quality.sh — Validate specification quality after sdd_write_spec
+# specky-spec-quality.sh — Validate specification quality after sdd_write_spec
 # Target: Claude Code (.claude/hooks/)
 # Type: Advisory | Trigger: PostToolUse | Phase: 3
 # Paper: arXiv:2601.03878 — EARS quality

package/.apm/hooks/scripts/{spec-sync.sh → specky-spec-sync.sh}

@@ -1,11 +1,11 @@
 #!/bin/bash
-# spec-sync.sh — Detect spec-code drift
+# specky-spec-sync.sh — Detect spec-code drift
 # Target: Claude Code (.claude/hooks/)
 # Type: Advisory | Trigger: PostToolUse | Phase: 6
 # Paper: arXiv:2602.20478 — anti-context-collapse
 #
 # Claude Code settings.json:
-#   "hooks": { "PostToolUse": ["bash .claude/hooks/spec-sync.sh"] }
+#   "hooks": { "PostToolUse": ["bash .claude/hooks/specky-spec-sync.sh"] }
 
 set -euo pipefail
 SPECS_DIR=".specs"

package/.apm/hooks/scripts/{task-tracer.sh → specky-task-tracer.sh}

@@ -1,5 +1,5 @@
 #!/bin/bash
-# task-tracer.sh — Detect tasks missing REQ-* traceability
+# specky-task-tracer.sh — Detect tasks missing REQ-* traceability
 # Target: Claude Code (.claude/hooks/)
 # Type: Advisory | Trigger: PostToolUse | Phase: 5
 # Paper: arXiv:2602.00180 — SDD traceability