Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
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-engineeringHow this skill is triggered — by the user, by Claude, or both
Slash command
/compound-engineering:lfgThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Orchestrates full autonomous engineering workflow: plan feature with /ce-plan, implement via /ce-work, review, clean slop, observe/learn patterns, resolve todos, browser test, record video. Use for end-to-end feature builds from description.
Executes full autonomous software engineering workflow using swarm mode for parallel planning, coding, review, testing, autofix, todo resolution, and feature video in PR.
Generates feature specs, implementation plans with task checklists, and project loop infrastructure via interactive user interviews on scope, risk tolerance, and validation.
Share bugs, ideas, or general feedback.
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.