specdacular 0.9.2 → 0.10.1

package/specdacular/workflows/new.md

@@ -31,7 +31,7 @@ Keep asking until you understand:
 2. What it integrates with (existing code)
 3. Key constraints (technical, timeline, scope)
 
-You don't need to resolve everything — that's what `/specd:discuss` is for.
+You don't need to resolve everything — that's what `/specd.discuss` is for.
 
 ## Decisions Get Recorded
 
@@ -63,7 +63,7 @@ Use AskUserQuestion:
 - header: "Task Exists"
 - question: "Task '{name}' already exists. What would you like to do?"
 - options:
-  - "Resume" — Continue with existing task (suggest /specd:continue)
+  - "Resume" — Continue with existing task (suggest /specd.continue)
   - "Reset" — Delete and start fresh
   - "Different name" — Use a different name
 
@@ -150,7 +150,7 @@ Does that capture it, or should we dig into anything more?
 **When to move on:**
 - User confirms understanding is correct
 - You have enough for initial FEATURE.md
-- Further details can be discussed later with /specd:discuss
+- Further details can be discussed later with /specd.discuss
 
 Continue to write_feature.
 </step>
@@ -252,7 +252,7 @@ Use AskUserQuestion:
 - question: "Want to keep discussing the open areas, or come back later?"
 - options:
   - "Keep discussing" — Dive into the gray areas now
-  - "Stop for now" — Come back with /specd:continue {task-name}
+  - "Stop for now" — Come back with /specd.continue {task-name}
 
 **If Keep discussing:**
 Execute the discuss workflow logic:
@@ -266,7 +266,7 @@ Use AskUserQuestion:
 - question: "Discussion looks solid. Want to keep going or come back later?"
 - options:
   - "Continue" — Move to the next step (research or planning)
-  - "Stop for now" — Come back with /specd:continue {task-name}
+  - "Stop for now" — Come back with /specd.continue {task-name}
 
 **If Continue:**
 Hand off to continue workflow:
@@ -278,7 +278,7 @@ Hand off to continue workflow:
 
 Progress saved. Pick up where you left off anytime:
 
-/specd:continue {task-name}
+/specd.continue {task-name}
 ```
 
 End workflow.

package/specdacular/workflows/orchestrator/new.md

@@ -234,7 +234,7 @@ Use AskUserQuestion:
 - question: "Want to keep discussing the open areas, or come back later?"
 - options:
   - "Keep discussing" — Dive into the gray areas now
-  - "Stop for now" — Come back with `/specd:continue {task-name}`
+  - "Stop for now" — Come back with `/specd.continue {task-name}`
 
 **If Keep discussing:**
 Execute the discuss workflow:
@@ -248,7 +248,7 @@ Use AskUserQuestion:
 - question: "Discussion looks solid. Want to keep going or come back later?"
 - options:
   - "Continue" — Move to next step
-  - "Stop for now" — Come back with `/specd:continue {task-name}`
+  - "Stop for now" — Come back with `/specd.continue {task-name}`
 
 **If Continue:**
 Hand off to continue workflow:
@@ -258,7 +258,7 @@ Hand off to continue workflow:
 ```
 Progress saved. Pick up where you left off anytime:
 
-/specd:continue {task-name}
+/specd.continue {task-name}
 ```
 
 End workflow.

package/specdacular/workflows/orchestrator/plan.md

@@ -162,7 +162,7 @@ Present multi-project roadmap summary.
 
 ## What's Next
 
-/specd:continue {task-name} — Start executing phases
+/specd.continue {task-name} — Start executing phases
 ```
 
 End workflow.

package/specdacular/workflows/plan.md

@@ -63,15 +63,15 @@ Missing:
 - {what's missing}
 
 Recommended next:
-- /specd:discuss {task-name} — Resolve gray areas
-- /specd:research {task-name} — Research implementation patterns
+- /specd.discuss {task-name} — Resolve gray areas
+- /specd.research {task-name} — Research implementation patterns
 ```
 End workflow.
 
 **If ready but RESEARCH.md missing:**
 ```
 Note: No research findings available. Plans will be based on discussion context only.
-Consider running /specd:research {task-name} first for better plans.
+Consider running /specd.research {task-name} first for better plans.
 ```
 
 Continue to derive_phases.

package/specdacular/workflows/status.md

@@ -37,7 +37,7 @@ Also check sub-project features — scan each project path for `{project-path}/.
 **If no features found anywhere:** output the following and stop:
 
 ```
-No tasks found. Start one with `/specd:new [name]`.
+No tasks found. Start one with `/specd.new [name]`.
 ```
 
 ### 4. Gather feature data
@@ -119,7 +119,7 @@ _{total} features, {in_progress} in progress_
 **If `--all` flag is NOT set and there are completed tasks:**
 
 ```
-Run `/specd:status --all` to include completed tasks.
+Run `/specd.status --all` to include completed tasks.
 ```
 
 **If `--all` flag IS set and there are completed tasks, add:**
@@ -190,7 +190,7 @@ Only show active standalone features (not complete/abandoned, unless `--all`).
 **If `--all` flag is NOT set and there are completed/abandoned features (root or sub-project):**
 
 ```
-Run `/specd:status --all` to include completed tasks.
+Run `/specd.status --all` to include completed tasks.
 ```
 
 **If `--all` flag IS set and there are completed/abandoned features, add:**

package/commands/specd/toolbox.md

@@ -1,103 +0,0 @@
----
-name: specd:toolbox
-description: "Advanced task operations and context management"
-argument-hint: "[tasks <task-name>|context]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Task
-  - AskUserQuestion
-  - WebSearch
-  - WebFetch
----
-
-<objective>
-Toolbox with two subdomains:
-
-1. **tasks** — Task lifecycle operations (requires task name): discuss, research, plan, execute, review
-2. **context** — Codebase context management (no task name): review, add
-</objective>
-
-<execution_context>
-**Parse $ARGUMENTS to determine subdomain:**
-
-- If starts with "tasks" → extract remaining words as task name, go to Tasks flow
-- If starts with "context" → go to Context flow
-- If a bare word that matches a directory in `.specd/tasks/` or `.specd/features/` → treat as `tasks {name}`
-- If empty or unrecognized → ask user which subdomain
-
-**If subdomain unclear, ask:**
-Use AskUserQuestion:
-- header: "Toolbox"
-- question: "Which toolbox?"
-- options:
-  - "Tasks" — Discuss, research, plan, execute, or review a task
-  - "Context" — Review or add to codebase context
-
----
-
-## Tasks Flow
-
-Requires a task name. If not provided after "tasks", check `.specd/tasks/` for available tasks. If only one task exists, use it automatically. If multiple, ask.
-
-Validate using:
-@~/.claude/specdacular/references/validate-task.md
-
-Then present the menu using AskUserQuestion:
-- header: "Operation"
-- question: "What would you like to do with {task-name}?"
-- options:
-  - "Discuss" — Explore gray areas and record decisions
-  - "Research" — Spawn parallel agents for patterns/pitfalls
-  - "Plan" — Create execution phases
-  - "Execute" — Execute the next phase
-  - "Review" — Review executed phase
-
-Based on selection, delegate to the appropriate workflow:
-- Discuss → @~/.claude/specdacular/workflows/discuss.md
-- Research → @~/.claude/specdacular/workflows/research.md
-- Plan → @~/.claude/specdacular/workflows/plan.md
-- Execute → @~/.claude/specdacular/workflows/execute.md
-- Review → @~/.claude/specdacular/workflows/review.md
-
----
-
-## Context Flow
-
-No task name needed. Present the menu using AskUserQuestion:
-- header: "Context"
-- question: "What would you like to do with codebase context?"
-- options:
-  - "Review" — Walk through and review a context file section by section
-  - "Add" — Add new content to a context file
-
-Based on selection, delegate to the appropriate workflow:
-- Review → follow the context-manual-review.md workflow
-- Add → follow the context-add.md workflow
-</execution_context>
-
-<context>
-Arguments: $ARGUMENTS
-
-**Task workflows:**
-@~/.claude/specdacular/workflows/discuss.md
-@~/.claude/specdacular/workflows/research.md
-@~/.claude/specdacular/workflows/plan.md
-@~/.claude/specdacular/workflows/execute.md
-@~/.claude/specdacular/workflows/review.md
-
-**Context workflows:**
-@~/.claude/specdacular/workflows/context-manual-review.md
-@~/.claude/specdacular/workflows/context-add.md
-</context>
-
-<success_criteria>
-- [ ] Subdomain selected (tasks or context) — from argument or prompt
-- [ ] For tasks: task validated and operation menu shown
-- [ ] For context: context operation menu shown
-- [ ] Selected operation executed via correct workflow
-</success_criteria>