specky-sdd 3.7.3 → 3.9.0

package/.apm/prompts/specky-implement.prompt.md

@@ -5,4 +5,4 @@ argument-hint: <feature-number>
 ---
 Run the SDD implementation phase for feature [FEATURE NUMBER].
 
-@implementer — generate implementation plan, quality checklists, test stubs with REQ-* traceability, and infrastructure scaffolding.
+@specky-implementer — generate implementation plan, quality checklists, test stubs with REQ-* traceability, and infrastructure scaffolding.

package/.apm/prompts/specky-migration.prompt.md

@@ -11,6 +11,6 @@ Plan a system migration using the Specky SDD pipeline.
 **Timeline:** [Migration deadline or phases]
 
 Please:
-1. Call @requirements-engineer to capture migration requirements as FRD + NFRD
-2. Call @sdd-init with project_type=migration
-3. Call @research-analyst to scan both source and target
+1. Call @specky-requirements-engineer to capture migration requirements as FRD + NFRD
+2. Call @specky-sdd-init with project_type=migration
+3. Call @specky-research-analyst to scan both source and target

package/.apm/prompts/specky-onboarding.prompt.md

@@ -1,5 +1,6 @@
 ---
 description: Get started with Specky SDD — interactive wizard
+argument-hint: <project context or goal>
 agent: agent
 ---
 Help me get started with Specky SDD.

package/.apm/prompts/specky-pipeline-status.prompt.md

@@ -1,5 +1,6 @@
 ---
 description: Check SDD pipeline status
+argument-hint: <feature-number or all>
 agent: agent
 ---
 Check the SDD pipeline status for feature [FEATURE NUMBER or "all"].

package/.apm/prompts/specky-release.prompt.md

@@ -8,4 +8,4 @@ Run the SDD release phase for feature [FEATURE NUMBER].
 **Branch:** [current spec/NNN-* branch]
 **Target:** develop (then stage → main after gates pass)
 
-@release-engineer — verify branch, run blocking gates (security-scan + release-gate), generate documentation, create PR targeting the correct branch.
+@specky-release-engineer — verify branch, run blocking gates (specky-security-scan + specky-release-gate), generate documentation, create PR targeting the correct branch.

package/.apm/prompts/specky-research.prompt.md

@@ -5,4 +5,4 @@ argument-hint: <feature-number or research topic>
 ---
 Run the SDD Discover phase (research) for feature [FEATURE NUMBER].
 
-@research-analyst — scan the codebase, import relevant documents, run discovery questions, and produce RESEARCH.md.
+@specky-research-analyst — scan the codebase, import relevant documents, run discovery questions, and produce RESEARCH.md.

package/.apm/prompts/specky-specify.prompt.md

@@ -5,4 +5,4 @@ argument-hint: <feature-number>
 ---
 Run the SDD specification phase for feature [FEATURE NUMBER].
 
-@spec-engineer — write SPECIFICATION.md using EARS notation. Every requirement must have a unique REQ-ID (REQ-DOMAIN-NNN), one of the 6 EARS patterns, and measurable acceptance criteria. Call sdd_write_spec then sdd_validate_ears.
+@specky-spec-engineer — write SPECIFICATION.md using EARS notation. Every requirement must have a unique REQ-ID (REQ-DOMAIN-NNN), one of the 6 EARS patterns, and measurable acceptance criteria. Call sdd_write_spec then sdd_validate_ears.

package/.apm/prompts/specky-tasks.prompt.md

@@ -5,4 +5,4 @@ argument-hint: <feature-number>
 ---
 Run the SDD task breakdown phase for feature [FEATURE NUMBER].
 
-@task-planner — produce TASKS.md with dependency-resolved task sequence, [P] parallel markers, REQ-* traceability on every task, and complexity estimates (S/M/L/XL). Call sdd_write_tasks then sdd_checklist.
+@specky-task-planner — produce TASKS.md with dependency-resolved task sequence, [P] parallel markers, REQ-* traceability on every task, and complexity estimates (S/M/L/XL). Call sdd_write_tasks then sdd_checklist.

package/.apm/prompts/specky-verify.prompt.md

@@ -5,4 +5,4 @@ argument-hint: <feature-number>
 ---
 Run the SDD verification phase for feature [FEATURE NUMBER].
 
-@test-verifier — verify test coverage, detect phantom completions, check spec-code drift. Gate: ≥90% pass, all P0 covered, zero phantoms.
+@specky-test-verifier — verify test coverage, detect phantom completions, check spec-code drift. Gate: ≥90% pass, all P0 covered, zero phantoms.

package/.apm/skills/specky-design-architect/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: specky-design-architect
+description: "Use for Phase 4 (Design): produce DESIGN.md with architecture, API contracts, data model, and Mermaid diagrams. Trigger on sdd_write_design, sdd_generate_all_diagrams, or /specky-design."
+---
+
+# Phase 4 — Design
+
+## Prerequisites
+- Approved SPECIFICATION.md at the Phase 2 LGTM gate
+
+## Workflow
+1. Read SPECIFICATION.md and CONSTITUTION.md
+2. Call `sdd_write_design` for architecture, API contracts, data model, and deployment topology
+3. Call `sdd_generate_all_diagrams`
+4. Trace every design decision to a REQ-ID
+5. Present DESIGN.md for LGTM at the Phase 4 gate
+
+## Hard Rules
+- API contracts cover all functional REQ-IDs
+- Diagrams use Mermaid syntax only
+- Branch must be `spec/NNN-*`

package/.apm/skills/{implementer → specky-implementer}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: implementer
+name: specky-implementer
 description: "This skill should be used when the user asks to 'generate implementation plan', 'create test stubs', 'set up infrastructure', 'generate quality checklists', 'transition from spec to code', or needs guidance on Phase 7 implementation scaffolding. Also trigger on 'sdd implement', 'implementation handoff', 'IaC generation', or 'test framework selection'."
 ---
 
@@ -119,7 +119,7 @@ Continuous synchronization between SPECIFICATION.md and implementation:
 - When code deviates from SPECIFICATION.md, flag as spec drift
 - When implementation discovers missing requirement, update SPECIFICATION.md
 - If design changes needed mid-implementation, update DESIGN.md and notify stakeholders
-- Daily spec-sync report comparing implemented features to SPECIFICATION.md
+- Daily specky-spec-sync report comparing implemented features to SPECIFICATION.md
 
 ## Implementation Handoff Template
 
@@ -168,4 +168,4 @@ Reference: **arXiv:2502.08235** — Use standard inference (no extended thinking
 
 ## Companion Agent
 
-**@implementer** — Phase 7 agent that calls these tools in sequence. Load this skill as first step.
+**@specky-implementer** — Phase 7 agent that calls these tools in sequence. Load this skill as first step.

package/.apm/skills/specky-onboarding/SKILL.md

@@ -7,7 +7,7 @@ description: "This skill should be used when the user asks 'help me with specky'
 
 ## Overview
 
-Specky SDD is a Spec-Driven Development CLI toolkit with 58 MCP tools, 13 agents, 22 prompts, 8 skills, and 16 hook scripts. It enforces a 10-phase pipeline from requirements through release.
+Specky SDD is a Spec-Driven Development CLI toolkit with 58 MCP tools, 13 agents, 22 prompts, 14 skills, and 16 hook scripts. It enforces a 10-phase pipeline from requirements through release.
 
 ## 5-Step Wizard Flow
 
@@ -47,17 +47,17 @@ Check for:
 |-------|-------|---------|
 | @specky-onboarding | Pre | Interactive wizard and help |
 | @specky-orchestrator | All | Full pipeline coordinator |
-| @sdd-init | 0 | Initialize pipeline + create spec branch |
-| @research-analyst | 1 | Codebase scan + discovery |
-| @spec-engineer | 2 | Write SPECIFICATION.md with EARS |
-| @sdd-clarify | 3 | Resolve ambiguities + EARS validation |
-| @design-architect | 4 | Write DESIGN.md + diagrams |
-| @task-planner | 5 | Write TASKS.md + CHECKLIST.md |
-| @quality-reviewer | 6 | Completeness audit + compliance |
-| @implementer | 7 | Implementation plan + test stubs + IaC |
-| @test-verifier | 8 | Coverage + drift + phantom detection |
-| @requirements-engineer | Pre | FRD + NFRD from raw input |
-| @release-engineer | 9 | Gates + PR + docs + work items |
+| @specky-sdd-init | 0 | Initialize pipeline + create spec branch |
+| @specky-research-analyst | 1 | Codebase scan + discovery |
+| @specky-spec-engineer | 2 | Write SPECIFICATION.md with EARS |
+| @specky-sdd-clarify | 3 | Resolve ambiguities + EARS validation |
+| @specky-design-architect | 4 | Write DESIGN.md + diagrams |
+| @specky-task-planner | 5 | Write TASKS.md + CHECKLIST.md |
+| @specky-quality-reviewer | 6 | Completeness audit + compliance |
+| @specky-implementer | 7 | Implementation plan + test stubs + IaC |
+| @specky-test-verifier | 8 | Coverage + drift + phantom detection |
+| @specky-requirements-engineer | Pre | FRD + NFRD from raw input |
+| @specky-release-engineer | 9 | Gates + PR + docs + work items |
 
 ## All 22 Prompts
 
@@ -91,18 +91,24 @@ Check for:
 - /specky-pipeline-status — Check pipeline status
 - /specky-reset-phase — Reset a pipeline phase
 
-## All 8 Skills
+## All 14 Skills
 
 | Skill | Triggers On |
 |-------|-------------|
-| sdd-pipeline | "specky", "SDD pipeline", "EARS notation", "pipeline phases" |
+| specky-sdd-pipeline | "specky", "SDD pipeline", "EARS notation", "pipeline phases" |
 | specky-orchestrator | "orchestrate", "run full pipeline", "advance phase" |
 | specky-onboarding | "help", "get started", "what is specky" |
+| specky-sdd-init | "initialize", "greenfield", "new feature bootstrap" |
+| specky-spec-engineer | "write specification", "EARS", "REQ-ID" |
+| specky-sdd-clarify | "clarify", "ambiguous requirements", "EARS validation" |
+| specky-design-architect | "design", "architecture", "Mermaid diagrams" |
+| specky-task-planner | "tasks", "checklist", "implementation plan" |
+| specky-quality-reviewer | "analysis", "quality review", "compliance" |
 | implementer | "implementation plan", "test stubs", "IaC generation" |
 | test-verifier | "verify tests", "check coverage", "phantom detection" |
 | release-engineer | "prepare release", "create PR", "release gates" |
 | research-analyst | "research codebase", "scan tech stack", "import documents" |
-| sdd-markdown-standard | "artifact format", "spec formatting" |
+| specky-sdd-markdown-standard | "artifact format", "spec formatting" |
 
 ## 58 MCP Tools by Category
 
@@ -135,21 +141,21 @@ Check for:
 ## 16 Hook Scripts
 
 **Blocking (exit 2 = halt):**
-- artifact-validator.sh — Prerequisite .md files exist
-- phase-gate.sh — Output artifact created with quality
-- security-scan.sh — OWASP + secrets scan
-- release-gate.sh — 90% pass rate + artifact checks
+- specky-artifact-validator.sh — Prerequisite .md files exist
+- specky-phase-gate.sh — Output artifact created with quality
+- specky-security-scan.sh — OWASP + secrets scan
+- specky-release-gate.sh — 90% pass rate + artifact checks
 
 **Advisory (exit 0 = warn):**
-- branch-validator.sh — Branch matches phase expectations
-- pipeline-guard.sh — Pipeline ordering / phase-skip guard
-- lgtm-gate.sh — Human review reminder at Phases 2/4/5
-- session-banner.sh — Session start pipeline-status banner
-- spec-sync.sh — Detect spec-code drift
-- auto-checkpoint.sh — Suggest checkpoint after writes
-- spec-quality.sh — Specification quality metrics
-- ears-validator.sh — EARS pattern compliance
-- task-tracer.sh — Task dependency graph
-- drift-monitor.sh — CONSTITUTION drift detection
-- cognitive-debt-alert.sh — Cognitive surrender detection
-- metrics-dashboard.sh — Quality metrics collection
+- specky-branch-validator.sh — Branch matches phase expectations
+- specky-pipeline-guard.sh — Pipeline ordering / phase-skip guard
+- specky-lgtm-gate.sh — Human review reminder at Phases 2/4/5
+- specky-session-banner.sh — Session start pipeline-status banner
+- specky-spec-sync.sh — Detect spec-code drift
+- specky-auto-checkpoint.sh — Suggest checkpoint after writes
+- specky-spec-quality.sh — Specification quality metrics
+- specky-ears-validator.sh — EARS pattern compliance
+- specky-task-tracer.sh — Task dependency graph
+- specky-drift-monitor.sh — CONSTITUTION drift detection
+- specky-cognitive-debt-alert.sh — Cognitive surrender detection
+- specky-metrics-dashboard.sh — Quality metrics collection

package/.apm/skills/specky-orchestrator/SKILL.md

@@ -15,16 +15,16 @@ Model guidance is capability-based: fast, balanced, and reasoning-focused. Do no
 
 | Phase | Agent | Recommended Class | MCP Tools | Required Input | Output Artifact |
 |-------|-------|-------------------|-----------|----------------|-----------------|
-| 0 Init | @sdd-init | Fast | sdd_init, sdd_scan_codebase | — | CONSTITUTION.md, .sdd-state.json |
-| 1 Discover | @research-analyst | Balanced | sdd_discover, sdd_research, sdd_import_document, sdd_import_transcript, sdd_check_ecosystem | CONSTITUTION.md | RESEARCH.md |
-| 2 Specify | @spec-engineer | Reasoning-focused | sdd_write_spec, sdd_turnkey_spec, sdd_validate_ears, sdd_figma_to_spec | RESEARCH.md | SPECIFICATION.md |
-| 3 Clarify | @sdd-clarify | Reasoning-focused | sdd_clarify, sdd_validate_ears, sdd_turnkey_spec | SPECIFICATION.md | Updates to SPECIFICATION.md |
-| 4 Design | @design-architect | Reasoning-focused | sdd_write_design, sdd_generate_all_diagrams, sdd_generate_diagram | SPECIFICATION.md | DESIGN.md |
-| 5 Tasks | @task-planner | Balanced | sdd_write_tasks, sdd_checklist | DESIGN.md | TASKS.md, CHECKLIST.md |
-| 6 Analyze | @quality-reviewer | Balanced | sdd_run_analysis, sdd_cross_analyze, sdd_compliance_check, sdd_check_sync | TASKS.md, CHECKLIST.md | ANALYSIS.md, COMPLIANCE.md |
-| 7 Implement | @implementer | Balanced | sdd_implement, sdd_generate_tests, sdd_generate_pbt, sdd_generate_iac, sdd_generate_dockerfile | ANALYSIS.md | Code scaffolding, test stubs |
-| 8 Verify | @test-verifier | Reasoning-focused | sdd_verify_tests, sdd_verify_tasks, sdd_check_sync, sdd_validate_ears | SPECIFICATION.md, TASKS.md | VERIFICATION.md, CROSS_ANALYSIS.md |
-| 9 Release | @release-engineer | Fast | sdd_create_pr, sdd_generate_all_docs, sdd_export_work_items | ANALYSIS.md (APPROVE) | PR, docs, work items |
+| 0 Init | @specky-sdd-init | Fast | sdd_init, sdd_scan_codebase | — | CONSTITUTION.md, .sdd-state.json |
+| 1 Discover | @specky-research-analyst | Balanced | sdd_discover, sdd_research, sdd_import_document, sdd_import_transcript, sdd_check_ecosystem | CONSTITUTION.md | RESEARCH.md |
+| 2 Specify | @specky-spec-engineer | Reasoning-focused | sdd_write_spec, sdd_turnkey_spec, sdd_validate_ears, sdd_figma_to_spec | RESEARCH.md | SPECIFICATION.md |
+| 3 Clarify | @specky-sdd-clarify | Reasoning-focused | sdd_clarify, sdd_validate_ears, sdd_turnkey_spec | SPECIFICATION.md | Updates to SPECIFICATION.md |
+| 4 Design | @specky-design-architect | Reasoning-focused | sdd_write_design, sdd_generate_all_diagrams, sdd_generate_diagram | SPECIFICATION.md | DESIGN.md |
+| 5 Tasks | @specky-task-planner | Balanced | sdd_write_tasks, sdd_checklist | DESIGN.md | TASKS.md, CHECKLIST.md |
+| 6 Analyze | @specky-quality-reviewer | Balanced | sdd_run_analysis, sdd_cross_analyze, sdd_compliance_check, sdd_check_sync | TASKS.md, CHECKLIST.md | ANALYSIS.md, COMPLIANCE.md |
+| 7 Implement | @specky-implementer | Balanced | sdd_implement, sdd_generate_tests, sdd_generate_pbt, sdd_generate_iac, sdd_generate_dockerfile | ANALYSIS.md | Code scaffolding, test stubs |
+| 8 Verify | @specky-test-verifier | Reasoning-focused | sdd_verify_tests, sdd_verify_tasks, sdd_check_sync, sdd_validate_ears | SPECIFICATION.md, TASKS.md | VERIFICATION.md, CROSS_ANALYSIS.md |
+| 9 Release | @specky-release-engineer | Fast | sdd_create_pr, sdd_generate_all_docs, sdd_export_work_items | ANALYSIS.md (APPROVE) | PR, docs, work items |
 
 ## Hook Enforcement Matrix
 
@@ -32,34 +32,34 @@ Model guidance is capability-based: fast, balanced, and reasoning-focused. Do no
 
 | Tool Matcher | Hooks | Type |
 |-------------|-------|------|
-| sdd_init | branch-validator | Advisory |
-| sdd_discover, sdd_research, sdd_import_* | artifact-validator, branch-validator | Blocking + Advisory |
-| sdd_write_spec, sdd_turnkey_spec, sdd_figma_to_spec | artifact-validator, branch-validator | Blocking + Advisory |
-| sdd_write_design, sdd_generate_all_diagrams | artifact-validator, branch-validator | Blocking + Advisory |
-| sdd_write_tasks, sdd_checklist | artifact-validator, branch-validator | Blocking + Advisory |
-| sdd_implement, sdd_generate_tests | artifact-validator, branch-validator | Blocking + Advisory |
-| sdd_verify_tests, sdd_verify_tasks | artifact-validator, branch-validator | Blocking + Advisory |
-| sdd_run_analysis, sdd_cross_analyze | artifact-validator, branch-validator | Blocking + Advisory |
-| sdd_create_pr | artifact-validator, branch-validator, security-scan, release-gate | All Blocking |
+| sdd_init | specky-branch-validator | Advisory |
+| sdd_discover, sdd_research, sdd_import_* | specky-artifact-validator, specky-branch-validator | Blocking + Advisory |
+| sdd_write_spec, sdd_turnkey_spec, sdd_figma_to_spec | specky-artifact-validator, specky-branch-validator | Blocking + Advisory |
+| sdd_write_design, sdd_generate_all_diagrams | specky-artifact-validator, specky-branch-validator | Blocking + Advisory |
+| sdd_write_tasks, sdd_checklist | specky-artifact-validator, specky-branch-validator | Blocking + Advisory |
+| sdd_implement, sdd_generate_tests | specky-artifact-validator, specky-branch-validator | Blocking + Advisory |
+| sdd_verify_tests, sdd_verify_tasks | specky-artifact-validator, specky-branch-validator | Blocking + Advisory |
+| sdd_run_analysis, sdd_cross_analyze | specky-artifact-validator, specky-branch-validator | Blocking + Advisory |
+| sdd_create_pr | specky-artifact-validator, specky-branch-validator, specky-security-scan, specky-release-gate | All Blocking |
 
 ### Post-Phase Hooks (validate after tool runs)
 
 | Tool Matcher | Hooks | Type |
 |-------------|-------|------|
-| sdd_init | phase-gate, auto-checkpoint | Blocking + Advisory |
-| sdd_write_spec, sdd_turnkey_spec | phase-gate, spec-quality, ears-validator, lgtm-gate, spec-sync, auto-checkpoint | Mixed |
-| sdd_write_design | phase-gate, spec-sync, lgtm-gate, auto-checkpoint | Mixed |
-| sdd_write_tasks | phase-gate, task-tracer, lgtm-gate, spec-sync, auto-checkpoint | Mixed |
-| sdd_implement, sdd_generate_tests | spec-sync, auto-checkpoint | Advisory |
-| sdd_verify_tests, sdd_verify_tasks | phase-gate, drift-monitor | Mixed |
-| sdd_run_analysis, sdd_cross_analyze | phase-gate, cognitive-debt-alert, metrics-dashboard, drift-monitor | Mixed |
+| sdd_init | specky-phase-gate, specky-auto-checkpoint | Blocking + Advisory |
+| sdd_write_spec, sdd_turnkey_spec | specky-phase-gate, specky-spec-quality, specky-ears-validator, specky-lgtm-gate, specky-spec-sync, specky-auto-checkpoint | Mixed |
+| sdd_write_design | specky-phase-gate, specky-spec-sync, specky-lgtm-gate, specky-auto-checkpoint | Mixed |
+| sdd_write_tasks | specky-phase-gate, specky-task-tracer, specky-lgtm-gate, specky-spec-sync, specky-auto-checkpoint | Mixed |
+| sdd_implement, sdd_generate_tests | specky-spec-sync, specky-auto-checkpoint | Advisory |
+| sdd_verify_tests, sdd_verify_tasks | specky-phase-gate, specky-drift-monitor | Mixed |
+| sdd_run_analysis, sdd_cross_analyze | specky-phase-gate, specky-cognitive-debt-alert, specky-metrics-dashboard, specky-drift-monitor | Mixed |
 
 ## LGTM Gate Protocol
 
 Phases 2 (Specify), 4 (Design), and 5 (Tasks) require human LGTM before advancing:
 
 1. Phase agent completes and writes artifact
-2. lgtm-gate.sh runs → prints artifact summary
+2. specky-lgtm-gate.sh runs → prints artifact summary
 3. Orchestrator asks: "Review [ARTIFACT]. Reply 'LGTM' to proceed."
 4. If LGTM → call sdd_advance_phase → next agent
 5. If feedback → route back to phase agent for revision
@@ -79,7 +79,7 @@ Phases 2 (Specify), 4 (Design), and 5 (Tasks) require human LGTM before advancin
 
 Before calling sdd_advance_phase, verify:
 1. ✅ Required artifact exists (PHASE_REQUIRED_FILES)
-2. ✅ Artifact has minimum quality (phase-gate.sh passed)
+2. ✅ Artifact has minimum quality (specky-phase-gate.sh passed)
 3. ✅ LGTM received (if phase 2, 4, or 5)
 4. ✅ Branch matches expectations
 5. ✅ Checkpoint created (sdd_checkpoint)

package/.apm/skills/specky-quality-reviewer/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: specky-quality-reviewer
+description: "Use for Phase 6 (Analyze): completeness audit, cross-analysis, compliance, and ANALYSIS.md gate decision. Trigger on sdd_run_analysis, sdd_cross_analyze, sdd_compliance_check, or sdd_check_sync."
+---
+
+# Phase 6 — Analyze
+
+## Prerequisites
+- TASKS.md and CHECKLIST.md complete on `spec/NNN-*`, or post-merge on `develop` per project policy
+
+## Workflow
+1. Read SPECIFICATION.md, DESIGN.md, TASKS.md, and CHECKLIST.md
+2. Call `sdd_run_analysis`
+3. Call `sdd_cross_analyze`
+4. Call `sdd_check_sync` if code exists
+5. Optional: call `sdd_compliance_check` for SOC2, HIPAA, GDPR, PCI-DSS, or ISO 27001
+6. Write ANALYSIS.md with gate decision: APPROVE, CONDITIONAL, or REJECT
+7. Write COMPLIANCE.md if compliance ran
+8. Call `sdd_metrics`
+
+## Gate Rules
+- REJECT blocks the pipeline
+- CONDITIONAL lists required fixes
+- Never APPROVE if pass rate is below 90% or critical drift exists
+
+## Hard Rules
+- Findings must be evidence-based
+- Phase 6 runs after Tasks and before Implement/Verify

package/.apm/skills/{release-engineer → specky-release-engineer}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: release-engineer
+name: specky-release-engineer
 description: "This skill should be used when the user asks to 'prepare release', 'create PR', 'generate documentation', 'run release gates', or needs guidance on Phase 9 release. Also trigger on 'sdd release', 'blocking gates', 'security scan', 'release gate', or 'export work items'."
 ---
 
@@ -33,11 +33,11 @@ Missing prerequisites block release. Run `/specky:check-gates` to validate.
 
 Two sequential blocking gates must pass before release:
 
-### Gate 1: Security Gate (security-scan.sh)
+### Gate 1: Security Gate (specky-security-scan.sh)
 
 Execute security scanning:
 ```bash
-./scripts/security-scan.sh --full
+./scripts/specky-security-scan.sh --full
 ```
 
 Checks performed:
@@ -56,11 +56,11 @@ Pass criteria:
 
 Fail items block release completely.
 
-### Gate 2: Release Gate (release-gate.sh)
+### Gate 2: Release Gate (specky-release-gate.sh)
 
 Execute final release checklist:
 ```bash
-./scripts/release-gate.sh --version=X.Y.Z
+./scripts/specky-release-gate.sh --version=X.Y.Z
 ```
 
 Verifies:
@@ -260,7 +260,7 @@ Generate from commit history, SPECIFICATION.md, and VERIFICATION.md:
 
 ```
 /specky:release --version=X.Y.Z          # Full release workflow
-/specky:release --security-scan          # Run security gate only
+/specky:release --specky-security-scan          # Run security gate only
 /specky:release --generate-docs          # Generate docs only
 /specky:release --create-pr --no-merge   # Create PR, don't merge
 /specky:release --export-items            # Export to project mgmt
@@ -290,4 +290,4 @@ If post-release issues detected:
 
 ## Companion Agent
 
-**@release-engineer** — Phase 9 agent that runs blocking gates and calls these tools. Load this skill as first step.
+**@specky-release-engineer** — Phase 9 agent that runs blocking gates and calls these tools. Load this skill as first step.

package/.apm/skills/{research-analyst → specky-research-analyst}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: research-analyst
+name: specky-research-analyst
 description: "This skill should be used when the user asks to 'research codebase', 'scan tech stack', 'import documents', 'discovery questions', or needs guidance on Phase 1 research. Also trigger on 'sdd research', 'brownfield scan', 'import transcript', or 'check ecosystem'."
 ---
 
@@ -283,4 +283,4 @@ Structure the research artifact as:
 
 ## Companion Agent
 
-**@research-analyst** — Phase 1 agent that calls these tools to build the knowledge baseline. Load this skill as first step.
+**@specky-research-analyst** — Phase 1 agent that calls these tools to build the knowledge baseline. Load this skill as first step.

package/.apm/skills/specky-sdd-clarify/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: specky-sdd-clarify
+description: "Use for Phase 3 (Clarify): resolve ambiguous requirements, validate EARS, and produce CLARIFICATION-LOG.md. Trigger on sdd_clarify or /specky-clarify."
+---
+
+# Phase 3 — Clarify
+
+## Prerequisites
+- SPECIFICATION.md exists
+
+## Workflow
+1. Read SPECIFICATION.md
+2. Call `sdd_clarify` with at most 5 questions per round
+3. Wait for developer answers
+4. Call `sdd_validate_ears`
+5. Rewrite non-compliant requirements
+6. Loop until ambiguities are resolved and EARS passes
+7. Write or update CLARIFICATION-LOG.md
+
+## EARS
+Use the canonical 6 patterns in `../specky-sdd-pipeline/references/ears-notation.md`.
+
+## Hard Rules
+- Ask at most 5 disambiguation questions per round
+- Do not advance to Design until ambiguities are resolved

package/.apm/skills/specky-sdd-init/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: specky-sdd-init
+description: "Use when initializing Phase 0 (Init): scaffold .specs/NNN-feature/, CONSTITUTION.md, .sdd-state.json, and spec branch from develop. Trigger on sdd_init, greenfield setup, or new feature bootstrap."
+---
+
+# Phase 0 — Init
+
+## Prerequisites
+- Feature name and project type: greenfield, brownfield, migration, or API
+- `develop` branch exists, or the exception is documented
+
+## Workflow
+1. Gather feature name, project type, and constraints
+2. Read FRD/NFRD from `docs/requirements/` if present
+3. Call `sdd_init` to create `.specs/NNN-feature/`, CONSTITUTION.md, and `.sdd-state.json`
+4. Call `sdd_create_branch` to create `spec/NNN-feature-name` from `develop`
+5. For brownfield projects, call `sdd_scan_codebase`
+6. Present CONSTITUTION.md and wait for developer confirmation
+7. Hand off to `@specky-research-analyst`
+
+## Outputs
+- CONSTITUTION.md
+- `.sdd-state.json`
+
+## Hard Rules
+- Never assign NNN manually; `sdd_init` owns numbering
+- Never write artifacts beyond Phase 0
+- Create `spec/NNN-*` from `develop`, never from `main` or `stage`

package/.apm/skills/{sdd-markdown-standard → specky-sdd-markdown-standard}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: sdd-markdown-standard
+name: specky-sdd-markdown-standard
 description: "This skill should be used when generating or formatting SDD artifacts (CONSTITUTION.md, SPECIFICATION.md, DESIGN.md, TASKS.md, VERIFICATION.md, ANALYSIS.md). Also trigger on 'sdd markdown', 'artifact format', or 'spec formatting'."
 ---
 
@@ -279,4 +279,4 @@ Run markdown linter: `markdownlint sdd-artifacts/`
 
 ## Companion Agent
 
-**@requirements-engineer** — Pre-pipeline agent that produces FRD/NFRD documents using this formatting standard. Load this skill as first step.
+**@specky-requirements-engineer** — Pre-pipeline agent that produces FRD/NFRD documents using this formatting standard. Load this skill as first step.

package/.apm/skills/{sdd-pipeline → specky-sdd-pipeline}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: sdd-pipeline
+name: specky-sdd-pipeline
 description: "This skill should be used when the user asks about 'spec-driven development', 'SDD pipeline', 'specky', 'pipeline phases', 'EARS notation', 'requirements engineering', 'model routing', or needs guidance on the 10-phase SDD workflow (Init → Discover → Specify → Clarify → Design → Tasks → Analyze → Implement → Verify → Release). Also trigger on 'spec this', 'plan this feature', 'break into tasks', 'quality gate', 'constitution', or 'spec sync'."
 ---
 
@@ -29,27 +29,20 @@ The SDD pipeline consists of 10 sequential phases designed to transform feature
 
 **Phase 9: Release** — Release gate execution, documentation generation, PR creation, work item export, and changelog preparation.
 
-## EARS Notation (Extended Requirements)
+## EARS Notation (Canonical 6 Patterns)
 
-EARS (Easy Approach to Requirements Syntax) provides five core patterns plus a complex pattern for unambiguous requirement capture:
+EARS (Easy Approach to Requirements Syntax) uses six requirement patterns. Should/May express priority or obligation level inside a requirement; they are not separate Specky EARS patterns.
 
-1. **Shall** — Mandatory requirements. Format: "The system shall [action]."
-   - Example: "The system shall validate email format before submission."
+| Pattern | Format |
+|---------|--------|
+| Ubiquitous | The system shall... |
+| Event-driven | When [event], the system shall... |
+| State-driven | While [state], the system shall... |
+| Optional | Where [condition], the system shall... |
+| Unwanted | If [condition], then the system shall... |
+| Complex | While [state], when [event], the system shall... |
 
-2. **Should** — Desired but not mandatory. Format: "The system should [action]."
-   - Example: "The system should display results within 2 seconds."
-
-3. **May** — Optional enhancements. Format: "The system may [action]."
-   - Example: "The system may support bulk import operations."
-
-4. **If...Then...** — Conditional requirements. Format: "If [condition] then [action]."
-   - Example: "If user is admin then system shall grant access to configuration panel."
-
-5. **When...Then...** — Trigger-based requirements. Format: "When [event] then [action]."
-   - Example: "When form is submitted then system shall validate all required fields."
-
-6. **Complex** — Combination patterns for intricate business logic.
-   - Example: "If user role is editor, when publish button is clicked, then system shall validate content and if valid shall queue for approval."
+See `references/ears-notation.md` for examples and validation guidance.
 
 ## Model Recommendation Table
 
@@ -79,22 +72,22 @@ For Phase 7 (Implementation), prioritize fast feedback loops over long reasoning
 The pipeline includes 16 automation hooks for customization:
 
 **Blocking Hooks** (workflow stops if hook fails — exit code 2):
-1. `artifact-validator` — Pre-tool: blocks if required artifacts missing
-2. `phase-gate` — Post-tool: blocks if output artifact wasn't created
-3. `security-scan` — Pre-release: blocks if hardcoded secrets detected
-4. `release-gate` — Pre-release: blocks if gate conditions not met
+1. `specky-artifact-validator` — Pre-tool: blocks if required artifacts missing
+2. `specky-phase-gate` — Post-tool: blocks if output artifact wasn't created
+3. `specky-security-scan` — Pre-release: blocks if hardcoded secrets detected
+4. `specky-release-gate` — Pre-release: blocks if gate conditions not met
 
 **Advisory Hooks** (workflow continues; failures logged):
-1. `branch-validator` — Pre-tool: warns if wrong branch for phase
-2. `spec-sync` — Post-tool: checks spec-code drift
-3. `auto-checkpoint` — Post-tool: suggests checkpoint after artifact changes
-4. `spec-quality` — Post-spec: validates specification quality
-5. `task-tracer` — Post-tasks: traces task dependencies
-6. `ears-validator` — Post-spec: validates EARS notation patterns
-7. `lgtm-gate` — Post-spec/design/tasks: pauses for human LGTM
-8. `drift-monitor` — Post-verify/review: monitors specification drift
-9. `cognitive-debt-alert` — Post-analysis: flags cognitive debt metrics
-10. `metrics-dashboard` — Post-analysis: updates metrics dashboard
+1. `specky-branch-validator` — Pre-tool: warns if wrong branch for phase
+2. `specky-spec-sync` — Post-tool: checks spec-code drift
+3. `specky-auto-checkpoint` — Post-tool: suggests checkpoint after artifact changes
+4. `specky-spec-quality` — Post-spec: validates specification quality
+5. `specky-task-tracer` — Post-tasks: traces task dependencies
+6. `specky-ears-validator` — Post-spec: validates EARS notation patterns
+7. `specky-lgtm-gate` — Post-spec/design/tasks: pauses for human LGTM
+8. `specky-drift-monitor` — Post-verify/review: monitors specification drift
+9. `specky-cognitive-debt-alert` — Post-analysis: flags cognitive debt metrics
+10. `specky-metrics-dashboard` — Post-analysis: updates metrics dashboard
 
 Hooks are configured in `sdd-hooks.json` with PreToolUse and PostToolUse matchers.
 
@@ -127,12 +120,12 @@ Hooks are configured in `sdd-hooks.json` with PreToolUse and PostToolUse matcher
 **Agent-based:**
 ```
 @specky-orchestrator           (end-to-end pipeline coordinator)
-@sdd-init feature-name         (Phase 0 — initialize feature)
-@spec-engineer                 (Phase 2 — write SPECIFICATION.md)
-@implementer                   (Phase 7 — scaffold code + tests)
+@specky-sdd-init feature-name         (Phase 0 — initialize feature)
+@specky-spec-engineer                 (Phase 2 — write SPECIFICATION.md)
+@specky-implementer                   (Phase 7 — scaffold code + tests)
 ```
 
-See [copilot-instructions.instructions.md](../../instructions/copilot-instructions.instructions.md) for the full agent catalog.
+See the target-specific instruction rule for the full runtime entry point guidance.
 
 ## Workflow Entry Points
 
@@ -179,7 +172,7 @@ spec/003-notifs    ──→    ↑
 git checkout develop
 git pull origin develop
 git checkout -b spec/001-user-authentication
-# Run @sdd-init / /specky-greenfield
+# Run @specky-sdd-init / /specky-greenfield
 ```
 
 **After Phase 7 passes:**
@@ -195,7 +188,7 @@ git push origin develop
 git checkout stage
 git merge --no-ff develop
 git push origin stage
-# Run @release-engineer for blocking gates
+# Run @specky-release-engineer for blocking gates
 ```
 
 **Releasing to production:**
@@ -228,13 +221,13 @@ git push origin main --tags
 |-------|-------|-------------------|
 | Pre | @specky-onboarding | Fast |
 | All | @specky-orchestrator | Balanced |
-| 0 | @sdd-init | Fast |
-| 1 | @research-analyst | Balanced |
-| 2 | @spec-engineer | Reasoning-focused |
-| 3 | @sdd-clarify | Reasoning-focused |
-| 4 | @design-architect | Reasoning-focused |
-| 5 | @task-planner | Balanced |
-| 6 | @quality-reviewer | Balanced |
-| 7 | @implementer | Balanced |
-| 8 | @test-verifier | Reasoning-focused |
-| 9 | @release-engineer | Fast |
+| 0 | @specky-sdd-init | Fast |
+| 1 | @specky-research-analyst | Balanced |
+| 2 | @specky-spec-engineer | Reasoning-focused |
+| 3 | @specky-sdd-clarify | Reasoning-focused |
+| 4 | @specky-design-architect | Reasoning-focused |
+| 5 | @specky-task-planner | Balanced |
+| 6 | @specky-quality-reviewer | Balanced |
+| 7 | @specky-implementer | Balanced |
+| 8 | @specky-test-verifier | Reasoning-focused |
+| 9 | @specky-release-engineer | Fast |