specdacular 0.10.0 → 0.11.0

package/specdacular/workflows/new.md

@@ -90,21 +90,22 @@ End main workflow.
 
 **Check for codebase docs:**
 ```bash
-ls .specd/codebase/*.md 2>/dev/null
+[ -f "CLAUDE.md" ] && cat CLAUDE.md || echo "no_claude_md"
+ls docs/*.md 2>/dev/null
 ```
 
-**If codebase docs found:**
+**If CLAUDE.md or docs/ found:**
 ```
 Found codebase documentation. I'll reference these when defining requirements.
 ```
-Read the available docs to understand project structure, code patterns, and architecture.
+Read the CLAUDE.md routing table and referenced docs to understand project structure, code patterns, and architecture.
 
 **If no codebase docs found:**
 Use AskUserQuestion:
 - header: "No Codebase Docs"
 - question: "I didn't find codebase documentation. How should we proceed?"
 - options:
-  - "Run map-codebase first" — Creates AI-optimized docs
+  - "Run /specd.docs first" — Generates topic docs and CLAUDE.md routing table
   - "Continue without" — Proceed without codebase context
   - "Custom location" — Docs are elsewhere
 

package/specdacular/workflows/orchestrator/new.md

@@ -13,10 +13,10 @@ Called from the main `new.md` workflow after orchestrator mode detection.
 <step name="load_system_docs">
 Read system-level codebase docs:
 
-- `.specd/codebase/PROJECTS.md` — Project registry
-- `.specd/codebase/TOPOLOGY.md` — Communication patterns
-- `.specd/codebase/CONTRACTS.md` — Shared interfaces
-- `.specd/codebase/CONCERNS.md` — System-level concerns
+- `docs/PROJECTS.md` — Project registry
+- `docs/TOPOLOGY.md` — Communication patterns
+- `docs/CONTRACTS.md` — Shared interfaces
+- `docs/CONCERNS.md` — System-level concerns
 
 Read project list from `.specd/config.json` `"projects"` array.
 

package/specdacular/workflows/orchestrator/plan.md

@@ -13,16 +13,16 @@ Called from the main `plan.md` workflow after orchestrator mode detection.
 <step name="load_cross_project_context">
 Load system-level and sub-project context.
 
-**System-level codebase docs:**
-- `.specd/codebase/PROJECTS.md` — Project registry
-- `.specd/codebase/TOPOLOGY.md` — Communication patterns
-- `.specd/codebase/CONTRACTS.md` — Shared interfaces
+**System-level docs:**
+- `docs/PROJECTS.md` — Project registry
+- `docs/TOPOLOGY.md` — Communication patterns
+- `docs/CONTRACTS.md` — Shared interfaces
 
 **Sub-project context:**
 From task config.json `"projects"` array, for each project:
 - Read `{project-path}/.specd/tasks/{task-name}/FEATURE.md` — Project-specific requirements
-- Read `{project-path}/.specd/codebase/MAP.md` — Project code overview (if exists)
-- Read `{project-path}/.specd/codebase/PATTERNS.md` — Project patterns (if exists)
+- Read `{project-path}/CLAUDE.md` — Project routing table and docs (if exists)
+- Read `{project-path}/docs/*.md` — Project topic docs (if exists)
 
 ```
 Orchestrator mode: {N} projects involved in this task.

package/commands/specd.codebase.map.md

@@ -1,72 +0,0 @@
----
-name: specd.codebase.map
-description: Analyze codebase with parallel agents to produce AI-optimized documentation
-argument-hint: ""
-allowed-tools:
-  - Read
-  - Bash
-  - Glob
-  - Grep
-  - Write
-  - Task
----
-
-<objective>
-Analyze existing codebase using parallel mapper agents to produce 4 AI-optimized documents.
-
-Each mapper agent explores a focus area and **writes documents directly** to `.specd/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.
-
-Output: .specd/codebase/ folder with 4 documents designed for Claude consumption.
-</objective>
-
-<execution_context>
-@~/.claude/specdacular/workflows/map-codebase.md
-</execution_context>
-
-<context>
-**These documents are FOR CLAUDE, not humans.**
-
-Each document answers a question Claude can't get from reading code:
-
-| Document | Question it answers |
-|----------|---------------------|
-| MAP.md | "Where is X? What functions exist?" |
-| PATTERNS.md | "How do I write code that fits here?" |
-| STRUCTURE.md | "Where do I put new code?" |
-| CONCERNS.md | "What will bite me?" |
-
-**Principle:** Don't document what Claude can grep. Document tribal knowledge, gotchas, and patterns.
-</context>
-
-<when_to_use>
-**Use map-codebase for:**
-- First time working with a codebase
-- Before planning a new feature
-- After significant refactoring
-- Onboarding Claude to an unfamiliar repo
-
-**Skip map-codebase for:**
-- Trivial codebases (<10 files)
-- When you already have recent codebase docs
-</when_to_use>
-
-<process>
-1. Check if .specd/codebase/ already exists (offer to refresh or skip)
-2. Create .specd/codebase/ directory
-3. Spawn 4 parallel specd-codebase-mapper agents:
-   - Agent 1: map focus → writes MAP.md
-   - Agent 2: patterns focus → writes PATTERNS.md
-   - Agent 3: structure focus → writes STRUCTURE.md
-   - Agent 4: concerns focus → writes CONCERNS.md
-4. Wait for agents to complete, collect confirmations
-5. Verify all 4 documents exist
-6. Commit codebase map
-7. Report completion
-</process>
-
-<success_criteria>
-- [ ] .specd/codebase/ directory created
-- [ ] All 4 documents written by mapper agents
-- [ ] Documents contain real code examples (not placeholders)
-- [ ] Parallel agents completed without errors
-</success_criteria>

package/commands/specd.codebase.review.md

@@ -1,39 +0,0 @@
----
-name: specd.codebase.review
-description: "Review and edit codebase context files section by section"
-argument-hint: ""
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Task
-  - AskUserQuestion
----
-
-<objective>
-Walk through and review a codebase context file (.specd/codebase/*.md) section by section. Confirm, edit, remove, or re-map individual sections.
-
-Output: Updated context file with reviewed/edited sections and updated timestamps.
-</objective>
-
-<execution_context>
-Follow the context-manual-review workflow:
-@~/.claude/specdacular/workflows/context-manual-review.md
-</execution_context>
-
-<context>
-**Context workflows:**
-@~/.claude/specdacular/workflows/context-manual-review.md
-@~/.claude/specdacular/workflows/context-add.md
-</context>
-
-<success_criteria>
-- [ ] User selects a context file to review
-- [ ] Section list shown with tag status
-- [ ] User can confirm, edit, remove, or re-map each section
-- [ ] Timestamps updated after review
-- [ ] Changes committed
-</success_criteria>