From compound-engineering
Executes autonomous engineering workflow: plan feature with /ce:plan, implement via /ce:work, autofix review, resolve todos, browser test, feature video, and PR. For full-cycle software tasks.
npx claudepluginhub everyinc/compound-engineering-plugin --plugin compound-engineeringThis skill uses the workspace's default tool permissions.
CRITICAL: You MUST execute every step below IN ORDER. Do NOT skip any required step. Do NOT jump ahead to coding or implementation. The plan phase (step 2) MUST be completed and verified BEFORE any work begins. Violating this order produces bad output.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
CRITICAL: You MUST execute every step below IN ORDER. Do NOT skip any required step. Do NOT jump ahead to coding or implementation. The plan phase (step 2) MUST be completed and verified BEFORE any work begins. Violating this order produces bad output.
Optional: If the ralph-loop skill is available, run /ralph-loop:ralph-loop "finish all slash commands" --completion-promise "DONE". If not available or it fails, skip and continue to step 2 immediately.
/ce:plan $ARGUMENTS
GATE: STOP. If ce:plan reported the task is non-software and cannot be processed in pipeline mode, stop the pipeline and inform the user that LFG requires software tasks. Otherwise, verify that the ce:plan workflow produced a plan file in docs/plans/. If no plan file was created, run /ce:plan $ARGUMENTS again. Do NOT proceed to step 3 until a written plan exists. Record the plan file path — it will be passed to ce:review in step 4.
/ce:work
GATE: STOP. Verify that implementation work was performed - files were created or modified beyond the plan. Do NOT proceed to step 4 if no code changes were made.
/ce:review mode:autofix plan:<plan-path-from-step-2>
Pass the plan file path from step 2 so ce:review can verify requirements completeness.
/compound-engineering:todo-resolve
/compound-engineering:test-browser
/compound-engineering:feature-video
Output <promise>DONE</promise> when video is in PR
Start with step 2 now (or step 1 if ralph-loop is available). Remember: plan FIRST, then work. Never skip the plan.