@codename_inc/spectre 3.7.0 → 5.0.0

package/plugins/spectre/{commands/create_plan.md → skills/create_plan/SKILL.md}

@@ -1,6 +1,15 @@
 ---
+name: create_plan
 description: 👻 | Create implementation plan from PRD - primary agent
+user-invocable: true
 ---
+
+# create_plan
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
 # create_plan: Transform PRD into Technical Implementation Plan
 
 ## Description

package/plugins/spectre/{commands/create_tasks.md → skills/create_tasks/SKILL.md}

@@ -1,7 +1,16 @@
 ---
+name: create_tasks
 description: 👻 | Transform requirements into executable tasks - primary agent
+user-invocable: true
 ---
 
+# create_tasks
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+
 # create_tasks: Unified Task Breakdown
 
 ## Description

package/plugins/spectre/{commands/create_test_guide.md → skills/create_test_guide/SKILL.md}

@@ -1,7 +1,16 @@
 ---
+name: create_test_guide
 description: 👻 | Generate right-sized manual test guides - primary agent
+user-invocable: true
 ---
 
+# create_test_guide
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+
 # create_test_guide: Right-sized manual testing documentation
 
 ### Description

package/plugins/spectre/{commands/evaluate.md → skills/evaluate/SKILL.md}

@@ -1,7 +1,16 @@
 ---
+name: evaluate
 description: "\ud83d\udc7b | Architecture review + knowledge capture"
+user-invocable: true
 ---
 
+# evaluate
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+
 # evaluate: Review architecture and capture learnings
 
 ## Description
@@ -18,7 +27,7 @@ $ARGUMENTS
 
 This command runs two activities in parallel:
 
-1. **Architecture Review** — dispatched as a background Opus 4.6 subagent via `/spectre:architecture_review`
+1. **Architecture Review** — dispatched as a background Opus 4.6 subagent via `Skill(architecture_review)` (Claude slash route: `/spectre:architecture_review`)
 2. **Learn** — run directly by loading the `spectre-learn` skill
 
 ## Step (1/2) - Dispatch Architecture Review
@@ -35,7 +44,7 @@ This command runs two activities in parallel:
 ## Step (2/2) - Capture Learnings
 
 - **Action** — Learn: Load the spectre-learn skill and follow its workflow
-  - Load skill: `Skill(spectre-learn)`
+  - Load skill: `Skill(learn)`
   - **If** ARGUMENTS is provided: use it as the learning topic
   - **If** ARGUMENTS is empty: the skill will analyze recent conversation to identify what's worth capturing
   - Follow the full learning workflow from the skill (categorize, propose, write, register)

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

@@ -1,7 +1,16 @@
 ---
+name: execute
 description: 👻 | Adaptive Wave-Based Build -> Code_Review -> Validate Flow
+user-invocable: true
 ---
 
+# execute
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+
 # execute: Adaptive Task Execution with Quality Gates
 
 Execute tasks in parallel waves with full scope context, adapt based on learnings, code review loop, validate requirements. Outcome: complete implementation with verified quality and E2E requirement coverage.
@@ -60,7 +69,7 @@ $ARGUMENTS
 
 - **Action** — ExecutedeveviewLoop: Until no critical/high feedback:
 
-  1. **Spawn Review**: @dev subagent runs `/spectre:code_review`
+  1. **Spawn Review**: @dev subagent runs `Skill(code_review)` (Claude slash route: `/spectre:code_review`)
   2. **Analyze**: Identify critical/high items
      - **If** none → exit loop
   3. **Address**: Parallel @dev subagents fix feedback
@@ -68,12 +77,12 @@ $ARGUMENTS
 
 ## Step 3 - Validate Requirements
 
-- **Action** — SpawnValidation: @reviewer runs `/spectre:validate` with task list
+- **Action** — SpawnValidation: @reviewer runs `Skill(validate)` (Claude slash route: `/spectre:validate`) with task list
 - **Action** — AddressGaps: If high priority gaps → dispatch @dev subagents to fix
 
 ## Step 4 - Prepare for QA
 
-- **Action** — GenerateTestGuide: @dev runs `/spectre:create_test_guide`
+- **Action** — GenerateTestGuide: @dev runs `Skill(create_test_guide)` (Claude slash route: `/spectre:create_test_guide`)
   - Save to `{OUT_DIR}/test_guide.md`
 
 ## Step 5 - Report

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

@@ -1,6 +1,15 @@
 ---
+name: fix
 description: Investigate bugs & implement fixes - primary agent
+user-invocable: true
 ---
+
+# fix
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
 # fix: Analyze bug and recommend fix
 
 ## Description

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

@@ -1,7 +1,16 @@
 ---
+name: forget
 description: Clear session memory - archive all session files so next session starts fresh
+user-invocable: true
 ---
 
+# forget
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+
 # forget: Clear Session Memory
 
 ## Description

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

@@ -1,6 +1,7 @@
 ---
-name: spectre-guide
+name: 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
 ---
 
 # SPECTRE Guide
@@ -93,7 +94,7 @@ This is how the creator of SPECTRE uses it daily:
 ### Building a Feature (the main loop)
 
 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_spec` first for user flows and components
+   - If UX is unclear: run `/spectre:ux` first for user flows and components
 
 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
@@ -146,7 +147,7 @@ Brain dump context, walk away, review the PR. Zero confirmation gates — scope,
 | `/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_spec` | UI-heavy features that need screen layouts, user flows, component states |
+| `/spectre:ux` | UI-heavy features that need screen layouts, user flows, component states |
 
 ### Phase: Plan — Research & Task Breakdown
 
@@ -212,7 +213,7 @@ Brain dump context, walk away, review the PR. Zero confirmation gates — scope,
 -> `/spectre:scope` (always start here unless it's trivial)
 
 **Feature has complex UI?**
--> `/spectre:ux_spec` after scope, before plan
+-> `/spectre:ux` after scope, before plan
 
 **High ambiguity / new project?**
 -> `/spectre:kickoff` (includes web research)
@@ -282,7 +283,7 @@ SPECTRE generates these documents in `docs/tasks/{branch_name}/`:
 | Document | Generated By | Purpose |
 |----------|-------------|---------|
 | `concepts/scope.md` | `/spectre:scope` | What's IN and OUT |
-| `specs/ux.md` | `/spectre:ux_spec` | User flows, components, interactions |
+| `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 |

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

@@ -1,7 +1,16 @@
 ---
+name: handoff
 description: Save state snapshot to session_logs for session resume
+user-invocable: true
 ---
 
+# handoff
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+
 # handoff: Fast Session State Snapshot
 
 Generate progress update, gather context, output structured JSON for session resume. Output: `{timestamp}_handoff.json` in session_logs.

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

@@ -1,7 +1,16 @@
 ---
+name: kickoff
 description: 👻 | Project kickoff with deep research & MVP pathfinding - primary agent
+user-invocable: true
 ---
 
+# kickoff
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+
 # kickoff: Deep Codebase Research + MVP Path Discovery
 
 Comprehensive codebase research, external best practices, and MVP implementation path with file:line evidence. Output: kickoff document with architecture insights, gap analysis, and implementation options saved to `docs/tasks/{task_name}/kickoff/`.

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

@@ -1,6 +1,7 @@
 ---
-name: spectre-learn
+name: 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
 ---
 
 # Learning Agent
@@ -10,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`, `/spectre:learn`, or `Skill(spectre-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(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
@@ -128,6 +129,8 @@ Format: `{skill-name}|{category}|{triggers}|{description}` (one learning per lin
 
 Example: `feature-spectre-plugin|feature|spectre, /learn, /recall|Use when modifying spectre plugin or debugging hooks`
 
+Triggers are also embedded in each skill's frontmatter `description` field as a `TRIGGER when:` line. This makes triggers visible in the session skill list without needing to read the registry file. The `register_learning.cjs` script handles this automatically during registration.
+
 ## Workflow
 
 ### 1. Parse Input
@@ -513,8 +516,8 @@ Always show FULL proposed content, not summaries. The user needs to see exactly
 ```markdown
 ---
 name: {skill-name}
-description: Use when {triggering conditions - MUST start with "Use when"}
-user-invocable: false
+description: Use when {triggering conditions - MUST start with "Use when"} TRIGGER when: {comma-separated trigger keywords}
+user-invocable: true
 ---
 
 # {Title}
@@ -553,7 +556,7 @@ user-invocable: false
 
 ### 13. Register the Learning
 
-After writing the skill file, register it in the project registry and regenerate the recall skill. This is two file operations — no external scripts needed.
+Run `spectre-register` (on PATH via the plugin bin/ directory) to update the registry, regenerate the recall skill, and inject `TRIGGER when:` into all skill frontmatter descriptions.
 
 <CRITICAL>
 **Registry description format:**
@@ -570,62 +573,19 @@ The description is used to MATCH knowledge to tasks. It must describe WHEN to us
 **Bad**: `"Authentication system overview"` (too vague, no triggering conditions)
 </CRITICAL>
 
-#### 13a. Update the Registry
-
-**Path**: `{{project_root}}/.claude/skills/spectre-recall/references/registry.toon`
-
-Create the directory and file if they don't exist. The registry format is one entry per line:
-
+```bash
+spectre-register \
+  --project-root "{{project_root}}" \
+  --skill-name "{skill-name}" \
+  --category "{category}" \
+  --triggers "{triggers}" \
+  --description "{description}"
 ```
-# SPECTRE Knowledge Registry
-# Format: skill-name|category|triggers|description
-
-{skill-name}|{category}|{triggers}|{description}
-```
-
-- If the skill-name already exists on a line, **replace** that line with the updated entry
-- If it's new, **append** the entry
-- Preserve existing entries and comments
-
-#### 13b. Regenerate the Recall Skill
-
-**Path**: `{{project_root}}/.claude/skills/spectre-recall/SKILL.md`
-
-Read the full registry content from `registry.toon`, then write the recall skill with this exact structure:
-
-```markdown
----
-name: spectre-recall
-description: Use when user wants to search for existing knowledge, recall a specific learning, or discover what knowledge is available.
----
 
-# Recall Knowledge
-
-Search and load relevant knowledge from the project's spectre learnings into your context.
-
-## Registry
-
-{full registry content here}
-
-## How to Use
-
-1. **Scan registry above** — match triggers/description against your current task
-2. **Load matching skills**: `Skill({skill-name})`
-3. **Apply knowledge** — use it to guide your approach
-
-## Search Commands
-
-- `/recall {query}` — search registry for matches
-- `/recall` — show all available knowledge by category
-
-## Workflow
-
-**Single match** → Load automatically via `Skill({skill-name})`
-
-**Multiple matches** → List options, ask user which to load
-
-**No matches** → Suggest `/learn` to capture new knowledge
-```
+This single command handles:
+- Creating/updating the registry entry in `registry.toon`
+- Regenerating the `spectre-recall/SKILL.md` skill
+- Injecting `TRIGGER when:` lines into ALL registered skills' frontmatter descriptions (so triggers are visible in the session skill list without reading the registry)
 
 ### 14. Confirm
 

package/plugins/spectre/skills/learn/references/recall-template.md

@@ -0,0 +1,34 @@
+---
+name: spectre-recall
+description: Use when user wants to search for existing knowledge, recall a specific learning, or discover what knowledge is available.
+user-invocable: false
+---
+
+# Recall Knowledge
+
+Search and load relevant knowledge from the project's spectre learnings into your context.
+
+## Registry
+
+{{REGISTRY}}
+
+## How to Use
+
+1. **Scan available skills** in your context — trigger keywords are visible in each skill's description
+2. **Load matching skills**: `Skill({skill-name})`
+3. **Apply knowledge** — use it to guide your approach
+
+The registry above is a fallback reference. For session-start discovery, triggers are embedded in each skill's frontmatter description.
+
+## Search Commands
+
+- `/recall {query}` — search registry for matches
+- `/recall` — show all available knowledge by category
+
+## Workflow
+
+**Single match** → Load automatically via `Skill({skill-name})`
+
+**Multiple matches** → List options, ask user which to load
+
+**No matches** → Suggest `/learn` to capture new knowledge

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

@@ -1,6 +1,15 @@
 ---
+name: plan
 description: 👻 | Unified planning entry point - researches, assesses complexity, routes to workflow - primary agent
+user-invocable: true
 ---
+
+# plan
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
 # plan: Intelligent Planning Router
 
 ## Description
@@ -14,7 +23,7 @@ description: 👻 | Unified planning entry point - researches, assesses complexi
 
 ## MANDATORY COMPLIANCE RULES
 
-> **⚠️ NON-NEGOTIABLE**: This workflow MUST invoke slash commands via the Skill tool. Failure to invoke `/spectre:create_plan` and `/spectre:create_tasks` is a critical error. Do NOT summarize, describe, or skip these commands. INVOKE THEM.
+> **⚠️ NON-NEGOTIABLE**: This workflow MUST invoke nested workflows via the Skill tool. Failure to invoke `Skill(create_plan)` and `Skill(create_tasks)` (Claude slash route: `/spectre:create_plan` and `/spectre:create_tasks`) is a critical error. Do NOT summarize, describe, or skip these workflows. INVOKE THEM.
 
 **After ANY user conversation or questions:**
 
@@ -24,8 +33,8 @@ description: 👻 | Unified planning entry point - researches, assesses complexi
 
 **You MUST call these skills (not describe them):**
 
-- Use the **Skill** tool with `skill: "spectre:create_plan"` and `args: "{path} --depth {tier}"` — generates plan.md
-- Use the **Skill** tool with `skill: "spectre:create_tasks"` and `args: "{path}"` — generates tasks.md
+- Use the **Skill** tool with `skill: "spectre-create_plan"` and `args: "{path} --depth {tier}"` — generates plan.md
+- Use the **Skill** tool with `skill: "spectre-create_tasks"` and `args: "{path}"` — generates tasks.md
 
 ## Instructions
 
@@ -71,16 +80,7 @@ description: 👻 | Unified planning entry point - researches, assesses complexi
 
 - **Action** — SaveResearch: Merge all findings (existing artifacts + new agent results) into `{OUT_DIR}/task_context.md` with sections: Architecture Patterns, Dependencies, Implementation Approaches, Impact Summary, and External Research (best practices, recommended libraries/frameworks, prior art, common pitfalls)
 
-## Step 2 - Present Architectural Options
-
-- **Action** — PresentOptions: 2-4 strategies (simplest to most robust)
-  - Each: core approach, trade-offs, when it makes sense
-- **Wait** — User selects strategy
-- **Action** — UpdateContext: Document selection in task_context.md
-
-> **CHECKPOINT**: After architecture discussion, proceed IMMEDIATELY to Step 3. Do NOT end turn without continuing the workflow.
-
-## Step 3 - Assess Complexity
+## Step 2 - Assess Complexity
 
 Use research findings from Step 1 to determine appropriate planning depth.
 
@@ -103,9 +103,50 @@ Use research findings from Step 1 to determine appropriate planning depth.
   - **STANDARD**: Mix of Low/Med signals, multi-file but contained scope, no hard-stops
   - **COMPREHENSIVE**: Any High signal, multiple Med signals, or any hard-stop triggered
 
-- **Action** — LogTier: Note the assessed tier in your response for transparency, then proceed immediately to Step 4. Do NOT ask for confirmation.
+- **Action** — LogTier: Note the assessed tier in your response for transparency, then proceed immediately to the next step. Do NOT ask for confirmation.
+
+> **CHECKPOINT**: After determining tier, proceed IMMEDIATELY to the next step — Step 3 (High-Level Design) for STANDARD/COMPREHENSIVE, or Step 4 (Route) for LIGHT. Do NOT end turn here. Do NOT ask user to confirm the tier.
+
+## Step 3 - High-Level Design
+
+**SKIP IF LIGHT** — proceed directly to Step 4.
+
+Goal: align on the *shape* of the solution before generating a full plan. This catches misalignments early and gives the user a chance to redirect before reading a long plan doc.
+
+- **Action** — PresentDesign: Synthesize research from Step 1 into a single proposed approach with open questions. Present inline (do not write a separate design file).
+
+  **Format**:
+
+  > Here's the high-level design I'd take. Scan the shape, then resolve any open questions or push back on the approach.
+  >
+  > **Approach**: [1-2 paragraph summary of the solution shape — what changes structurally, not file-by-file]
+  >
+  > **Key components touched**:
+  > - `path/file.ts` — [what shifts and why]
+  > - `path/other.ts` — [what shifts and why]
+  >
+  > **Key decisions**:
+  > - [decision] — [rationale; alternative considered]
+  > - [decision] — [rationale; alternative considered]
+  >
+  > **Open questions** (with default assumption):
+  > 1. [question] — *default: [assumption]*
+  > 2. [question] — *default: [assumption]*
+  >
+  > Reply with answers, edits to the approach, or 'looks good' to continue.
+
+  **CRITICAL**:
+  - **Single proposed approach**, not a menu. If a true fork exists, surface it as an open question with your recommendation — not as parallel options.
+  - Stay at the *shape* level: components, key decisions, structural changes. Defer file-by-file detail to `create_plan`.
+  - Open questions should be specific and answerable; pair each with a default assumption so the user can skip if the default is fine.
+
+- **Action** — IterateDesign: If the user replies with answers, edits, or pushback, update the design and re-present. Loop until user says 'looks good' (or equivalent).
+
+- **Wait** — User signals alignment.
+
+- **Action** — PersistDesign: Append a "Selected Design" section to `{OUT_DIR}/task_context.md` capturing the agreed approach, key decisions, and resolved questions. This is what `create_plan` consumes.
 
-> **CHECKPOINT**: After determining tier, proceed IMMEDIATELY to Step 4. The ONLY valid next action is invoking a Skill. Do NOT end turn here. Do NOT ask user to confirm the tier.
+> **CHECKPOINT**: After alignment, proceed IMMEDIATELY to Step 4. The ONLY valid next action is invoking a Skill.
 
 ## Step 4 - Route to Workflow
 
@@ -119,8 +160,8 @@ Use research findings from Step 1 to determine appropriate planning depth.
 │  ❌ 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: "..." │
-│  ✅ CORRECT: Skill tool with skill: "spectre:create_tasks", args: "..."│
+│  ✅ CORRECT: Skill tool with skill: "spectre-create_plan", args: "..." │
+│  ✅ CORRECT: Skill tool with skill: "spectre-create_tasks", args: "..."│
 └────────────────────────────────────────────────────────────────────────┘
 ```
 
@@ -134,8 +175,8 @@ Use research findings from Step 1 to determine appropriate planning depth.
 
 **YOU MUST:**
 
-- Use the Skill tool: `skill: "spectre:create_plan"`, `args: "{OUT_DIR}/task_context.md --depth {tier}"`
-- Use the Skill tool: `skill: "spectre:create_tasks"`, `args: "{OUT_DIR}/task_context.md"`
+- Use the Skill tool: `skill: "spectre-create_plan"`, `args: "{OUT_DIR}/task_context.md --depth {tier}"`
+- Use the Skill tool: `skill: "spectre-create_tasks"`, `args: "{OUT_DIR}/task_context.md"`
 
 ---
 
@@ -143,28 +184,28 @@ Use research findings from Step 1 to determine appropriate planning depth.
 
 - **If LIGHT**:
 
-  - **INVOKE NOW** → Skill tool with `skill: "spectre:create_tasks"`, `args: "{OUT_DIR}/task_context.md --depth light"`
+  - **INVOKE NOW** → Skill tool with `skill: "spectre-create_tasks"`, `args: "{OUT_DIR}/task_context.md --depth light"`
   - **Wait** — Returns task breakdown with brief implementation approach
   - Skip to footer
 
 - **ElseIf STANDARD**:
 
-  - **INVOKE NOW** → Skill tool with `skill: "spectre:create_plan"`, `args: "{OUT_DIR}/task_context.md --depth standard"`
+  - **INVOKE NOW** → Skill tool with `skill: "spectre-create_plan"`, `args: "{OUT_DIR}/task_context.md --depth standard"`
   - **Wait** — Returns focused plan (Overview, Approach, Out of Scope)
   - **Action** — PromptUser: "Review plan. Reply 'Approved' or provide feedback."
   - **Wait** — User approval
-  - **INVOKE NOW** → Skill tool with `skill: "spectre:create_tasks"`, `args: "{OUT_DIR}/task_context.md"`
+  - **INVOKE NOW** → Skill tool with `skill: "spectre-create_tasks"`, `args: "{OUT_DIR}/task_context.md"`
   - **Wait** — Returns task breakdown
 
 - **ElseIf COMPREHENSIVE**:
 
-  - **INVOKE NOW** → Skill tool with `skill: "spectre:create_plan"`, `args: "{OUT_DIR}/task_context.md --depth comprehensive"`
+  - **INVOKE NOW** → Skill tool with `skill: "spectre-create_plan"`, `args: "{OUT_DIR}/task_context.md --depth comprehensive"`
   - **Wait** — Returns full plan (all sections: Architecture, Phases, API Design, Testing Strategy, etc.)
   - **Action** — PromptUser: "Review plan. Reply 'Approved' or provide feedback."
   - **Wait** — User approval
-  - **INVOKE NOW** → Skill tool with `skill: "spectre:create_tasks"`, `args: "{OUT_DIR}/task_context.md"`
+  - **INVOKE NOW** → Skill tool with `skill: "spectre-create_tasks"`, `args: "{OUT_DIR}/task_context.md"`
   - **Wait** — Returns task breakdown
 
 ---
 
-- **Action** — RenderFooter: Use `@skill-spectre:spectre-guide` skill for Next Steps
+- **Action** — RenderFooter: Use `@skill-spectre:spectre-guide` skill for Next Steps

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

@@ -1,7 +1,16 @@
 ---
+name: plan_review
 description: 👻 | Find simplifications in a plan or tasks
+user-invocable: true
 ---
 
+# plan_review
+
+## Input Handling
+
+Treat the current command arguments as this workflow's input. When invoked from a slash command, use the forwarded `$ARGUMENTS` value.
+
+
 You are a senior staff engineer with deep expertise in system design, architecture, and pragmatic problem-solving. Your specialty is finding the simplest path to meet all requirements.
 
 Review the following [plan/document/tasks/context] and identify opportunities to simplify while ensuring all requirements and functionality are delivered.