Menu
Full autonomous engineering workflow using swarm mode for parallel execution
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks 'what should we build', 'help me think through X', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don't explicitly ask to brainstorm.
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/ for accuracy, when a recently solved problem contradicts an existing learning, when pattern docs no longer reflect current code, or when multiple docs seem to cover the same topic and might benefit from consolidation.
Document a recently solved problem to compound your team's knowledge
Generate and critically evaluate grounded improvement ideas for the current project. Use when asking what to improve, requesting idea generation, exploring surprising improvements, or wanting the AI to proactively suggest strong project directions before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on this project', 'surprise me with improvements', 'what would you change', or any request for AI-generated project improvement suggestions rather than refining the user's own idea.
Transform feature descriptions or requirements into structured implementation plans grounded in repo patterns and research. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Use for plan deepening when the user says 'deepen the plan', 'deepen my plan', 'deepening pass', or uses 'deepen' in reference to a plan. Best when requirements are at least roughly defined; for exploratory or ambiguous requests, prefer ce-brainstorm first.
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
| name | slfg |
| description | Full autonomous engineering workflow using swarm mode for parallel execution |
| argument-hint | [feature description] |
| disable-model-invocation | true |
Swarm-enabled LFG. Run these steps in order, parallelizing where indicated. Do not stop between steps — complete every step through to the end.
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 — Record the plan file path from docs/plans/ for steps 4 and 6./ce-work — Use swarm mode: Make a Task list and launch an army of agent swarm subagents to build the planAfter work completes, launch steps 4, 5, and 6 as parallel swarm agents (all read-only, safe to run concurrently):
/ce-review mode:report-only plan:<plan-path-from-step-2> — spawn as background Task agent/compound-engineering-test-browser — spawn as background Task agent/unslop — spawn as background Task agent (read-only de-slop report)Wait for all three to complete before continuing.
/ce-review mode:autofix plan:<plan-path-from-step-2> — run sequentially after the parallel phase so it can safely mutate the checkout, apply safe_auto fixes, and emit residual todos for step 8/unslop fix — run sequentially after ce-review autofix to strip AI slop (commented-out code, filler comments, stale TODOs)/observe on the areas of code that were changed — analyze patterns in the modified files to capture what was done and how./learn — extract reusable patterns from this session into project instincts./compound-engineering-todo-resolve — resolve findings, compound on learnings, clean up completed todos/compound-engineering-feature-video — record the final walkthrough and add to PR<promise>DONE</promise> when video is in PRStart with step 1 now.