claude-orchestration 1.0.5 → 1.0.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-orchestration",
-  "version": "1.0.5",
+  "version": "1.0.6",
   "description": "CLI tool to scaffold Claude orchestration workflows into your project",
   "bin": {
     "claude-orchestration": "bin/cli.js"

package/templates/claude/orchestration.md

@@ -1,13 +1,9 @@
 # Orchestration Protocol
 
-**MANDATORY: Process this file BEFORE any tool usage.**
-
----
+**MANDATORY: Process BEFORE any tool usage.**
 
 ## 1. CLASSIFY TASK
 
-### ⛔ STOP CHECKPOINT #1
-
 | Signal Words | Workflow |
 |--------------|----------|
 | build, create, add, implement, new | `feature.md` |
@@ -19,83 +15,38 @@
 | document, README, explain | `docs.md` |
 | complex, multi-step, plan | `todo.md` |
 
-**Complexity:** 1-2 ops (simple) | 3+ ops (complex → also use `todo.md`)
-
-**Technology:** React (`.jsx`/`.tsx`, react imports, hooks) → `workflows/react/` | Other → `workflows/`
-
----
-
-## 2. DECLARE BINDING
+**Complexity:** 1-2 ops = simple | 3+ ops = complex (add `todo.md`)
+**Technology:** React (`.jsx`/`.tsx`, hooks) → `workflows/react/` | Other → `workflows/`
 
-### ⛔ STOP CHECKPOINT #2
+### Selection
+- **Clear match:** Proceed to binding
+- **Ambiguous:** Use `AskUserQuestion` (header: "Workflow", options: relevant workflows)
+- **No match:** Ask user to clarify
 
-Before ANY tool use, declare:
+## 2. BINDING (required before ANY tool use)
 
 ```
 ORCHESTRATION_BINDING:
 - Task: [description]
-- Classification: [workflow]
 - Workflow: [path]
-- Complexity: [1-2 ops / 3+ ops]
-- Technology: [React / Other / N/A]
+- Complexity: [simple/complex]
 ```
 
----
-
 ## 3. EXEMPT TASKS
 
-Exemption requires ALL: single file, 1-2 ops, zero architectural impact, obvious correctness, no debugging.
-
-**NOT exempt:** "quick bug fix" (needs investigation), "small feature" (needs context), "make it faster" (needs measurement).
+Requires ALL: single file, 1-2 ops, zero architecture impact, obvious correctness.
 
-Exempt binding:
 ```
 ORCHESTRATION_BINDING:
 - Task: [description]
 - Classification: EXEMPT
-- Justification: [criteria met]
 ```
 
----
-
-## 4. VIOLATIONS
-
-| Type | Indicator |
-|------|-----------|
-| Missing Binding | Tool use without declaration |
-| Premature Tool Use | Edit before workflow read |
-| Scope Creep | Unplanned files modified |
-| False Exemption | Exempt claim for complex task |
+## 4. COMPLETION
 
-**Self-correct:** STOP → DECLARE violation → RETURN to checkpoint → REBIND → CONTINUE
-
----
-
-## 5. EXECUTION
-
-**Pre-Work:** Binding declared, workflow read, "Before Coding" answered
-
-**Mid-Work:** Within scope, no unplanned files, todo tracking if 3+ ops
-
-**Completion:** Validation done, then declare:
 ```
 ORCHESTRATION_COMPLETE:
 - Task: [description]
 - Workflow: [used]
 - Files: [modified]
 ```
-
----
-
-## 6. WORKFLOW REFERENCE
-
-| Workflow | React | Other |
-|----------|-------|-------|
-| feature | `workflows/react/feature.md` | `workflows/feature.md` |
-| bugfix | `workflows/react/bugfix.md` | `workflows/bugfix.md` |
-| refactor | `workflows/react/refactor.md` | `workflows/refactor.md` |
-| performance | `workflows/react/performance.md` | `workflows/performance.md` |
-| review | `workflows/react/review.md` | `workflows/review.md` |
-| pr | `workflows/react/pr.md` | `workflows/pr.md` |
-| docs | `workflows/react/docs.md` | `workflows/docs.md` |
-| todo | `workflows/react/todo.md` | `workflows/todo.md` |

package/templates/claude/workflows/react/bugfix.md

@@ -1,50 +1,32 @@
 # React Bugfix Workflow
 
-> Architecture rules: See orchestration.md. Violations block merge.
+## 1. Reproduce
 
-## Before Coding
+- Confirm bug exists | find minimal repro
+- Check Strict Mode behavior
+- Answer: Expected vs actual? React 18 concurrent issue?
 
-MUST answer:
-- Can I reproduce the bug?
-- What is expected vs actual behavior?
-- Is this related to React 18 concurrent features?
+## 2. Locate Root Cause
 
-## Process
+| Common React 18 Issues |
+|------------------------|
+| Effects missing cleanup |
+| Stale closures in effects |
+| Concurrent rendering race conditions |
+| Automatic batching changes |
 
-### 1. Reproduce and Isolate
-- Confirm the bug exists
-- Check if it only occurs in Strict Mode
-- Find minimal reproduction case
+## 3. Fix
 
-### 2. Locate Root Cause
+- Keep changes within affected feature folder
+- Add cleanup: `return () => controller.abort()`
+- Fix stale closures with proper deps
 
-**Common React 18 issues:**
-- Effects missing cleanup functions
-- Effects with stale closures
-- Race conditions from concurrent rendering
-- Automatic batching behavior changes
+## 4. Verify
 
-### 3. Fix
-
-MUST keep changes within affected feature folder.
-
-```tsx
-// Example: Add cleanup for effects
-useEffect(() => {
-  const controller = new AbortController()
-  fetchData(controller.signal)
-  return () => controller.abort()
-}, [])
-```
-
-### 4. Verify
-- Confirm bug is fixed
-- Test with Strict Mode enabled
-- Add test that would have caught this bug
+- Confirm fix | test with Strict Mode
+- Add regression test
 
 ## Constraints
 
-- A bugfix is NOT an opportunity to refactor
-- The best fix is the smallest fix
-- NEVER introduce barrel exports
-- Note other issues separately—don't fix them here
+- Smallest fix only | NO refactoring
+- NO barrel exports | note other issues separately

package/templates/claude/workflows/react/feature.md

@@ -1,55 +1,37 @@
 # React Feature Workflow
 
-> Architecture rules: See orchestration.md. Violations block merge.
+## 1. Architecture
 
-## Before Coding
+**IF not specified:** Use `AskUserQuestion` (header: "Architecture")
 
-MUST answer:
-- What problem does this feature solve?
-- What's the minimal viable version?
-- Which feature folder does this belong in?
-- Are there existing patterns to follow?
+| Architecture | Structure |
+|--------------|-----------|
+| Feature-driven | `features/{name}/components\|hooks\|utils/` |
+| Flat feature-driven | `features/{name}/` flat files |
+| Atomic design | `atoms\|molecules\|organisms\|templates/` |
 
-## Process
+**IF project has patterns:** Follow existing, skip question.
 
-### 1. Understand Context
-- Read related existing code
-- Identify the target feature folder
-- Check for similar implementations
-- Review reusable hooks and utilities
+## 2. Context
 
-### 2. Plan Implementation
-- Break into small, testable pieces
-- Plan component hierarchy
-- Identify shared vs feature-specific code
-- Design state approach (local, context, or external)
+- Read related code, identify target folder
+- Check similar implementations, reusable hooks/utils
+- Answer: What problem? Minimal version? Which folder?
 
-### 3. Implement
+## 3. Implement
 
-**Components:**
-- Function components only
-- `useState`/`useReducer` for local state
+**Components:** Function only | `useState`/`useReducer` for local state
+**Hooks:** Extract logic | `hooks/{feature}/{name}.ts` | descriptive names
+**State:** Lift only as needed | composition over prop drilling
 
-**Hooks:**
-- Extract reusable logic into custom hooks
-- Components handle rendering; hooks handle logic
-- Name descriptively: `useAuthState`, `useFormValidation`
-- Place in `hooks/{feature}/{hookName}.ts`
+## 4. Validate
 
-**State:**
-- Lift state only as high as necessary
-- Prefer composition over prop drilling
-- `useSyncExternalStore` for external state
-
-### 4. Validate
-- Run existing tests for regressions
-- Add tests for new components/hooks
-- Test loading and error states
-- Remove debugging code and unused imports
+- Run tests for regressions
+- Add tests for new code
+- Test loading/error states
+- Remove debug code
 
 ## Constraints
 
-- NEVER create `index.ts` or `index.tsx` files
-- MUST import directly from file, not folder
-- MUST match surrounding code style
-- NEVER add features beyond what was requested
+- NO `index.ts`/`index.tsx` | import from file directly
+- Match existing style | no extra features

package/templates/claude/workflows/react/pr.md

@@ -2,23 +2,18 @@
 
 ## Process
 
-1. Read the diff between current branch and main/master
-2. Analyze changes to understand what was done
-3. Output a PR title and description
+1. Read diff (current branch vs main/master)
+2. Analyze changes
+3. Output title + description
 
-## Output Format
+## Output
 
 ```
-PR Title: <concise title>
-
-Description:
-<2-3 sentences: what changed and why>
+PR Title: <imperative mood>
+Description: <2-3 sentences: what + why>
 ```
 
 ## Constraints
 
-- MUST use imperative mood ("Add feature" not "Added feature")
-- MUST mention breaking changes if any
-- Keep description focused on "what" and "why"
-- NEVER create branches, push, or create PRs remotely
-- ONLY output the title and description for the user to copy
+- Imperative mood ("Add" not "Added") | mention breaking changes
+- Output only | NO branch/push/remote PR creation

package/templates/claude/workflows/react/refactor.md

@@ -1,43 +1,32 @@
 # React Refactor Workflow
 
-> Architecture rules: See orchestration.md. Violations block merge.
+## 1. Safety Net
 
-## Before Coding
+- Run tests | add if coverage insufficient
+- Answer: What improvement? How verify unchanged behavior?
 
-MUST answer:
-- What specific improvement am I making?
-- Is there adequate test coverage?
-- How will I verify behavior is unchanged?
+## 2. Plan
 
-## Process
-
-### 1. Ensure Safety Net
-- Run tests to confirm they pass
-- Add tests if coverage is insufficient
-
-### 2. Plan
-- Map all imports and dependencies
-- Identify all callers of affected code
+- Map imports/dependencies | identify all callers
 - Break into small, safe steps
 
-### 3. Execute Incrementally
+## 3. Execute
 
-Make one type of change at a time. Examples:
+One change type at a time | run tests after each:
 
-- Rename files to match folder names
-- Convert barrel imports to direct imports
-- Extract logic into hooks
-- Split large components
+| Change Types |
+|--------------|
+| Rename files to match folders |
+| Barrel → direct imports |
+| Extract logic into hooks |
+| Split large components |
 
-Run tests after each step.
+## 4. Validate
 
-### 4. Validate
-- All tests pass
-- No `index.ts` or `index.tsx` files remain
-- All entry points match folder names
+- All tests pass | no `index.ts`/`index.tsx`
+- Entry points match folder names
 
 ## Constraints
 
-- Refactoring changes structure, NOT behavior
-- NEVER fix bugs during refactor—note them separately
-- MUST keep scope contained: one change type at a time
+- Structure only, NOT behavior | NO bug fixes
+- One change type at a time | note issues separately

package/templates/claude/workflows/react/review.md

@@ -1,54 +1,46 @@
 # React Code Review Workflow
 
-> Architecture rules: See orchestration.md. Violations block merge.
+## 1. Understand
 
-## Before Reviewing
+- Read PR description | review diff scope
+- Answer: What is the goal? What files changed?
 
-MUST answer:
-- What is this change trying to accomplish?
-- What files are modified?
+## 2. Architecture Checklist
 
-## Process
+| Check | Rule |
+|-------|------|
+| Barrels | No `index.ts`/`index.tsx` |
+| Entry files | Match folder names (`Button/Button.tsx`) |
+| Imports | Direct, not barrel |
+| Colocation | Component + hooks + types + tests together |
+| Placement | Correct feature folder |
 
-### 1. Understand the Change
-- Read the PR description
-- Review the diff to understand scope
-- Check if the approach makes sense for the goal
+## 3. React Patterns Checklist
 
-### 2. Check Architecture Compliance
+| Check | Rule |
+|-------|------|
+| Components | Function only, no class |
+| Hooks | No conditionals, proper deps |
+| Effects | Cleanup where needed |
+| Memory | No leaks (subscriptions, timers) |
+| States | Loading + error handled |
 
-- [ ] No `index.ts` or `index.tsx` barrel files
-- [ ] Entry files match folder names (`Button/Button.tsx`)
-- [ ] Direct imports used, not barrel imports
-- [ ] Files colocated properly (component, hooks, types, tests together)
-- [ ] New code placed in correct feature folder
+## 4. Code Quality Checklist
 
-### 3. Check React Patterns
+| Check | Rule |
+|-------|------|
+| Debug | No console.log/debugger |
+| Imports | No unused |
+| Types | No unjustified `any` |
+| Tests | Cover new functionality |
+| Scope | No unrelated changes |
 
-- [ ] Function components only (no class components)
-- [ ] Hooks follow rules (no conditional hooks, proper dependencies)
-- [ ] Effects have cleanup where needed
-- [ ] No obvious memory leaks (subscriptions, timers)
-- [ ] Loading and error states handled
+## 5. Feedback
 
-### 4. Check Code Quality
-
-- [ ] No debugging code left in (console.log, debugger)
-- [ ] No unused imports or variables
-- [ ] Types are accurate (no `any` without justification)
-- [ ] Tests cover new functionality
-- [ ] No unrelated changes mixed in
-
-### 5. Provide Feedback
-
-Categorize comments:
-- **Blocking**: Must fix before merge (bugs, architecture violations)
-- **Suggestion**: Improvements to consider
-- **Question**: Clarification needed
+- **Blocking:** Must fix (bugs, architecture violations)
+- **Suggestion:** Improvements | **Question:** Clarification
 
 ## Constraints
 
-- NEVER approve code with architecture violations
-- NEVER approve code without understanding what it does
-- Keep feedback specific and actionable
-- Suggest fixes, not just problems
+- NO approval with violations | must understand code
+- Specific + actionable | suggest fixes, not just problems