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.
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. 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', 'plan a trip', 'create a study plan', or when a brainstorm/requirements document is ready for 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.
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
Use when starting any conversation - establishes how to find and use skills, requiring skill tool invocation before ANY response including clarifying questions
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
| 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/systematic:deepen-plan
deepen-plan workflow only if the plan is Standard or Deep, touches a high-risk area (auth, security, payments, migrations, external APIs, significant rollout concerns), or still has obvious confidence gaps in decisions, sequencing, system-wide impact, risks, or verificationdeepen-plan workflow, confirm the plan was deepened or explicitly judged sufficiently grounded before moving on/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 5 and 6 as parallel swarm agents (both only need code to be written):
/ce:review mode:report-only — spawn as background Task agent/systematic:test-browser — spawn as background Task agentWait for both to complete before continuing.
/ce:review mode:autofix — run sequentially after the parallel phase so it can safely mutate the checkout, apply safe_auto fixes, and emit residual todos for step 8/systematic:todos (resolve) — resolve findings, compound on learnings, clean up completed todos<promise>DONE</promise> when work is completeStart with step 1 now.