fix: resolve first-run workflow failures (2.35.0)

- fix(lfg, slfg): make ralph-loop step optional — graceful fallback
  when ralph-wiggum skill not installed (#154); add explicit
  "do not stop" instruction across all pipeline steps (#134)
- fix(plan): add mandatory "Write Plan File" step with explicit Write
  tool instructions before post-generation options — plan always
  written to disk even in LFG/SLFG pipeline context (#155, #134)
- fix(plan): use full qualified agent name for spec-flow-analyzer
  to prevent Claude prepending wrong 'workflows:' prefix (#193)

Closes #154, #155, #193
Contributing to #134

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kieran Klaassen
2026-02-17 10:42:42 -08:00
parent e1906592cb
commit d314d7fa2a
5 changed files with 31 additions and 7 deletions

View File

@@ -150,7 +150,7 @@ Think like a product manager - what would make this issue clear and actionable?
After planning the issue structure, run SpecFlow Analyzer to validate and refine the feature specification:
- Task spec-flow-analyzer(feature_description, research_findings)
- Task compound-engineering:workflow:spec-flow-analyzer(feature_description, research_findings)
**SpecFlow Analyzer Output:**
@@ -475,6 +475,20 @@ end
- [ ] Add names of files in pseudo code examples and todo lists
- [ ] Add an ERD mermaid diagram if applicable for new model changes
## Write Plan File
**REQUIRED: Write the plan file to disk before presenting any options.**
```bash
mkdir -p docs/plans/
```
Use the Write tool to save the complete plan to `docs/plans/YYYY-MM-DD-<type>-<descriptive-name>-plan.md`. This step is mandatory and cannot be skipped — even when running as part of LFG/SLFG or other automated pipelines.
Confirm: "Plan written to docs/plans/[filename]"
**Pipeline mode:** If invoked from an automated workflow (LFG, SLFG, or any `disable-model-invocation` context), skip all AskUserQuestion calls. Make decisions automatically and proceed to writing the plan without interactive prompts.
## Output Format
**Filename:** Use the date and kebab-case filename from Step 2 Title & Categorization.