From rockets-sdk-config
This skill should be used when generating an entire Rockets SDK project from a spec, bootstrapping multiple entities at once, or when the user has a plan.json file. Orchestrates wave-based generation with dependency ordering and validation gates. Works sequentially by default; supports Agent Teams for parallel execution. Requires rockets-crud-generator.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rockets-sdk-config:rockets-orchestratorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generates complete Rockets SDK projects from a parsed spec — multiple entities, relations, ACL — with automatic dependency ordering, validation gates, and progress tracking.
Generates complete Rockets SDK projects from a parsed spec — multiple entities, relations, ACL — with automatic dependency ordering, validation gates, and progress tracking.
Requires:
rockets-crud-generatormust be installed as a sibling skill.
# Sequential mode (no Agent Teams needed)
node skills/rockets-orchestrator/scripts/orchestrate.js \
--project ./apps/api \
--spec .rockets/plan.json
# Dry run (show waves without executing)
node skills/rockets-orchestrator/scripts/orchestrate.js \
--project ./apps/api \
--spec .rockets/plan.json \
--dry-run
# Resume from last checkpoint
node skills/rockets-orchestrator/scripts/orchestrate.js \
--project ./apps/api \
--resume
Entities are sorted by dependency graph (relations). Entities with no dependencies are generated first. Entities that depend on others wait until their dependencies are done.
Wave 1: Category, Tag (no deps)
Wave 2: Product (depends on Category)
Wave 3: ProductTag (depends on Product, Tag)
Each wave runs:
generate.js for each entity in the waveintegrate.js writes files + wires into projectvalidate.js checks structural rulesAfter all waves complete and build passes:
typeorm migration:generate (requires a running database) — ~98% confidenceAfter all waves + migration:
validate.js --build for full TypeScript compilation checksmoke-test-endpoints.js for HTTP endpoint testingProgress is saved to .rockets/state.json in the project directory:
{
"startedAt": "2026-02-25T10:00:00Z",
"waves": [
{ "index": 0, "entities": ["category", "tag"], "status": "completed" },
{ "index": 1, "entities": ["product"], "status": "in_progress" }
],
"completedEntities": ["category", "tag"],
"failedEntities": [],
"currentWave": 1
}
Use --resume to continue from the last checkpoint.
.rockets/plan.json)The plan.json is created by the rockets-planner agent. See agents/rockets-planner.md for the full schema and rules.
Each entity in plan.json follows the same config schema as rockets-crud-generator (see skills/rockets-crud-generator/SKILL.md). The orchestrator passes each entity config directly to generate.js.
When CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is enabled, the /rockets-from-doc command creates a team instead of running the script:
| Role | Model | Responsibility |
|---|---|---|
| Lead | opus | Parse spec, create tasks with dependencies, coordinate waves |
| Generator | sonnet | Run generate.js + integrate.js per entity |
| Reviewer | haiku | Validate against 9 Engineering Rules (see rockets-auto-reviewer) |
| Tester | sonnet | Run validate.js + smoke-test-endpoints.js |
| Builder | sonnet | Fix build errors (max 3 retries) |
Teammates communicate directly — Reviewer sends fixes to Generator without going through Lead. Tasks use the built-in task list with blockedBy dependencies matching the topological sort.
| Script | Purpose | Tokens |
|---|---|---|
orchestrate.js | Batch generation with waves + migration (sequential fallback) | 0 |
| Flag | Description |
|---|---|
--project <path> | Path to the project root (required) |
--spec <path> | Path to plan.json (default: <project>/.rockets/plan.json) |
--dry-run | Show waves without executing |
--resume | Resume from .rockets/state.json |
--skip-smoke | Skip endpoint smoke test at end |
--skip-migration | Skip migration generation step |
--validate-only | Only run validation (no generation) |
{
"success": true,
"waves": [
{
"index": 0,
"entities": ["category", "tag"],
"status": "completed",
"generated": 2,
"validated": true
}
],
"summary": {
"totalEntities": 4,
"completed": 4,
"failed": 0,
"buildPassed": true,
"smokeTestPassed": true
}
}
npx claudepluginhub btwld/skills --plugin rockets-sdk-configCreates detailed engineering implementation plans with team orchestration for multi-step projects requiring task dependencies and parallel execution. Uses specialized agents for Django, Python, FastAPI, React, and Playwright.
Drives long-running, multi-session development with a Project → Sprint → Task hierarchy, isolated worktrees, review round-loops, governance-as-code, and orchestrator-readable state. Designed for /loop, autoresearch:ship, and goal-driven workflows.
Reads a multi-step plan document, decomposes it into steps, and emits ready-to-paste /orchestrate custom prompts with per-step agent chains from the ECC catalogue. Generative only — does not invoke /orchestrate itself.