@codename_inc/spectre 5.2.2 → 5.3.0

package/plugins/spectre-codex/skills/{execute → spectre-execute}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "execute"
+name: "spectre-execute"
 description: "👻 | Adaptive Wave-Based Build with Per-Wave Verification Gate"
 user-invocable: true
 ---
@@ -118,7 +118,7 @@ $ARGUMENTS
 
 ## Step 2 - Cross-Wave Validate
 
-- **Action** — SpawnValidation: @analyst runs `Skill(validate)` (Claude slash route: `validate`) with **narrowed scope**:
+- **Action** — SpawnValidation: @analyst runs `Skill(spectre-validate)` (Claude slash route: `spectre-validate`) with **narrowed scope**:
   - Focus: cross-wave integration audit (did later waves silently break earlier waves' wiring?) + scope-creep audit (anything implemented that is NOT in the acceptance criteria?) + dead-computation sweep across the full cumulative diff
   - Skip: per-area wiring verification (already done per-wave in Step 1.3b's wiring lens)
 
@@ -126,7 +126,7 @@ $ARGUMENTS
 
 ## Step 3 - Prepare for QA
 
-- **Action** — GenerateTestGuide: @dev runs `Skill(create_test_guide)` (Claude slash route: `create_test_guide`)
+- **Action** — GenerateTestGuide: @dev runs `Skill(spectre-create_test_guide)` (Claude slash route: `spectre-create_test_guide`)
   - Save to `{OUT_DIR}/test_guide.md`
 
 ## Step 4 - Report

package/plugins/spectre-codex/skills/{fix → spectre-fix}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "fix"
+name: "spectre-fix"
 description: "Investigate bugs & implement fixes - primary agent"
 user-invocable: true
 ---

package/plugins/spectre-codex/skills/{forget → spectre-forget}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "forget"
+name: "spectre-forget"
 description: "Clear session memory - archive all session files so next session starts fresh"
 user-invocable: true
 ---

package/plugins/spectre-codex/skills/{guide → spectre-guide}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "guide"
+name: "spectre-guide"
 description: "Use when rendering the Next Steps footer after any spectre command, suggesting next actions, or when users need guidance on which SPECTRE command to run."
 user-invocable: false
 ---
@@ -53,7 +53,7 @@ AI agents are 10x better at working around *working* existing code. That's why t
 ### Your First Feature
 
 ```plaintext
-scope
+spectre-scope
 ```
 
 That's it. Start with scope, follow the prompts, and SPECTRE will guide you through the rest. Every command ends with "Next Steps" suggestions — you never have to remember what to run next.
@@ -63,9 +63,9 @@ That's it. Start with scope, follow the prompts, and SPECTRE will guide you thro
 SPECTRE accumulates context across sessions:
 
 1. Turn off auto-compact in Claude Code `/config`
-2. Run `handoff` before session ends or when context window is getting full
+2. Run `spectre-handoff` before session ends or when context window is getting full
 3. Run `/clear` — next session auto-loads your progress
-4. `forget` when switching gears to start fresh
+4. `spectre-forget` when switching gears to start fresh
 
 ---
 
@@ -75,13 +75,13 @@ SPECTRE accumulates context across sessions:
 
 | Phase | Command | What It Does |
 |-------|---------|--------------|
-| **S**cope | `scope` | Define requirements, constraints, what's IN and OUT |
-| **P**lan | `plan` | Research codebase, create implementation plan + tasks |
-| **E**xecute | `execute` | Parallel subagent development in waves |
-| **C**lean | `clean` | Remove dead code, fix duplication, lint |
-| **T**est | `test` | Risk-aware test coverage (not brute-force 100%) |
-| **R**ebase | `rebase` | Safe merge preparation with conflict handling |
-| **E**valuate | `evaluate` | Architecture review + knowledge capture |
+| **S**cope | `spectre-scope` | Define requirements, constraints, what's IN and OUT |
+| **P**lan | `spectre-plan` | Research codebase, create implementation plan + tasks |
+| **E**xecute | `spectre-execute` | Parallel subagent development in waves |
+| **C**lean | `spectre-clean` | Remove dead code, fix duplication, lint |
+| **T**est | `spectre-test` | Risk-aware test coverage (not brute-force 100%) |
+| **R**ebase | `spectre-rebase` | Safe merge preparation with conflict handling |
+| **E**valuate | `spectre-evaluate` | Architecture review + knowledge capture |
 
 You can use any command standalone — they don't require running in order.
 
@@ -93,30 +93,30 @@ This is how the creator of SPECTRE uses it daily:
 
 ### Building a Feature (the main loop)
 
-1. **`scope`** — Get crisp on what's in/out. Non-negotiable unless it's a one-liner.
-   - If UX is unclear: run `ux` first for user flows and components
+1. **`spectre-scope`** — Get crisp on what's in/out. Non-negotiable unless it's a one-liner.
+   - If UX is unclear: run `spectre-ux` first for user flows and components
 
-2. **`plan`** — Build a well-researched technical design or task set
-   - Once you have scope/plan/tasks, run `handoff` for a fresh context window
+2. **`spectre-plan`** — Build a well-researched technical design or task set
+   - Once you have scope/plan/tasks, run `spectre-handoff` for a fresh context window
 
-3. **`execute`** — Parallel subagents work through the tasks
+3. **`spectre-execute`** — Parallel subagents work through the tasks
    - Execute also calls code review and validation automatically
-   - When done, run `handoff` again for clean context
+   - When done, run `spectre-handoff` again for clean context
 
 4. **Manual testing + fixes** — Test the feature yourself
    - Use Claude Code's built-in `/plan` mode for small fixes
-   - Use `fix` for structured debugging of tough bugs
-   - New scope needed? Run another `scope` cycle
-   - Use `handoff` liberally to keep context clean
+   - Use `spectre-fix` for structured debugging of tough bugs
+   - New scope needed? Run another `spectre-scope` cycle
+   - Use `spectre-handoff` liberally to keep context clean
 
-5. **`sweep`** — Commit accumulated changes with lint + test
+5. **`spectre-sweep`** — Commit accumulated changes with lint + test
    - Groups changes logically with descriptive conventional commits
 
-6. **`clean`** then **`test`** — Deep cleanup and risk-aware testing
+6. **`spectre-clean`** then **`spectre-test`** — Deep cleanup and risk-aware testing
 
-7. **`rebase`** — Rebase onto parent branch, prepare for merge
+7. **`spectre-rebase`** — Rebase onto parent branch, prepare for merge
 
-8. **`evaluate`** — Architecture review + capture knowledge for future sessions
+8. **`spectre-evaluate`** — Architecture review + capture knowledge for future sessions
 
 9. **Merge/PR** — Address PR comments, get it checked in
 
@@ -124,7 +124,7 @@ This is how the creator of SPECTRE uses it daily:
 
 For small/medium changes (1-5 tasks):
 ```plaintext
-quick_dev
+spectre-quick_dev
 ```
 Lightweight scope + plan that gets you to execution fast.
 
@@ -132,7 +132,7 @@ Lightweight scope + plan that gets you to execution fast.
 
 For low-complexity features/fixes where you trust the agent:
 ```plaintext
-ship
+spectre-ship
 ```
 Brain dump context, walk away, review the PR. Zero confirmation gates — scope, TDD, sweep, rebase, and PR creation happen autonomously.
 
@@ -144,118 +144,118 @@ Brain dump context, walk away, review the PR. Zero confirmation gates — scope,
 
 | Command | When to Use |
 |---------|-------------|
-| `scope` | Starting any new feature — interactive scoping with IN/OUT boundaries |
-| `kickoff` | High-ambiguity projects — includes web research for best practices |
-| `research` | Need deep codebase understanding before planning |
-| `ux` | UI-heavy features that need screen layouts, user flows, component states |
+| `spectre-scope` | Starting any new feature — interactive scoping with IN/OUT boundaries |
+| `spectre-kickoff` | High-ambiguity projects — includes web research for best practices |
+| `spectre-research` | Need deep codebase understanding before planning |
+| `spectre-ux` | UI-heavy features that need screen layouts, user flows, component states |
 
 ### Phase: Plan — Research & Task Breakdown
 
 | Command | When to Use |
 |---------|-------------|
-| `plan` | Unified entry — researches, assesses complexity, routes to right workflow |
-| `create_plan` | Complex work needing architectural design before tasking |
-| `create_tasks` | Requirements/plan ready to become concrete tasks |
-| `plan_review` | Sanity check a plan/task list for over-engineering |
+| `spectre-plan` | Unified entry — researches, assesses complexity, routes to right workflow |
+| `spectre-create_plan` | Complex work needing architectural design before tasking |
+| `spectre-create_tasks` | Requirements/plan ready to become concrete tasks |
+| `spectre-plan_review` | Sanity check a plan/task list for over-engineering |
 
 ### Phase: Execute — Development & Verification
 
 | Command | When to Use |
 |---------|-------------|
-| `execute` | Tasks exist, ready for coordinated multi-agent parallel execution |
-| `code_review` | Implementation complete, ready for in-depth review |
-| `validate` | Verify implementation against original scope requirement-by-requirement |
-| `create_test_guide` | Generate manual QA checklist based on features and risks |
+| `spectre-execute` | Tasks exist, ready for coordinated multi-agent parallel execution |
+| `spectre-code_review` | Implementation complete, ready for in-depth review |
+| `spectre-validate` | Verify implementation against original scope requirement-by-requirement |
+| `spectre-create_test_guide` | Generate manual QA checklist based on features and risks |
 
 ### Phase: Clean — Codebase Hygiene
 
 | Command | When to Use |
 |---------|-------------|
-| `clean` | Deep cleanup — dead code, duplication, artifacts |
-| `sweep` | Light pass — lint, test, descriptive commits for accumulated changes |
+| `spectre-clean` | Deep cleanup — dead code, duplication, artifacts |
+| `spectre-sweep` | Light pass — lint, test, descriptive commits for accumulated changes |
 
 ### Phase: Test — Risk-Aware Coverage
 
 | Command | When to Use |
 |---------|-------------|
-| `test` | After changes — analyzes risk tiers (P0-P3), writes behavioral tests |
+| `spectre-test` | After changes — analyzes risk tiers (P0-P3), writes behavioral tests |
 
 ### Phase: Rebase — Merge Preparation
 
 | Command | When to Use |
 |---------|-------------|
-| `rebase` | Rebase working branch onto target with conflict handling |
+| `spectre-rebase` | Rebase working branch onto target with conflict handling |
 
 ### Phase: Evaluate — Review & Learn
 
 | Command | When to Use |
 |---------|-------------|
-| `evaluate` | Full evaluate — architecture review (background) + knowledge capture |
-| `learn` | Just capture knowledge from this session |
-| `architecture_review` | Just run the architecture review |
-| `recall {query}` | Find and load existing knowledge |
+| `spectre-evaluate` | Full evaluate — architecture review (background) + knowledge capture |
+| `spectre-learn` | Just capture knowledge from this session |
+| `spectre-architecture_review` | Just run the architecture review |
+| `spectre-recall {query}` | Find and load existing knowledge |
 
 ### Session & Utilities
 
 | Command | When to Use |
 |---------|-------------|
-| `handoff` | Save session state — end of session, context full, switching gears |
-| `forget` | Clear memory, archive logs, start fresh |
-| `fix` | Structured debugging for tough bugs |
-| `quick_dev` | Lightweight scope + plan for small/medium tasks |
-| `ship` | Autonomous end-to-end: brain dump → scope → TDD → commit → rebase → PR |
+| `spectre-handoff` | Save session state — end of session, context full, switching gears |
+| `spectre-forget` | Clear memory, archive logs, start fresh |
+| `spectre-fix` | Structured debugging for tough bugs |
+| `spectre-quick_dev` | Lightweight scope + plan for small/medium tasks |
+| `spectre-ship` | Autonomous end-to-end: brain dump → scope → TDD → commit → rebase → PR |
 
 ---
 
 ## Quick Decision Tree
 
 **Starting a feature?**
--> `scope` (always start here unless it's trivial)
+-> `spectre-scope` (always start here unless it's trivial)
 
 **Feature has complex UI?**
--> `ux` after scope, before plan
+-> `spectre-ux` after scope, before plan
 
 **High ambiguity / new project?**
--> `kickoff` (includes web research)
+-> `spectre-kickoff` (includes web research)
 
 **Need to understand code first?**
--> `research`
+-> `spectre-research`
 
 **Have scope, need plan?**
--> `plan` (auto-routes based on complexity)
+-> `spectre-plan` (auto-routes based on complexity)
 
 **Have tasks, ready to build?**
--> `execute`
+-> `spectre-execute`
 
 **Code complete, need review?**
--> `code_review` then `validate`
+-> `spectre-code_review` then `spectre-validate`
 
 **Accumulated uncommitted changes?**
--> `sweep` (light) or `clean` (deep)
+-> `spectre-sweep` (light) or `spectre-clean` (deep)
 
 **Need test coverage?**
--> `test`
+-> `spectre-test`
 
 **Ready to merge?**
--> `rebase`
+-> `spectre-rebase`
 
 **Feature done?**
--> `evaluate` (review + learn)
+-> `spectre-evaluate` (review + learn)
 
 **Ending session?**
--> `handoff`
+-> `spectre-handoff`
 
 **Switching contexts?**
--> `forget`
+-> `spectre-forget`
 
 **Bug to fix?**
--> `fix`
+-> `spectre-fix`
 
 **Small task, skip ceremony?**
--> `quick_dev`
+-> `spectre-quick_dev`
 
 **Low-complexity task, full autonomy?**
--> `ship` (brain dump → PR, zero gates)
+-> `spectre-ship` (brain dump → PR, zero gates)
 
 ---
 
@@ -282,14 +282,14 @@ SPECTRE generates these documents in `docs/tasks/{branch_name}/`:
 
 | Document | Generated By | Purpose |
 |----------|-------------|---------|
-| `concepts/scope.md` | `scope` | What's IN and OUT |
-| `specs/ux.md` | `ux` | User flows, components, interactions |
-| `specs/plan.md` | `create_plan` | Technical design and phasing |
-| `specs/tasks.md` | `create_tasks` | Concrete tasks with acceptance criteria |
-| `reviews/code_review.md` | `code_review` | Severity-based code review findings |
-| `validation/validation_gaps.md` | `validate` | Gaps between scope and implementation |
-| `testing/*_test_guide.md` | `create_test_guide` | Manual QA checklists |
-| `session_logs/*_handoff.json` | `handoff` | Session state snapshots |
+| `concepts/scope.md` | `spectre-scope` | What's IN and OUT |
+| `specs/ux.md` | `spectre-ux` | User flows, components, interactions |
+| `specs/plan.md` | `spectre-create_plan` | Technical design and phasing |
+| `specs/tasks.md` | `spectre-create_tasks` | Concrete tasks with acceptance criteria |
+| `reviews/code_review.md` | `spectre-code_review` | Severity-based code review findings |
+| `validation/validation_gaps.md` | `spectre-validate` | Gaps between scope and implementation |
+| `testing/*_test_guide.md` | `spectre-create_test_guide` | Manual QA checklists |
+| `session_logs/*_handoff.json` | `spectre-handoff` | Session state snapshots |
 
 Keep these checked into git — they're the context in context engineering.
 
@@ -310,9 +310,9 @@ Keep these checked into git — they're the context in context engineering.
 ║ Next — {concise recommendation; 1–2 lines max}           ║
 ║                                                          ║
 ║ Options:                                                 ║
-║ - {command or action} — {why}                   ║
-║ - {command or action} — {why}                   ║
-║ - {command or action} — {why}                   ║
+║ - {spectre-command or action} — {why}                   ║
+║ - {spectre-command or action} — {why}                   ║
+║ - {spectre-command or action} — {why}                   ║
 ║   … up to 5 total; max 2 manual actions                  ║
 ║                                                          ║
 ║ Reply — {only if textual reply expected}                  ║
@@ -340,14 +340,14 @@ Keep these checked into git — they're the context in context engineering.
 
 **CRITICAL:**
 
-1. **All SPECTRE commands use `/spectre:` prefix** (e.g., `scope`, `execute`)
+1. **All SPECTRE commands use `/spectre:` prefix** (e.g., `spectre-scope`, `spectre-execute`)
 2. **Manual actions are NOT slash commands** (e.g., "Run tests", "Review PR feedback")
 3. **Never invent slash commands** — only suggest commands listed in this guide
 
 **Correct:**
 ```
-scope — Interactive feature scoping
-execute — Parallel agent execution
+spectre-scope — Interactive feature scoping
+spectre-execute — Parallel agent execution
 Run manual tests — Execute test guide checklist
 ```
 

package/plugins/spectre-codex/skills/{handoff → spectre-handoff}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "handoff"
+name: "spectre-handoff"
 description: "Save state snapshot to session_logs for session resume"
 user-invocable: true
 ---

package/plugins/spectre-codex/skills/{kickoff → spectre-kickoff}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "kickoff"
+name: "spectre-kickoff"
 description: "👻 | Project kickoff with deep research & MVP pathfinding - primary agent"
 user-invocable: true
 ---
@@ -114,11 +114,11 @@ $ARGUMENTS
   > **Established**: User problem, user value, key findings (file:line), decisions made, remaining ambiguities
   >
   > **Options**:
-  > 1. "Proceed with scope" → `scope` with FROM_KICKOFF=true, SKIP_EXPLORATION=true
-  > 2. "Skip to planning" → `plan` with kickoff doc context
-  > 3. "Need to think" → `handoff`
+  > 1. "Proceed with scope" → `spectre-scope` with FROM_KICKOFF=true, SKIP_EXPLORATION=true
+  > 2. "Skip to planning" → `spectre-plan` with kickoff doc context
+  > 3. "Need to think" → `spectre-handoff`
 
 - **Action** — ExecuteChoice:
-  - **If** scope → invoke `scope` with: FROM_KICKOFF=true, KICKOFF_DOC={path}, SKIP_EXPLORATION=true, context summary
-  - **If** planning → suggest `plan`
-  - **If** pause → run `handoff`
+  - **If** scope → invoke `spectre-scope` with: FROM_KICKOFF=true, KICKOFF_DOC={path}, SKIP_EXPLORATION=true, context summary
+  - **If** planning → suggest `spectre-plan`
+  - **If** pause → run `spectre-handoff`

package/plugins/spectre-codex/skills/{learn → spectre-learn}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "learn"
+name: "spectre-learn"
 description: "Use when user invokes /learn or wants to save patterns, decisions, gotchas, procedures, or feature knowledge from a conversation for later re-use. Look for user requests like \"please remember\" or \"what did we learn from this?\"."
 user-invocable: true
 ---
@@ -11,7 +11,7 @@ You capture durable project knowledge into Skills that Claude Code loads on-dema
 <CRITICAL>
 ## Exclusive Knowledge Handler
 
-When this skill is invoked (via `/learn`, `learn`, or `Skill(learn)`), it is the **exclusive handler** for knowledge capture. It supersedes ALL other memory systems.
+When this skill is invoked (via `/learn`, `spectre-learn`, or `Skill(spectre-learn)`), it is the **exclusive handler** for knowledge capture. It supersedes ALL other memory systems.
 
 **Do NOT**:
 - Write to `MEMORY.md` or any auto-memory directory

package/plugins/spectre-codex/skills/{plan → spectre-plan}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "plan"
+name: "spectre-plan"
 description: "👻 | Unified planning entry point - researches, assesses complexity, routes to workflow - primary agent"
 user-invocable: true
 ---
@@ -23,7 +23,7 @@ Treat the current command arguments as this workflow's input. When invoked from
 
 ## MANDATORY COMPLIANCE RULES
 
-> **⚠️ NON-NEGOTIABLE**: After tier routing, this workflow MUST invoke nested workflows via the Skill tool. LIGHT must invoke `Skill(create_plan)` and `Skill(create_tasks)`; STANDARD/COMPREHENSIVE must invoke `Skill(create_plan)`, `Skill(create_tasks)`, and `Skill(plan_review)` (Claude slash route: `create_plan`, `create_tasks`, and `plan_review`). Failure to invoke the required skills is a critical error. Do NOT summarize, describe, or skip these workflows. INVOKE THEM.
+> **⚠️ NON-NEGOTIABLE**: After tier routing, this workflow MUST invoke nested workflows via the Skill tool. LIGHT must invoke `Skill(spectre-create_plan)` and `Skill(spectre-create_tasks)`; STANDARD/COMPREHENSIVE must invoke `Skill(spectre-create_plan)`, `Skill(spectre-create_tasks)`, and `Skill(spectre-plan_review)` (Claude slash route: `spectre-create_plan`, `spectre-create_tasks`, and `spectre-plan_review`). Failure to invoke the required skills is a critical error. Do NOT summarize, describe, or skip these workflows. INVOKE THEM.
 
 **After ANY user conversation or questions:**
 
@@ -184,7 +184,7 @@ Goal: align on the *shape* of the solution before generating a full plan. This c
 │  YOU MUST USE THE SKILL TOOL TO INVOKE THESE COMMANDS                  │
 │                                                                        │
 │  ❌ WRONG: "I'll now create the plan..."                               │
-│  ❌ WRONG: "The next step would be to run create_plan"        │
+│  ❌ WRONG: "The next step would be to run spectre-create_plan"        │
 │  ❌ WRONG: Ending turn without invoking Skill tool                     │
 │                                                                        │
 │  ✅ CORRECT: Skill tool with skill: "spectre-create_plan", args: "..." │
@@ -275,7 +275,7 @@ Only proceed past this checkpoint when the user confirms.
 - **Wait** — User final approval or feedback.
 
 - **If feedback preserves canonical scope** — apply the smallest edits to `plan.md`/`tasks.md`, re-run `plan_review {OUT_DIR} --auto-apply scope-safe` if the feedback changes implementation approach, verification, dependencies, task sequencing, or references, then present the Final Gate again.
-- **If feedback changes canonical scope** — stop and route back to `scope` (or explicitly update the canonical scope artifact if the user directs it). Do not silently update plan/tasks against stale scope.
+- **If feedback changes canonical scope** — stop and route back to `spectre-scope` (or explicitly update the canonical scope artifact if the user directs it). Do not silently update plan/tasks against stale scope.
 
 ---
 

package/plugins/spectre-codex/skills/{plan_review → spectre-plan_review}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "plan_review"
+name: "spectre-plan_review"
 description: "👻 | Independent multi-lens review of plan.md and/or tasks.md — finds overengineering, missing verification, hallucinated deps, weak references"
 user-invocable: true
 ---
@@ -58,7 +58,7 @@ A single reviewer biases toward the issues it notices first. Published practice
   - `REVIEW_REPORT=${REVIEWS_DIR}/plan_review.md`; if that exists, use `plan_review_{YYYY-MM-DD_HHMMSS}.md` to avoid overwriting prior review evidence.
   - `plan.md` and `tasks.md` are independently reviewable. It is valid to review only `plan.md`, only `tasks.md`, or both.
   - `task_context.md` is helpful context but is not required. If it is missing, continue and note that requirements traceability is limited.
-  - If both `plan.md` and `tasks.md` are missing, stop and suggest the user run `plan` or `create_tasks` first.
+  - If both `plan.md` and `tasks.md` are missing, stop and suggest the user run `spectre-plan` or `spectre-create_tasks` first.
   - If exactly one of `plan.md` or `tasks.md` is missing, list it as absent context and continue. Do not decline, stop, or ask the user to create the missing artifact.
 
 - **Action** — ReadAvailable: Read each available file completely into context before dispatching reviewers. Reviewers receive curated excerpts plus an artifact manifest that says which files are present and absent. Every reviewer must review the artifacts that exist and must not treat absent artifacts as a blocker. The manifest must label the canonical scope source and state that review findings may not remove or narrow scope.
@@ -213,6 +213,6 @@ Missing-artifact rule for every lens: review what exists. If a finding depends o
 
 ## Notes
 
-- This skill does NOT generate plans or tasks. It reviews available planning artifacts. If only one of `plan.md` or `tasks.md` exists, review that artifact. Only route the user to `plan` or `create_tasks` when neither reviewable artifact exists.
+- This skill does NOT generate plans or tasks. It reviews available planning artifacts. If only one of `plan.md` or `tasks.md` exists, review that artifact. Only route the user to `spectre-plan` or `spectre-create_tasks` when neither reviewable artifact exists.
 - The four lenses are intentionally non-overlapping by design but will surface overlap in practice — dedupe at synthesis, don't ask reviewers to coordinate.
 - The "Must-Delete" nomination from Lens 1 is mandatory output — even on a tight plan, naming the single weakest element is a forcing function against under-review.

package/plugins/spectre-codex/skills/{prototype → spectre-prototype}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "prototype"
+name: "spectre-prototype"
 description: "👻 | Generate a self-contained HTML prototype to validate a feature visually before planning - primary agent"
 user-invocable: true
 ---
@@ -22,10 +22,10 @@ Produce a self-contained, clickable HTML artifact that makes a feature visible
 
 Detect mode from environment markers, ARGUMENTS, and existing docs. **Order matters** — check from most context to least:
 
-- **Complete ux.md exists** (post-ux) — full Stage 2 spec is on disk. The prototype's job is to **render the spec**, not synthesize it. Default fidelity: **high-fi**. Skip all intake except visual anchor. Treat ux.md as authoritative — don't invent screens, don't contradict documented states or copy. On completion, recommend `plan` or `create_tasks`.
+- **Complete ux.md exists** (post-ux) — full Stage 2 spec is on disk. The prototype's job is to **render the spec**, not synthesize it. Default fidelity: **high-fi**. Skip all intake except visual anchor. Treat ux.md as authoritative — don't invent screens, don't contradict documented states or copy. On completion, recommend `spectre-plan` or `spectre-create_tasks`.
 - **`FROM_UX=true`** — invoked mid-flow from `ux` Stage 1 → Stage 2 gate. Only approved flows exist (no detailed spec yet). Skip flow-discovery intake. Default fidelity: **mid-fi**. On completion, point user back to `ux` Stage 2.
-- **`--explore` flag in ARGUMENTS** — pre-scope discovery. Concept is unvalidated. Default fidelity: **low-fi**. On completion, recommend `scope` as next step.
-- **scope.md exists for this branch** (no ux.md) — post-scope validation. Default fidelity: **mid-fi**. On completion, recommend `ux` or `plan` based on feature complexity.
+- **`--explore` flag in ARGUMENTS** — pre-scope discovery. Concept is unvalidated. Default fidelity: **low-fi**. On completion, recommend `spectre-scope` as next step.
+- **scope.md exists for this branch** (no ux.md) — post-scope validation. Default fidelity: **mid-fi**. On completion, recommend `spectre-ux` or `spectre-plan` based on feature complexity.
 - **Standalone, no context** — ask the user what they're prototyping. Default fidelity: **mid-fi**.
 
 ---
@@ -50,7 +50,7 @@ Detect mode from environment markers, ARGUMENTS, and existing docs. **Order matt
   - Read whichever exist FULLY (no offset/limit)
 
 - **Action** — ClassifyUxDoc: If `ux.md` exists, classify its completeness — this drives fidelity AND how much intake to skip.
-  - **Complete** — contains all of: Screens, Layouts, Components, Interactions, States, Content sections (the Stage 2 deliverables from `ux`). Treat as authoritative. Skip flow-discovery questions. Set mode = **post-ux**.
+  - **Complete** — contains all of: Screens, Layouts, Components, Interactions, States, Content sections (the Stage 2 deliverables from `spectre-ux`). Treat as authoritative. Skip flow-discovery questions. Set mode = **post-ux**.
   - **Flows-only** — contains user flows / journeys but missing Stage 2 sections. Treat flows as approved input but expect to make UI decisions. Set mode = **flows-only ux**.
   - **Absent** — fall back to scope.md / prd.md / standalone modes.
 
@@ -181,7 +181,7 @@ Wait for ALL subagents to complete. Synthesize their outputs, then generate a si
      Key assumptions: {bullet list of design decisions and content assumptions}
      Filled assumptions: {only in post-ux mode — items the spec was silent on that the prototype filled in; review these against the spec}
      NOT included: {explicit list of what was deliberately left out}
-     Next step: plan  OR  resume ux Stage 2
+     Next step: spectre-plan  OR  resume spectre-ux Stage 2
    -->
    ```
 3. **Design tokens comment block** in `<head>`:
@@ -275,9 +275,9 @@ Surface any violations as caveats in the handoff. Don't silently ship a broken p
   - Re-present with a one-line diff per added item: `ux.md ← added: {item} (in {section})`.
 
 - **Action** — RenderFooter: Render Next Steps using `Skill(spectre-guide)` skill, with mode-specific recommendation:
-  - **If `FROM_UX=true`** → recommend: "Resume `ux` Stage 2 with this prototype as input"
-  - **If `--explore`** → recommend: `scope` with the prototype as anchor
-  - **If post-scope** → recommend: `ux` (if flows still need detail) or `plan` (if ready to build)
+  - **If `FROM_UX=true`** → recommend: "Resume `spectre-ux` Stage 2 with this prototype as input"
+  - **If `--explore`** → recommend: `spectre-scope` with the prototype as anchor
+  - **If post-scope** → recommend: `spectre-ux` (if flows still need detail) or `spectre-plan` (if ready to build)
   - **Else** → standard Next Steps options
 
 ---

package/plugins/spectre-codex/skills/{quick_dev → spectre-quick_dev}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "quick_dev"
+name: "spectre-quick_dev"
 description: "👻 | Quickly scope, research, & plan s/m tasks - primary agent"
 user-invocable: true
 ---
@@ -97,7 +97,7 @@ $ARGUMENTS
   - Exclude: code snippets, line-by-line steps
   - 2-3 acceptance criteria per sub-task
 
-  **Bounds**: ~3 phases, ~8 parent tasks max. If exceeds → suggest `create_tasks`
+  **Bounds**: ~3 phases, ~8 parent tasks max. If exceeds → suggest `spectre-create_tasks`
 
 - **Action** — ValidateCoverage: Verify all in-scope items have tasks; no out-of-scope tasks added
 

package/plugins/spectre-codex/skills/{rebase → spectre-rebase}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "rebase"
+name: "spectre-rebase"
 description: "👻 | Safe guided rebase w/conflict handling - primary agent"
 user-invocable: true
 ---

package/plugins/spectre-codex/skills/spectre-recall/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: "spectre-recall"
+description: "👻 | Search Project Knowledge"
+user-invocable: true
+---
+
+# recall
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+# /recall - Search Project Knowledge
+
+Read the project knowledge recall skill directly, then follow its instructions for the query below:
+
+- Claude Code path: `{{project_root}}/.agents/skills/spectre-recall/SKILL.md`
+- Codex path: `{{project_root}}/.agents/skills/spectre-recall/SKILL.md`
+
+If neither file exists, report that no project knowledge registry exists yet and suggest `spectre-learn` after the current work produces something worth preserving.
+
+**Search query**: $ARGUMENTS

package/plugins/spectre-codex/skills/{research → spectre-research}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: "research"
+name: "spectre-research"
 description: "👻 | Research codebase with parallel agents - primary agent"
 user-invocable: true
 ---