john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: merge deepen-plan into ce:plan as automatic confidence check (#404)

Browse Source
This commit is contained in:
Trevin Chow
2026-03-26 22:15:58 -07:00
committed by GitHub
parent 5e6cd5c909
commit da390a65a2
16 changed files with 717 additions and 468 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
plugins/compound-engineering/skills/lfg/SKILL.md
View File

@@ -5,7 +5,7 @@ argument-hint: "[feature description]"
disable-model-invocation: true
---
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, and step 3 when warranted) MUST be completed and verified BEFORE any work begins. Violating this order produces bad output.
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.
1. **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.
@@ -13,24 +13,18 @@ CRITICAL: You MUST execute every step below IN ORDER. Do NOT skip any required s
GATE: STOP. 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.
3. **Conditionally** run `/compound-engineering:deepen-plan`
3. `/ce:work`
Run the `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 verification.
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.
GATE: STOP. If you ran the `deepen-plan` workflow, confirm the plan was deepened or explicitly judged sufficiently grounded. If you skipped it, briefly note why and proceed to step 4.
4. `/ce:review mode:autofix`
4. `/ce:work`
5. `/compound-engineering:todo-resolve`
GATE: STOP. Verify that implementation work was performed - files were created or modified beyond the plan. Do NOT proceed to step 5 if no code changes were made.
6. `/compound-engineering:test-browser`
5. `/ce:review mode:autofix`
7. `/compound-engineering:feature-video`
6. `/compound-engineering:todo-resolve`
7. `/compound-engineering:test-browser`
8. `/compound-engineering:feature-video`
9. Output `<promise>DONE</promise>` when video is in PR
8. 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.