cforge
v0.4.3
Published
Claude Code workflow orchestration engine
Maintainers
Readme
Stack Forge
Claude Code workflow orchestration engine. Composes existing plugins into a unified development workflow.
What it does
Stack Forge discovers your installed Claude Code plugins (Superpowers, feature-dev, code-review, etc.) and generates an orchestration workflow that chains them together automatically. It includes health checks to ensure providers are working correctly before starting a workflow.
Quick Start
# Install
npm install -g cforge
# Initialize (zero-config)
cforge init
# Start a workflow
cforge # default: feature
cforge feature "add auth" # explicit
cforge bugfix "fix login" # explicitHow it works
cforge initscans your system for installed plugins- Auto-installs missing required providers
- Runs health checks to verify providers are working
- Generates an orchestration skill + stage skills
cforgetriggers the orchestration skill- The skill forks subagents for each stage automatically
- Stages: Brainstorm → Spec → Plan → Build → Review → Release
- Implementation stage uses parallel execution for independent tasks
Parallel Implementation
The Implementation stage automatically detects independent tasks and executes them in parallel:
# tasks.md example
- [ ] Task 1: Modify src/discovery/scanner.ts
- [ ] Task 2: Modify src/generator/templates.ts
- [ ] Task 3: Modify src/cli/generate.ts
- [ ] Task 4: Modify src/discovery/scanner.ts (depends on Task 1)Automatic batching:
- Tasks 1, 2, 3 → Batch 1 (parallel, no file conflicts)
- Task 4 → Batch 2 (serial, depends on Task 1)
Benefits:
- 3x faster for independent tasks
- Automatic conflict detection
- Each task follows TDD workflow
- Full test suite validation at end
Commands
| Command | Description |
|---------|-------------|
| cforge init | Initialize Stack Forge (zero-config) |
| cforge [workflow] [desc] | Start or continue a workflow |
| cforge status | Show current workflow status |
| cforge healthcheck | Check health of installed providers |
| cforge update | Re-scan providers and update configuration |
| cforge generate | Regenerate all config files |
| cforge validate | Validate implementation against spec requirements |
| cforge reset | Reset Stack Forge to pre-initialization state |
Debug Mode
Set environment variable for verbose logging:
CFORGE_LOG_LEVEL=debug cforge <command>Supported Providers
| Capability | Default Provider | |------------|-----------------| | Brainstorm | Superpowers | | Specification | feature-dev | | Planning | Superpowers | | Implementation | Built-in | | Review | code-review | | Release | gstack | | Memory | claude-mem |
Architecture
cforge CLI
├── Provider Discovery (scan plugins)
├── Health Check (verify providers)
├── Config Generator (skills, commands, CLAUDE.md)
├── Schema Validation (Zod)
└── State Management (state.json with backup)
Claude Code Runtime
├── Orchestration Skill (state machine + fork)
│ └── Stage Skills (context: fork isolation)
└── Provider Delegation
├── Superpowers (brainstorm, planning)
├── feature-dev (specification)
├── code-review (review)
└── gstack (release)License
MIT
