feat!: remove ClaudeKit dependency, become standalone

BREAKING CHANGE: Removed ClaudeKit and STM dependencies. Ideate commands migrated to brainstorm:* commands. Spec:feedback command migrated to feedback:* commands.Task tracking now via 03-tasks.md. Node.js requirement lowered to 20+. Specs directory changed from specs/ to doc/specs/.

Author: kennyjpowers

.claude/README.md

@@ -11,58 +11,69 @@ This directory contains custom commands and settings distributed via the **claud
 
 claudeflow provides a complete feature development workflow:
 
-1. **Ideation** - Structured investigation before coding
-2. **Specification** - Transform ideation into validated specs
+1. **Brainstorm** - Structured investigation before coding
+2. **Clarify & Specify** - Transform brainstorm into validated specs
 3. **Decomposition** - Break specs into actionable tasks
 4. **Implementation** - Execute tasks with session continuity
-5. **Feedback** - Process post-implementation feedback
+5. **Feedback** - Add and resolve post-implementation feedback
 6. **Documentation** - Update docs based on changes
 
 ## Available Custom Commands
 
-### /ideate
-Structured ideation workflow that enforces complete investigation for any code-change task (bug fix or feature). Creates comprehensive ideation documentation.
+### /brainstorm:start
+Structured brainstorming workflow that enforces complete investigation for any code-change task (bug fix or feature). Creates comprehensive brainstorm documentation.
 
-**Usage**: `/ideate Fix chat UI auto-scroll bug when messages exceed viewport height`
+**Usage**: `/brainstorm:start Fix chat UI auto-scroll bug when messages exceed viewport height`
 
-### /ideate-to-spec
-Transform an ideation document into a validated, implementation-ready specification. Bridges the gap between ideation and implementation with automatic open questions resolution.
+### /brainstorm:clarify
+Interactive clarification phase for brainstorm documents. Extracts decisions from brainstorm clarifications and prepares for specification creation.
 
 **Features:**
-- Extracts decisions from ideation clarifications
-- Builds detailed spec via `/spec:create`
+- Extracts decisions from brainstorm clarifications
 - **Automatically resolves open questions interactively**
-- Validates completeness via `/spec:validate`
-- Loops until all questions answered
-- Preserves audit trail in spec file
-
-**Usage**: `/ideate-to-spec doc/specs/<slug>/01-ideation.md`
-
-**Interactive Question Resolution:**
-When the generated specification contains open questions, the system:
-- Parses the "Open Questions" section
 - Presents questions one at a time with progress ("Question 3 of 12")
 - Shows context and available options for each question
 - Supports multi-select questions (e.g., "Which package managers?")
-- Updates spec with strikethrough answers (preserves original context)
-- Re-validates after answering questions
-- Loops until all questions resolved
+- Updates brainstorm doc with strikethrough answers (preserves original context)
 - Skips already-answered questions (re-entrant support)
 
-### /spec:feedback
-Process ONE specific piece of post-implementation feedback with a structured workflow. After manual testing reveals issues or improvement opportunities, this command:
+**Usage**: `/brainstorm:clarify doc/specs/<slug>/01-brainstorm.md`
+
+### /brainstorm:spec
+Transform a brainstorm document into a validated, implementation-ready specification. Bridges the gap between brainstorming and implementation.
+
+**Features:**
+- Builds detailed spec via `/spec:create`
+- Validates completeness via `/spec:validate`
+- Loops until all validation issues resolved
+- Preserves audit trail in spec file
+
+**Usage**: `/brainstorm:spec doc/specs/<slug>/01-brainstorm.md`
+
+**Note:** For a complete workflow, run `/brainstorm:clarify` first to resolve open questions, then `/brainstorm:spec` to generate the specification.
+
+### /feedback:add
+Add ONE specific piece of post-implementation feedback. After manual testing reveals issues or improvement opportunities, this command:
 
 1. Validates prerequisites (implementation must exist)
 2. Collects detailed feedback description
 3. Explores relevant code with targeted investigation
 4. Optionally consults research-expert for solution approaches
-5. Guides through interactive decisions (implement now/defer/out-of-scope)
-6. Updates spec changelog for "implement now" decisions
-7. Logs all decisions in `05-feedback.md`
+5. Logs feedback in `05-feedback.md`
+
+**Usage**: `/feedback:add doc/specs/add-user-auth/02-specification.md`
+
+### /feedback:resolve
+Resolve pending feedback items with structured decisions. For each unresolved feedback item:
+
+1. Presents feedback with context
+2. Guides through interactive decisions (implement now/defer/out-of-scope)
+3. Updates spec changelog for "implement now" decisions
+4. Updates feedback status in `05-feedback.md`
 
 Seamlessly integrates with incremental `/spec:decompose` and resume `/spec:execute` for feedback iteration cycles.
 
-**Usage**: `/spec:feedback doc/specs/add-user-auth/02-specification.md`
+**Usage**: `/feedback:resolve doc/specs/add-user-auth/02-specification.md`
 
 ### /spec:doc-update
 Review all documentation to identify what needs to be updated based on a new specification file. Launches parallel documentation expert agents.

.github/workflows/release.yml

@@ -21,7 +21,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: 22.14.0
+          node-version: '20'
 
       - name: Install dependencies
         run: npm install
@@ -62,7 +62,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: 22.14.0
+          node-version: '20'
 
       - name: Update npm to latest
         run: npm install -g npm@latest

CLAUDE.md

@@ -24,58 +24,67 @@ See [docs/INSTALLATION_GUIDE.md](docs/INSTALLATION_GUIDE.md) for detailed prereq
 Complete feature lifecycle in 6 phases:
 
 ```
-IDEATION → SPECIFICATION → DECOMPOSITION → IMPLEMENTATION → FEEDBACK → COMPLETION
+BRAINSTORM → CLARIFY → SPECIFICATION → DECOMPOSITION → IMPLEMENTATION → FEEDBACK → COMPLETION
 ```
 
-### Phase 1: Ideation
-- **Command:** `/ideate <task-brief>`
-- **Output:** `doc/specs/<slug>/01-ideation.md`
+### Phase 1: Brainstorm
+- **Command:** `/brainstorm:start <task-brief>`
+- **Output:** `doc/specs/<slug>/01-brainstorm.md`
 - **Purpose:** Enforce complete investigation before code changes
 - **Includes:** Intent, pre-reading, codebase mapping, root cause analysis, research, clarifications
 
-### Phase 2: Specification
-- **Command:** `/ideate-to-spec <path-to-ideation>`
+### Phase 2: Clarify
+- **Command:** `/brainstorm:clarify <path-to-brainstorm>`
+- **Output:** Updates `doc/specs/<slug>/01-brainstorm.md` with resolved questions
+- **Purpose:** Resolve open questions interactively before creating specification
+- **Process:** Detect questions → present with context → record answers → re-validate
+
+### Phase 3: Specification
+- **Command:** `/brainstorm:spec <path-to-brainstorm>`
 - **Output:** `doc/specs/<slug>/02-specification.md`
-- **Purpose:** Transform ideation into validated technical specification
-- **Process:** Extract decisions → build spec → validate → resolve open questions → re-validate
-- **Interactive:** Automatically detects and resolves open questions before completion
+- **Purpose:** Transform brainstorm into validated technical specification
+- **Process:** Extract decisions → build spec → validate
 
-### Phase 3: Decomposition
+### Phase 4: Decomposition
 - **Command:** `/spec:decompose <path-to-spec>`
 - **Output:** `doc/specs/<slug>/03-tasks.md`
 - **Purpose:** Break specification into actionable tasks
 - **Pattern:** Full implementation details copied into tasks (NOT summaries)
 
-### Phase 4: Implementation
+### Phase 5: Implementation
 - **Command:** `/spec:execute <path-to-spec>`
 - **Output:** `doc/specs/<slug>/04-implementation.md`
 - **Purpose:** Implement tasks incrementally with session continuity
 - **Process:** For each task: implement → test → code review → fix → commit
 - **Tracks:** Progress, files modified, tests added, known issues, next steps
 
-### Phase 5: Feedback
-- **Command:** `/spec:feedback <path-to-spec>`
+### Phase 6: Feedback
+- **Commands:** `/feedback:add` then `/feedback:resolve`
 - **Output:** `doc/specs/<slug>/05-feedback.md`
-- **Purpose:** Process post-implementation feedback with structured decisions
-- **Process:** One feedback item at a time → explore code → interactive decisions → take action based on outcome
+- **Purpose:** Capture and process post-implementation feedback with structured decisions
+- **Two-Step Process:**
+  1. **Capture:** `/feedback:add` - Loop to capture multiple feedback items (save-as-you-go)
+  2. **Resolve:** `/feedback:resolve` - Batch analyze and resolve all pending items
 - **Decision Outcomes:**
   - **Implement Now:** Update spec changelog → incremental `/spec:decompose` → resume `/spec:execute`
   - **Defer:** Log for future consideration in feedback file
   - **Out of Scope:** Log decision with rationale → no further action
 - **Integration:** Works with incremental `/spec:decompose` and resume `/spec:execute`
 
-### Phase 6: Completion
+### Phase 7: Completion
 - **Commands:** `/spec:doc-update`, git commit & push
 - **Purpose:** Finalize changes, update documentation, push to remote
 
 ## Key Commands
 
-### Custom Commands (4)
+### Custom Commands (6)
 | Command | Purpose |
 |---------|---------|
-| `/ideate <task-brief>` | Structured investigation workflow |
-| `/ideate-to-spec <path>` | Transform ideation → validated spec |
-| `/spec:feedback <path>` | Post-implementation feedback processing |
+| `/brainstorm:start <task-brief>` | Structured investigation workflow |
+| `/brainstorm:clarify <path>` | Resolve open questions interactively |
+| `/brainstorm:spec <path>` | Transform brainstorm → validated spec |
+| `/feedback:add [path]` | Quick capture of feedback items |
+| `/feedback:resolve [path]` | Batch analyze and resolve pending feedback |
 | `/spec:doc-update <path>` | Review docs with parallel agents |
 
 ### Command Overrides (4)
@@ -94,7 +103,7 @@ Enhanced versions of spec commands:
 
 ```
 doc/specs/<feature-slug>/
-├── 01-ideation.md          # Investigation & research
+├── 01-brainstorm.md        # Investigation & research
 ├── 02-specification.md     # Technical specification
 ├── 03-tasks.md             # Task breakdown
 ├── 04-implementation.md    # Progress tracking
@@ -111,13 +120,13 @@ doc/specs/<feature-slug>/
 
 ### Interactive Question Resolution
 
-The `/ideate-to-spec` command includes automatic open questions resolution to ensure specifications are implementation-ready:
+The `/brainstorm:clarify` command provides automatic open questions resolution to ensure brainstorm documents are ready for specification creation:
 
 **How It Works:**
-1. After spec creation, system detects "Open Questions" section
+1. System detects "Open Questions" section in brainstorm document
 2. Presents each unanswered question interactively with context
 3. Records answers with audit trail (strikethrough format)
-4. Updates spec file incrementally (save-as-you-go)
+4. Updates document incrementally (save-as-you-go)
 5. Re-validates and loops until all questions resolved
 6. Summary shows all resolved questions
 
@@ -130,25 +139,24 @@ The `/ideate-to-spec` command includes automatic open questions resolution to en
 - External edit detection prevents data loss
 
 **Backward Compatibility:**
-- Specs without "Open Questions" section skip resolution steps entirely
+- Documents without "Open Questions" section skip resolution steps entirely
 - Already-answered questions (containing "Answer:") are skipped automatically
 - Re-entrant: Can run multiple times, only processes unanswered questions
 
 **Error Handling:**
-- Edit failures automatically retry after re-reading spec
+- Edit failures automatically retry after re-reading document
 - External edits detected via re-parsing on each loop iteration
 - Validation failures for non-question issues prompt user interactively
 - Manual intervention requested only when automated recovery fails
 
 **Example Workflow:**
 ```bash
-/ideate-to-spec doc/specs/my-feature/01-ideation.md
-# → System creates spec via /spec:create
+/brainstorm:clarify doc/specs/my-feature/01-brainstorm.md
 # → Detects 5 open questions
 # → Presents questions interactively
 # → Question 1 of 5: Package Manager Support?
 # → User answers each question
-# → Spec updated with strikethrough answers
+# → Document updated with strikethrough answers
 # → Re-validates until complete
 # → Summary shows 5 questions resolved
 ```
@@ -218,8 +226,10 @@ claudeflow/                    # npm package (@33strategies/claudeflow)
 │   └── utils/                 # Cross-platform utilities
 ├── .claude/                   # Distributed in package
 │   ├── commands/              # Custom slash commands
-│   │   ├── ideate.md
-│   │   ├── ideate-to-spec.md
+│   │   ├── brainstorm/        # Brainstorming workflow commands
+│   │   │   ├── start.md       # Structured brainstorming workflow
+│   │   │   ├── clarify.md     # Resolve open questions
+│   │   │   └── spec.md        # Transform brainstorm to spec
 │   │   └── spec/              # Spec command overrides
 │   ├── settings.json.example  # Configuration template
 │   └── README.md
@@ -270,23 +280,25 @@ claudeflow doctor    # Verify installation
 
 ### Standard Workflow
 ```bash
-/ideate <task-brief>
-/ideate-to-spec doc/specs/<slug>/01-ideation.md
+/brainstorm:start <task-brief>
+/brainstorm:clarify doc/specs/<slug>/01-brainstorm.md
+/brainstorm:spec doc/specs/<slug>/01-brainstorm.md
 /spec:decompose doc/specs/<slug>/02-specification.md
 /spec:execute doc/specs/<slug>/02-specification.md
 
-# After manual testing, process feedback
-/spec:feedback doc/specs/<slug>/02-specification.md  # One item at a time
-# (Choose: implement/defer/out-of-scope)
-# If "implement": spec updated, then run:
+# After manual testing, capture and resolve feedback
+/feedback:add doc/specs/<slug>/02-specification.md    # Capture multiple items
+/feedback:resolve doc/specs/<slug>/05-feedback.md     # Batch analyze & decide
+# (For each item: implement/defer/out-of-scope)
+# If any "implement": spec updated, then run:
 /spec:decompose doc/specs/<slug>/02-specification.md  # Incremental mode
 /spec:execute doc/specs/<slug>/02-specification.md    # Resume mode
 
 # Final steps
 /spec:doc-update doc/specs/<slug>/02-specification.md
 ```
 
-### Quick Start (Skip Ideation)
+### Quick Start (Skip Brainstorming)
 ```bash
 /spec:create <description>
 /spec:decompose doc/specs/<slug>/02-specification.md