{"_id":"@33strategies/claudeflow","_rev":"6-9083302162272cf13d9a2bc05d73888a","name":"@33strategies/claudeflow","dist-tags":{"latest":"2.0.0"},"versions":{"1.0.1":{"name":"@33strategies/claudeflow","version":"1.0.1","keywords":["claude","claude-code","workflow","orchestration","ai-assisted-development","cli","automation"],"author":{"name":"Kenneth Priester","email":"33strategies@duck.com"},"license":"MIT","_id":"@33strategies/claudeflow@1.0.1","maintainers":[{"name":"kjpriester","email":"kennethjpriester@gmail.com"}],"homepage":"https://claudeflow.dev","bugs":{"url":"https://github.com/kennyjpowers/claude-flow/issues"},"bin":{"claudeflow":"bin/claudeflow.js"},"dist":{"shasum":"b84a356e764ee1cfc623d9d73a2c03124d6fdd8a","tarball":"https://registry.npmjs.org/@33strategies/claudeflow/-/claudeflow-1.0.1.tgz","fileCount":33,"integrity":"sha512-+83K1mDUS/i1A8nigimI0x5kGmj6Qz9pqakRq7cqWc+V8NEu3jZ6YxeDeGx9HX89XKUnY1/FcJ6INOHSIMBD6w==","signatures":[{"sig":"MEQCIBOlPlhg3F7IVQLy3DSdPpWpLP/olTuULhew3q5hUDaFAiATcybSTSKc4Ogw7kJJb9AhCJlGO+uCEmR0eRksXz7J6w==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":319714},"main":"./lib/index.js","type":"module","engines":{"npm":">=9.0.0","node":">=20.0.0"},"gitHead":"51e5604587b4e3b607ffb1826e1292d3907996a8","scripts":{"test":"echo 'Tests coming in Phase 2'","prepublishOnly":"node scripts/verify-files.js"},"_npmUser":{"name":"kjpriester","email":"kennethjpriester@gmail.com"},"repository":{"url":"git+https://github.com/kennyjpowers/claude-flow.git","type":"git"},"_npmVersion":"10.9.4","description":"Workflow orchestration for Claude Code - seamless end-to-end feature development workflow","directories":{},"_nodeVersion":"22.21.1","dependencies":{"claudekit":"^0.9.0","update-notifier":"^7.0.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"semantic-release":"^22.0.0","@semantic-release/git":"^10.0.1","@semantic-release/changelog":"^6.0.3"},"_npmOperationalInternal":{"tmp":"tmp/claudeflow_1.0.1_1763783569741_0.2239878986779087","host":"s3://npm-registry-packages-npm-production"}},"1.1.0":{"name":"@33strategies/claudeflow","version":"1.1.0","keywords":["claude","claude-code","workflow","orchestration","ai-assisted-development","cli","automation"],"author":{"name":"Kenneth Priester","email":"33strategies@duck.com"},"license":"MIT","_id":"@33strategies/claudeflow@1.1.0","maintainers":[{"name":"kjpriester","email":"kennethjpriester@gmail.com"}],"homepage":"https://claudeflow.dev","bugs":{"url":"https://github.com/kennyjpowers/claude-flow/issues"},"bin":{"claudeflow":"bin/claudeflow.js"},"dist":{"shasum":"8bdaefc6ca78a5b70041a50cec2c5cbf1e523844","tarball":"https://registry.npmjs.org/@33strategies/claudeflow/-/claudeflow-1.1.0.tgz","fileCount":33,"integrity":"sha512-hqWFvZnqlHZXMx587QSDez9h4cJXil3Fw5NfJWeoGn5N0vyWs2EalS8yr3tgbE1m+crj0Hchk6E+2gVk3NmphQ==","signatures":[{"sig":"MEUCIQDX0L2eWHSJ41IdF/ZjZ2Sl8wHID5DJScZkwUASqL577QIgS4bbNUSerjNccLuiKZ/McwX5X41vIr/eN1FxCfzcJiU=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@33strategies%2fclaudeflow@1.1.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":320845},"main":"./lib/index.js","type":"module","engines":{"npm":">=9.0.0","node":">=20.0.0"},"gitHead":"4b7847b2a11dcdfae8017f377ac24c645c3278a0","scripts":{"test":"echo 'Tests coming in Phase 2'","prepublishOnly":"node scripts/verify-files.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:c325db07-78d1-4682-bfb2-b13060d23940"}},"repository":{"url":"git+https://github.com/kennyjpowers/claude-flow.git","type":"git"},"_npmVersion":"11.6.3","description":"Workflow orchestration for Claude Code - seamless end-to-end feature development workflow","directories":{},"_nodeVersion":"22.14.0","dependencies":{"claudekit":"^0.9.0","update-notifier":"^7.0.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"semantic-release":"^25.0.2","@semantic-release/git":"^10.0.1","@semantic-release/npm":"^13.1.2","@semantic-release/changelog":"^6.0.3"},"_npmOperationalInternal":{"tmp":"tmp/claudeflow_1.1.0_1763785509069_0.05033423565515571","host":"s3://npm-registry-packages-npm-production"}},"1.1.1":{"name":"@33strategies/claudeflow","version":"1.1.1","keywords":["claude","claude-code","workflow","orchestration","ai-assisted-development","cli","automation"],"author":{"name":"Kenneth Priester","email":"33strategies@duck.com"},"license":"MIT","_id":"@33strategies/claudeflow@1.1.1","maintainers":[{"name":"kjpriester","email":"kennethjpriester@gmail.com"}],"homepage":"https://claudeflow.dev","bugs":{"url":"https://github.com/kennyjpowers/claude-flow/issues"},"bin":{"claudeflow":"bin/claudeflow.js"},"dist":{"shasum":"f5eea2e11ba4ebfeb3ae8fe024ccf73ea91cd575","tarball":"https://registry.npmjs.org/@33strategies/claudeflow/-/claudeflow-1.1.1.tgz","fileCount":34,"integrity":"sha512-xSGM89TXNIbBTif+ckjbV3ZCk0zh4fsnDBLCgXfEoTn8H1AF2iBbvM0lx2ZKKBu81TgW4l0WSc9Ddlb75L8/rA==","signatures":[{"sig":"MEQCIGNopbm/nDW7gaa1Ptikb2do8NrrVy2SRYMOKnWiIIytAiAlgT0xfeJyHNqJ+Fr2WlmFxwkO7nReXWmtMBK5AUQtXg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@33strategies%2fclaudeflow@1.1.1","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":344389},"main":"./lib/index.js","type":"module","engines":{"npm":">=9.0.0","node":">=22.14.0"},"gitHead":"7bd03400abc34e5fba4af70ad95661107454502e","scripts":{"test":"echo 'Tests coming in Phase 2'","prepublishOnly":"node scripts/verify-files.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:c325db07-78d1-4682-bfb2-b13060d23940"}},"repository":{"url":"git+https://github.com/kennyjpowers/claude-flow.git","type":"git"},"_npmVersion":"11.6.3","description":"Workflow orchestration for Claude Code - seamless end-to-end feature development workflow","directories":{},"_nodeVersion":"22.14.0","dependencies":{"claudekit":"^0.9.0","update-notifier":"^7.0.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"semantic-release":"^25.0.2","@semantic-release/git":"^10.0.1","@semantic-release/npm":"^13.1.2","@semantic-release/changelog":"^6.0.3"},"_npmOperationalInternal":{"tmp":"tmp/claudeflow_1.1.1_1763791390373_0.7538162052666086","host":"s3://npm-registry-packages-npm-production"}},"1.1.2":{"name":"@33strategies/claudeflow","version":"1.1.2","keywords":["claude","claude-code","workflow","orchestration","ai-assisted-development","cli","automation"],"author":{"name":"Kenneth Priester","email":"33strategies@duck.com"},"license":"MIT","_id":"@33strategies/claudeflow@1.1.2","maintainers":[{"name":"kjpriester","email":"kennethjpriester@gmail.com"}],"homepage":"https://claudeflow.dev","bugs":{"url":"https://github.com/kennyjpowers/claude-flow/issues"},"bin":{"claudeflow":"bin/claudeflow.js"},"dist":{"shasum":"93385a72732910d8f01f7e2bff729c3f9bdcbaf8","tarball":"https://registry.npmjs.org/@33strategies/claudeflow/-/claudeflow-1.1.2.tgz","fileCount":34,"integrity":"sha512-hq6C16nIjtoRdOCoH4EQ9V9NFl7xAjlK4V0pY6kdVCluaMSUyMkqYOkLbEv2picIoWZsA3tCN+2s+k1S0jG4Tg==","signatures":[{"sig":"MEUCIQDeKEPNFeHdsdRPV+sFOGmUNp1nO7vpaq4r8Vm0jIFuHQIgSZ/t7xc9tUJhbkX4ja5avHSNCg1LE6t6zug24B0lBJs=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@33strategies%2fclaudeflow@1.1.2","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":344641},"main":"./lib/index.js","type":"module","engines":{"npm":">=9.0.0","node":">=22.14.0"},"gitHead":"c40473f1d64f5e688f1eeaa7524bc25aae5a169b","scripts":{"test":"echo 'Tests coming in Phase 2'","prepublishOnly":"node scripts/verify-files.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:c325db07-78d1-4682-bfb2-b13060d23940"}},"repository":{"url":"git+https://github.com/kennyjpowers/claude-flow.git","type":"git"},"_npmVersion":"11.6.3","description":"Workflow orchestration for Claude Code - seamless end-to-end feature development workflow","directories":{},"_nodeVersion":"22.14.0","dependencies":{"claudekit":"^0.9.0","update-notifier":"^7.0.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"semantic-release":"^25.0.2","@semantic-release/git":"^10.0.1","@semantic-release/npm":"^13.1.2","@semantic-release/changelog":"^6.0.3"},"_npmOperationalInternal":{"tmp":"tmp/claudeflow_1.1.2_1763791693217_0.4867916501519023","host":"s3://npm-registry-packages-npm-production"}},"1.2.0":{"name":"@33strategies/claudeflow","version":"1.2.0","keywords":["claude","claude-code","workflow","orchestration","ai-assisted-development","cli","automation"],"author":{"name":"Kenneth Priester","email":"33strategies@duck.com"},"license":"MIT","_id":"@33strategies/claudeflow@1.2.0","maintainers":[{"name":"kjpriester","email":"kennethjpriester@gmail.com"}],"homepage":"https://claudeflow.dev","bugs":{"url":"https://github.com/kennyjpowers/claude-flow/issues"},"bin":{"claudeflow":"bin/claudeflow.js"},"dist":{"shasum":"242dd7270e1fdea6ffc1e7589b7ab6f3feb11f68","tarball":"https://registry.npmjs.org/@33strategies/claudeflow/-/claudeflow-1.2.0.tgz","fileCount":35,"integrity":"sha512-E8vTxAdAwDbCcviqlPUNeAUDcRk+4DxuOSAxE0oSOtpTaDtvBdtE06Cnvxq2jfjS1kawy6JwVf5SfXJXTOGAqg==","signatures":[{"sig":"MEUCIAWVmODtBVjrXoJ7+MHp3/H0ybmNSpYY8Morkzw+nPF8AiEA6/gvZU4wo2bSdRz2dACJwNnS851R9Pn+ZbTr1z4CUIE=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@33strategies%2fclaudeflow@1.2.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":601067},"main":"./lib/index.js","type":"module","engines":{"npm":">=9.0.0","node":">=22.14.0"},"gitHead":"46b1c947e541544d8260411107dd9a107f4d3d1c","scripts":{"test":"echo 'Tests coming in Phase 2'","prepublishOnly":"node scripts/verify-files.js"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:c325db07-78d1-4682-bfb2-b13060d23940"}},"repository":{"url":"git+https://github.com/kennyjpowers/claude-flow.git","type":"git"},"_npmVersion":"11.6.3","description":"Workflow orchestration for Claude Code - seamless end-to-end feature development workflow","directories":{},"_nodeVersion":"22.14.0","dependencies":{"claudekit":"^0.9.0","update-notifier":"^7.0.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"semantic-release":"^25.0.2","@semantic-release/git":"^10.0.1","@semantic-release/npm":"^13.1.2","@semantic-release/changelog":"^6.0.3"},"_npmOperationalInternal":{"tmp":"tmp/claudeflow_1.2.0_1763803713180_0.6195954348212087","host":"s3://npm-registry-packages-npm-production"}},"2.0.0":{"name":"@33strategies/claudeflow","version":"2.0.0","description":"Workflow orchestration for AI-assisted development - seamless end-to-end feature development workflow","keywords":["claude","claude-code","workflow","orchestration","ai-assisted-development","cli","automation"],"author":{"name":"Kenneth Priester","email":"33strategies@duck.com"},"license":"MIT","repository":{"type":"git","url":"git+https://github.com/kennyjpowers/claude-flow.git"},"bugs":{"url":"https://github.com/kennyjpowers/claude-flow/issues"},"homepage":"https://claudeflow.dev","publishConfig":{"access":"public"},"bin":{"claudeflow":"bin/claudeflow.js"},"main":"./lib/index.js","engines":{"node":">=20.0.0"},"dependencies":{"update-notifier":"^7.0.0"},"devDependencies":{"@semantic-release/changelog":"^6.0.3","@semantic-release/git":"^10.0.1","@semantic-release/npm":"^13.1.2","semantic-release":"^25.0.2"},"scripts":{"test":"echo 'Tests coming in Phase 2'","prepublishOnly":"node scripts/verify-files.js"},"type":"module","gitHead":"9ac902fd28c65ca5bb0c441a922a3d9829ff3987","_id":"@33strategies/claudeflow@2.0.0","_nodeVersion":"22.21.1","_npmVersion":"11.6.3","dist":{"integrity":"sha512-aV82kyuDObusjzEpRNYGlZpipqiF0VEL3Xt1/GBadm1uTPsy/xPd1K6BwfdmBFmXt+fU5UdVRu9rGpfEihszUQ==","shasum":"e2dec224bb404ece47208b22b119ad123943603b","tarball":"https://registry.npmjs.org/@33strategies/claudeflow/-/claudeflow-2.0.0.tgz","fileCount":37,"unpackedSize":277215,"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@33strategies%2fclaudeflow@2.0.0","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEQCIGN83pHq/NN1mowMEs6/82Gjajd593Vu57DJaOVaZE/wAiBk2oRAKah8B23pl3RixwxFlWz50PBSTNHEnESLuJPUAQ=="}]},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:c325db07-78d1-4682-bfb2-b13060d23940"}},"directories":{},"maintainers":[{"name":"kjpriester","email":"kennethjpriester@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/claudeflow_2.0.0_1767925101374_0.5654454481579949"},"_hasShrinkwrap":false}},"time":{"created":"2025-11-22T03:52:49.689Z","modified":"2026-01-09T02:18:21.852Z","1.0.1":"2025-11-22T03:52:49.957Z","1.1.0":"2025-11-22T04:25:09.278Z","1.1.1":"2025-11-22T06:03:10.642Z","1.1.2":"2025-11-22T06:08:13.465Z","1.2.0":"2025-11-22T09:28:33.417Z","2.0.0":"2026-01-09T02:18:21.520Z"},"bugs":{"url":"https://github.com/kennyjpowers/claude-flow/issues"},"author":{"name":"Kenneth Priester","email":"33strategies@duck.com"},"license":"MIT","homepage":"https://claudeflow.dev","keywords":["claude","claude-code","workflow","orchestration","ai-assisted-development","cli","automation"],"repository":{"type":"git","url":"git+https://github.com/kennyjpowers/claude-flow.git"},"description":"Workflow orchestration for AI-assisted development - seamless end-to-end feature development workflow","maintainers":[{"name":"kjpriester","email":"kennethjpriester@gmail.com"}],"readme":"# claudeflow - Workflow Orchestration for AI-Assisted Development\n\n[![npm version](https://img.shields.io/npm/v/@33strategies/claudeflow.svg)](https://www.npmjs.com/package/@33strategies/claudeflow)\n[![npm downloads](https://img.shields.io/npm/dm/@33strategies/claudeflow.svg)](https://www.npmjs.com/package/@33strategies/claudeflow)\n[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n[![Node Version](https://img.shields.io/badge/node-%3E%3D20-brightgreen.svg)](https://nodejs.org/)\n\nWorkflow commands for seamless end-to-end feature development with AI coding assistants. Works with Claude Code, OpenCode, and other AI development tools.\n\n## What's New in v2\n\n**claudeflow v2.0.0** is a major release with breaking changes:\n\n- **Standalone package** - No external dependencies (ClaudeKit/STM removed)\n- **Simplified installation** - Just `npm install` and `claudeflow setup`\n- **Tool-agnostic** - Works with Claude Code, OpenCode, and other AI tools\n- **Lower requirements** - Node.js 20+ (down from 22.14+)\n- **Streamlined workflow** - Focus on workflow commands only\n\nSee [CHANGELOG.md](CHANGELOG.md) for full details.\n\n## Quick Start\n\n### Installation\n\n> **Prerequisites:** Node.js 20+ \n> Check version: `node --version` | Install: https://nodejs.org \n\nInstall claudeflow globally via your preferred package manager:\n\n#### npm\n```bash\nnpm install -g @33strategies/claudeflow\n```\n\n#### yarn\n```bash\nyarn global add @33strategies/claudeflow\n```\n\n#### pnpm\n```bash\npnpm add -g @33strategies/claudeflow\n```\n\n### Setup\n\nAfter installation, run the setup command:\n\n```bash\nclaudeflow setup\n```\n\nChoose your installation mode:\n- **1) Global** - Install to `~/.claude/` (available in all projects)\n- **2) Project** - Install to `./.claude/` (this project only)\n\n**Quick decision**:\n- **Solo developer or want commands everywhere?** → Global mode\n- **Team project or want version control?** → Project mode\n- **Both?** → You can do both! They work together via configuration hierarchy.\n\nThe setup will:\n1. Check prerequisites (Node.js 20+, npm)\n2. Copy custom workflow commands to your chosen location\n3. Set up configuration files\n\n## What This Package Provides\n\nclaudeflow provides **workflow commands** for AI-assisted feature development:\n\n### Custom Workflow Commands\n- **/brainstorm:start**: Structured brainstorming with comprehensive documentation\n- **/brainstorm:clarify**: Resolve open questions interactively\n- **/brainstorm:spec**: Transform brainstorm into validated specification\n- **/feedback:add**: Quick capture of feedback items after testing\n- **/feedback:resolve**: Batch analyze and resolve pending feedback\n- **/spec:doc-update**: Parallel documentation review based on specs\n\n### Enhanced Spec Commands\n- **/spec:create**: Detects output path and creates specs in feature directories\n- **/spec:decompose**: Incremental mode preserves completed work\n- **/spec:execute**: Session resume capability with implementation tracking\n- **/spec:migrate**: Migrates existing specs to feature-directory structure\n\n### Key Features\n- Complete end-to-end workflow from brainstorming to deployment\n- Task tracking via `doc/specs/<slug>/03-tasks.md`\n- Session continuity across implementation runs\n- Interactive question resolution in specifications\n\n### Verify Installation\n\nCheck that everything is set up correctly:\n\n```bash\nclaudeflow doctor\n```\n\nThis diagnostic command checks:\n- Node.js version (need 20+)\n- npm availability\n- Claude Code CLI (optional - other AI tools supported)\n- .claude/ directory structure\n- Command files presence\n\n### Troubleshooting\n\n#### \"Command not found: claudeflow\"\n- Ensure npm global bin is in your PATH\n- Try: `npm list -g @33strategies/claudeflow`\n- Reinstall: `npm install -g @33strategies/claudeflow`\n\n#### \"Commands not loading in Claude Code\"\n- Run: `claudeflow doctor`\n- Verify files exist in `~/.claude/commands/` (global) or `./.claude/commands/` (project)\n- Restart Claude Code\n\n#### Installation Issues\nRun the diagnostic command for detailed information:\n```bash\nclaudeflow doctor\n```\n\n### Migration from install.sh\n\nIf you previously used the bash script installation:\n\n1. **Uninstall old version:**\n   ```bash\n   # Global installation\n   rm -rf ~/.claude\n\n   # OR Project installation\n   rm -rf .claude\n   ```\n\n2. **Install via npm:**\n   ```bash\n   npm install -g @33strategies/claudeflow\n   ```\n\n3. **Run setup:**\n   ```bash\n   # Global (if you used install.sh user)\n   claudeflow setup --global\n\n   # OR Project (if you used install.sh project)\n   claudeflow setup --project\n   ```\n\n4. **Verify installation:**\n   ```bash\n   claudeflow doctor\n   ```\n\n**Note:** The migration only affects the installation method, not your feature work or task data.\n\n### Package Security\n\nclaudeflow is published with npm provenance attestations and SLSA Level 2 compliance. All releases are built and published via GitHub Actions with cryptographic verification.\n\nFor details on verifying package authenticity, supply chain security, and security best practices, see **[docs/SECURITY.md](docs/SECURITY.md)**.\n\n### Update Management\n\nclaudeflow checks for updates automatically once per week (every 7 days). This check runs in the background and doesn't block command execution.\n\n**Manual update check:**\n```bash\nnpm outdated -g @33strategies/claudeflow\n```\n\n**When updates are available**, you'll see a notification:\n```\n╭───────────────────────────────────────────────────╮\n│                                                   │\n│   Update available: 1.3.0                        │\n│   Current version:  1.2.0                        │\n│   Run: npm install -g @33strategies/claudeflow   │\n│                                                   │\n╰───────────────────────────────────────────────────╯\n```\n\n**To update:**\n```bash\n# npm\nnpm update -g @33strategies/claudeflow\n\n# yarn\nyarn global upgrade @33strategies/claudeflow\n\n# pnpm\npnpm update -g @33strategies/claudeflow\n```\n\n## Document Organization\n\nAll documents related to a feature are organized in a single directory:\n\n```\ndoc/specs/\n└── <feature-slug>/\n    ├── 01-brainstorm.md        # Brainstorming and research\n    ├── 02-specification.md     # Validated specification\n    ├── 03-tasks.md             # Task breakdown\n    ├── 04-implementation.md    # Implementation summary\n    └── 05-feedback.md          # Post-implementation feedback log\n```\n\n**Benefits:**\n- All related documents in one place\n- Clear lifecycle progression (01 → 02 → 03 → 04)\n- Easy to find and navigate\n- Git-friendly tracking\n\n**Example:**\n```\ndoc/specs/add-user-auth-jwt/\n├── 01-brainstorm.md        # Created by /brainstorm:start\n├── 02-specification.md     # Created by /brainstorm:spec (after /brainstorm:clarify)\n├── 03-tasks.md             # Created by /spec:decompose\n├── 04-implementation.md    # Created by /spec:execute\n└── 05-feedback.md          # Created by /feedback:add (after testing)\n```\n\n## Repository Structure\n\n```\nclaudeflow/ (@33strategies/claudeflow npm package)\n├── package.json                      # npm package metadata\n├── bin/\n│   └── claudeflow.js                 # CLI entry point\n├── lib/\n│   ├── setup.js                      # Installation logic\n│   └── doctor.js                     # Diagnostic command\n├── scripts/\n│   └── verify-files.js               # Pre-publish file verification\n│\n├── .claude/                          # Custom configuration (distributed in package)\n│   ├── commands/                     # Custom slash commands\n│   │   ├── brainstorm/               # Brainstorming workflow commands\n│   │   │   ├── start.md              # Structured brainstorming workflow\n│   │   │   ├── clarify.md            # Resolve open questions\n│   │   │   └── spec.md               # Transform brainstorm to spec\n│   │   └── spec/\n│   │       ├── create.md             # Enhanced spec creation\n│   │       ├── decompose.md          # Incremental task breakdown\n│   │       ├── execute.md            # Session-aware implementation\n│   │       ├── feedback.md           # Post-implementation feedback\n│   │       ├── doc-update.md         # Documentation review\n│   │       └── migrate.md            # Spec structure migration\n│   ├── settings.json.example         # Example configuration\n│   └── README.md                     # Component documentation\n│\n├── .claude-plugin/                   # Plugin metadata\n│   └── plugin.json                   # Package metadata\n│\n├── templates/                        # Configuration templates\n│   ├── project-config/               # Project-level templates\n│   │   ├── settings.json             # Team settings\n│   │   ├── settings.local.json.example\n│   │   ├── CLAUDE.md                 # Project instructions\n│   │   ├── CLAUDE.local.md.example\n│   │   └── .gitignore.example\n│   └── user-config/                  # User-level templates\n│       ├── settings.json             # Personal global settings\n│       └── CLAUDE.md                 # Personal preferences\n│\n├── docs/                             # Documentation\n│   ├── DESIGN_RATIONALE.md          # Design validation & best practices\n│   └── ...\n│\n├── .github/\n│   └── workflows/\n│       └── release.yml               # CI/CD automation\n├── .releaserc.json                   # Semantic-release config\n├── .npmignore                        # Package exclusion rules\n├── LICENSE                           # MIT License\n├── CHANGELOG.md                      # Version history (auto-generated)\n└── README.md                         # This file\n```\n\n## Configuration\n\n### Configuration Hierarchy\n\nClaude Code uses a 5-tier precedence system:\n\n1. **Enterprise policies** (highest) - IT-managed, cannot be overridden\n2. **CLI arguments** - Temporary session overrides\n3. **Local settings** (`.claude/settings.local.json`) - Personal, gitignored\n4. **Project settings** (`.claude/settings.json`) - Team, committed\n5. **User settings** (`~/.claude/settings.json`) - Personal global defaults\n\n## Available Commands\n\n#### /brainstorm:start\nStructured brainstorming workflow that enforces complete investigation for any code-change task (bug fix or feature). Produces comprehensive brainstorm documentation including:\n- Intent & assumptions\n- Pre-reading log\n- Codebase mapping\n- Root cause analysis (for bugs)\n- Research findings\n- Clarification questions\n\n**Usage:** `/brainstorm:start Fix chat UI auto-scroll bug when messages exceed viewport height`\n\n#### /brainstorm:clarify\nResolve open questions in a brainstorm or specification document interactively. This command:\n1. Reads the document and detects unanswered questions\n2. Presents each question with context and options\n3. Records answers in strikethrough format (audit trail)\n4. Re-validates and loops until all questions resolved\n5. Shows progress: \"Question 3 of 12\"\n\n**Key Features:**\n- Supports multi-select for questions requiring multiple choices\n- Detects external edits to prevent data loss\n- Backward compatible (skips if no questions exist)\n- Re-entrant (skips already-answered questions)\n- Save-as-you-go for recoverability\n\n**Usage:** `/brainstorm:clarify doc/specs/<slug>/01-brainstorm.md`\n\n**Example:**\n```bash\n/brainstorm:clarify doc/specs/my-feature/01-brainstorm.md\n# → System detects 5 open questions\n# ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n# Question 1 of 5\n# ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n# Package Manager Support\n# → User selects: npm, yarn, pnpm (all three)\n# → Document updated with strikethrough answer\n# → Continues with questions 2-5\n# → Final summary shows 5 questions resolved\n```\n\n**Answer Format (Audit Trail):**\n\nQuestions are marked as resolved using strikethrough format:\n\nBefore:\n```markdown\n1. **ClaudeKit Version Compatibility**\n   - Option A: Pin exact version\n   - Option B: Use caret range\n```\n\nAfter:\n```markdown\n1. ~~**ClaudeKit Version Compatibility**~~ (RESOLVED)\n   **Answer:** Use caret range (^1.0.0)\n   **Rationale:** Automatic updates, test compatibility in CI/CD\n\n   Original context preserved:\n   - Option A: Pin exact version\n   - Option B: Use caret range\n```\n\nThis format provides a complete audit trail showing both the original question and the final decision.\n\n#### /brainstorm:spec\nTransform a brainstorm document into a validated, implementation-ready specification. This command:\n1. Reads and synthesizes the brainstorm document\n2. Interactively gathers decisions from the user\n3. Creates a detailed specification using `/spec:create`\n4. Validates it with `/spec:validate`\n5. Presents a summary with next steps\n\n**Usage:** `/brainstorm:spec doc/specs/<slug>/01-brainstorm.md`\n\n**Note:** Run `/brainstorm:clarify` first to resolve any open questions before creating the specification.\n\n#### /feedback:add\nQuick capture of feedback items after manual testing. This command:\n1. Locates the specification (auto-selects most recent if not specified)\n2. Creates or loads `05-feedback.md` file\n3. Loops to capture multiple feedback items\n4. Saves each item immediately (save-as-you-go)\n5. Presents summary and next steps\n\n**Usage:** `/feedback:add` or `/feedback:add doc/specs/my-feature/02-specification.md`\n\n**Example:**\n```bash\n/feedback:add\n# → Auto-selects most recent specification\n# → \"What feedback do you have?\"\n# → User enters: \"Login button should be more prominent\"\n# → FB-1 added.\n# → \"What feedback do you have?\" (loop continues)\n# → User selects \"Done\"\n# → Summary: 3 feedback item(s) added\n# → Next: Run /feedback:resolve to analyze and resolve\n```\n\n#### /feedback:resolve\nBatch analyze and resolve all pending feedback items. This command:\n1. Locates the feedback file (auto-selects most recent if not specified)\n2. Loads all pending items from `05-feedback.md`\n3. Analyzes all items in parallel using domain experts\n4. Presents each item with analysis for user decision (implement/defer/out-of-scope)\n5. Updates specification with approved changes\n6. Logs resolutions in `05-feedback.md`\n\nIntegrates with incremental `/spec:decompose` and resume `/spec:execute` for seamless iteration.\n\n**Usage:** `/feedback:resolve` or `/feedback:resolve doc/specs/my-feature/05-feedback.md`\n\n**Example:**\n```bash\n/feedback:resolve\n# → Auto-selects most recent feedback file\n# → \"3 pending feedback item(s)\"\n# → Analyzes all items in parallel\n# → Presents FB-1 with analysis\n# → User selects: \"Implement\"\n# → Presents FB-2 with analysis\n# → User selects: \"Defer\" (reason: \"Not enough time\")\n# → Presents FB-3 with analysis\n# → User selects: \"Out of scope\"\n# → Updates specification with FB-1 changes\n# → Summary: 1 implement, 1 defer, 1 out of scope\n# → Next: Run /spec:decompose to create new tasks\n```\n\n#### /spec:doc-update\nReview all documentation to identify what needs to be updated based on a new specification file. Launches parallel documentation expert agents to review each doc file for:\n- Deprecated content\n- Content requiring updates\n- Missing content for new features\n\n**Usage:** `/spec:doc-update doc/specs/text-generator-spec.md`\n\n### Enhanced Spec Commands\n\n#### /spec:create\nCreates specifications in feature directories at `doc/specs/<slug>/02-specification.md`.\n\n**Usage:** `/spec:create Add user authentication with JWT tokens`\n\n#### /spec:decompose\nBreaks down specifications into tasks with **incremental mode** that preserves completed work. Creates task breakdown in `doc/specs/<slug>/03-tasks.md`.\n\n**Usage:** `/spec:decompose doc/specs/add-user-auth/02-specification.md`\n\n**Incremental Mode:** Automatically detects when spec changelog has been updated and creates only new tasks for changes.\n\n#### /spec:execute\nImplements tasks with **session resume capability**. Reads implementation summary to skip completed tasks and continue from previous progress. Creates/updates `doc/specs/<slug>/04-implementation.md`.\n\n**Usage:** `/spec:execute doc/specs/add-user-auth/02-specification.md`\n\n**Session Continuity:** When you run `/spec:execute` multiple times on the same spec, it reads `04-implementation.md` to understand what work has already been completed. This allows you to:\n- Work on large features across multiple sessions without re-doing completed tasks\n- Return to implementation after testing/feedback cycles\n- Maintain a complete history of all sessions (Session 1, Session 2, etc.)\n- Seamlessly integrate feedback workflow: implement → test → `/feedback:add` → `/feedback:resolve` → `/spec:decompose` (incremental) → `/spec:execute` (resume)\n\n#### /spec:migrate\nMigrates existing specs from flat structure to feature-directory structure.\n\n**Usage:** `/spec:migrate`\n\n## Standard Workflow\n\nThis repository implements a complete end-to-end workflow for feature development:\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                   BRAINSTORM PHASE                              │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n                 /brainstorm:start <task-brief>\n                   (Custom Command)\n                              │\n                   Creates brainstorm doc\n                   with research & analysis\n                              │\n                              ▼\n               /brainstorm:clarify <brainstorm-doc>\n                   (Resolve open questions)\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────────┐\n│                   SPECIFICATION PHASE                           │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n          /brainstorm:spec <brainstorm-doc>\n          (Custom, calls /spec:create & /spec:validate)\n                              │\n              Creates validated specification\n                              │\n                              ▼\n            /spec:decompose <spec-file>\n                              │\n              Breaks spec into tasks\n              (creates 03-tasks.md)\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────────┐\n│                  IMPLEMENTATION PHASE                           │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n            /spec:execute <spec-file>\n                              │\n              Implements tasks\n              (updates 03-tasks.md status)\n                              │\n                              ▼\n                    Manual Testing\n                              │\n                   Discover issues or\n                   improvement opportunities\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────────┐\n│                     FEEDBACK PHASE                              │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n              /feedback:add (capture items)\n                              │\n              Loop to add multiple items\n              (save-as-you-go)\n                              │\n                              ▼\n             /feedback:resolve (batch analyze)\n                              │\n              For each pending item:\n              • Parallel analysis\n              • User decision\n                              │\n                   ┌──────────┴──────────┬────────────┐\n                   │                     │            │\n               Implement Now           Defer     Out of Scope\n                   │                     │            │\n        Update spec changelog       Log for later    Log only\n                   │                     │            │\n                   └──────────┬──────────┴────────────┘\n                              │\n                              ▼\n       /spec:decompose (incremental - if any \"implement\")\n                              │\n       /spec:execute (resume)\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────────┐\n│                    COMPLETION PHASE                             │\n└─────────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n           /spec:doc-update <spec-file>\n                              │\n        Reviews & updates documentation\n                              │\n                              ▼\n               git commit & push\n                              │\n                              ▼\n                          DONE! 🎉\n```\n\n### Key Workflow Steps\n\n1. **Brainstorm** → Comprehensive investigation and research\n2. **Clarify** → Resolve open questions interactively\n3. **Specification** → Validated, implementation-ready spec\n4. **Decomposition** → Tasks broken down in `03-tasks.md`\n5. **Implementation** → Iterative execution with task status tracking\n6. **Feedback** → Process post-implementation feedback with structured decisions (implement/defer/out-of-scope)\n7. **Completion** → Documentation updates and git workflow\n\n## Usage Examples\n\n### Complete Workflow Example\n\n```bash\n# Step 1: Start with brainstorming\n/brainstorm:start Add user authentication with JWT tokens\n# → Creates: doc/specs/add-user-auth-jwt/01-brainstorm.md\n\n# Step 2: Resolve any open questions\n/brainstorm:clarify doc/specs/add-user-auth-jwt/01-brainstorm.md\n# → Interactively resolves all open questions\n\n# Step 3: Transform to validated specification\n/brainstorm:spec doc/specs/add-user-auth-jwt/01-brainstorm.md\n# → Creates: doc/specs/add-user-auth-jwt/02-specification.md (validated & complete)\n\n# Step 4: Break down into tasks\n/spec:decompose doc/specs/add-user-auth-jwt/02-specification.md\n# → Creates: doc/specs/add-user-auth-jwt/03-tasks.md\n\n# Step 5: Start implementation\n/spec:execute doc/specs/add-user-auth-jwt/02-specification.md\n# → Implements tasks, updates status in 03-tasks.md\n\n# Step 6: Continue implementing (loop back to step 5 if needed)\n/spec:execute doc/specs/add-user-auth-jwt/02-specification.md\n# → Resume mode: skips completed work\n\n# Step 7: Manual testing (discover feedback items)\n# Test the implemented feature manually\n\n# Step 8: Capture feedback items\n/feedback:add doc/specs/add-user-auth-jwt/02-specification.md\n# → Loop to capture multiple feedback items\n# → Each item saved immediately\n\n# Step 9: Resolve feedback (batch analyze and decide)\n/feedback:resolve doc/specs/add-user-auth-jwt/05-feedback.md\n# → Analyzes all pending items in parallel\n# → Interactive decisions: implement/defer/out-of-scope\n# → Updates spec with approved changes\n\n# Step 10: If any \"Implement\" decisions, run incremental decompose\n/spec:decompose doc/specs/add-user-auth-jwt/02-specification.md\n# → Incremental mode: preserves completed tasks, creates only new ones\n\n# Step 11: Resume implementation for new tasks\n/spec:execute doc/specs/add-user-auth-jwt/02-specification.md\n\n# Step 12: Update documentation and commit\n/spec:doc-update doc/specs/add-user-auth-jwt/02-specification.md\n# git add . && git commit -m \"feat: add user authentication\"\n# git push\n\n# All documents for this feature are now in: doc/specs/add-user-auth-jwt/\n```\n\n### Quick Start (Skip Brainstorming)\n\nIf you already know what you need:\n\n```bash\n# Start directly with spec creation\n/spec:create Add user authentication with JWT tokens\n\n# Then follow steps 4-12 above\n```\n\n### Migrating Existing Specs\n\nIf you have specs in the old flat structure:\n\n```bash\n# Migrate all existing specs to new structure\n/spec:migrate\n\n# This will:\n# - Move specs/*.md to doc/specs/<slug>/02-specification.md\n# - Move specs/*-tasks.md to doc/specs/<slug>/03-tasks.md\n# - Move docs/ideation/*.md to doc/specs/<slug>/01-brainstorm.md\n# - Generate migration report\n```\n\n### Updating Documentation After Implementation\n\n```bash\n# After implementing a feature via a spec\n/spec:doc-update doc/specs/add-user-auth-jwt/02-specification.md\n\n# This will:\n# - Review all docs for outdated content\n# - Identify missing documentation for new features\n# - Provide prioritized recommendations\n```\n\n## Settings Management\n\n**Project Settings** (`.claude/settings.json` - committed):\n```json\n{\n  \"permissions\": {\n    \"allow\": [\"Read\", \"Edit\", \"Bash(git:*)\"],\n    \"deny\": [\".env\", \"**/*.key\", \"secrets/\"]\n  }\n}\n```\n\n**Personal Overrides** (`.claude/settings.local.json` - gitignored):\n- Use for personal preferences that shouldn't be committed\n\n## Best Practices\n\n### 1. Security First\n- Never commit secrets to `.claude/settings.json`\n- Use environment variable references: `\"API_KEY\": \"${API_KEY}\"`\n- Keep `.env` files gitignored\n\n### 2. Team Collaboration\n- Commit `.claude/settings.json` and `CLAUDE.md` to git\n- Gitignore `.claude/settings.local.json` and `CLAUDE.local.md`\n\n### 3. Context Optimization\n- Keep CLAUDE.md focused and concise\n- Break large tasks into smaller steps\n\n## Resources\n\n### Documentation\n- [Installation Guide](docs/INSTALLATION_GUIDE.md) - When to use global vs project installation\n- [Setup Guide](docs/SETUP_GUIDE.md) - Detailed setup instructions\n- [Design Rationale](docs/DESIGN_RATIONALE.md) - Design validation and best practices\n- [Feedback Workflow Guide](docs/guides/feedback-workflow-guide.md) - Complete guide to post-implementation feedback\n- [GitHub Issues](https://github.com/kennyjpowers/claude-flow/issues) - Report problems\n\n## Contributing\n\nContributions welcome! Please:\n1. Follow existing patterns and structure\n2. Test changes thoroughly\n3. Update documentation\n4. Submit PRs with clear descriptions\n\n## License\n\nMIT License - feel free to use and modify for your projects.\n\n## Acknowledgments\n\n- **Anthropic** - Claude Code CLI and AI development\n- Community contributors and examples\n","readmeFilename":"README.md"}