From 88616224e04138f25bc9b6a0372784ee788db389 Mon Sep 17 00:00:00 2001 From: catlog22 Date: Wed, 4 Feb 2026 17:18:56 +0800 Subject: [PATCH] refactor: remove redundant usage guidelines from workflow documentation --- .codex/prompts/brainstorm-with-file.md | 21 ----------------- .codex/prompts/collaborative-plan-parallel.md | 23 ------------------- .../prompts/collaborative-plan-with-file.md | 22 ------------------ .codex/prompts/unified-execute-with-file.md | 21 ----------------- 4 files changed, 87 deletions(-) diff --git a/.codex/prompts/brainstorm-with-file.md b/.codex/prompts/brainstorm-with-file.md index 02fa3e65..c22feaa5 100644 --- a/.codex/prompts/brainstorm-with-file.md +++ b/.codex/prompts/brainstorm-with-file.md @@ -562,27 +562,6 @@ Final synthesis: 4. **Evolution Tracking**: Document how ideas changed and evolved 5. **Action Items**: Generate specific, implementable recommendations ---- - -## When to Use This Workflow - -### Use brainstorm-with-file when: -- Starting a new feature/product without clear direction -- Facing a complex problem with multiple possible solutions -- Need to explore alternatives before committing to an approach -- Want documented thinking process for team review -- Combining multiple viewpoints (creative, pragmatic, systematic) - -### Use direct execution when: -- Short, focused idea evaluation (single component) -- Clear direction with minimal exploration needed -- Quick follow-up to existing brainstorm session - -### Consider alternatives when: -- Analyzing existing code/system → use `workflow:analyze-with-file` -- Complex planning with parallel perspectives → use `workflow:collaborative-plan-with-file` -- Ready to implement → use `workflow:lite-plan` -- Debugging or troubleshooting → use `workflow:debug-with-file` --- diff --git a/.codex/prompts/collaborative-plan-parallel.md b/.codex/prompts/collaborative-plan-parallel.md index 82bfe59f..7ff56f92 100644 --- a/.codex/prompts/collaborative-plan-parallel.md +++ b/.codex/prompts/collaborative-plan-parallel.md @@ -612,7 +612,6 @@ cat .workflow/.execution/EXEC-eg-001-*/execution-events.md cat .workflow/.execution/EXEC-eg-002-*/execution-events.md cat .workflow/.execution/EXEC-eg-003-*/execution-events.md ``` -``` ### Step 4.3: Generate plan.md Summary (Extended) @@ -703,28 +702,6 @@ Present session statistics with execution group information. 3. **Prepare Environments**: Ensure multiple codex instances can run in parallel 4. **Plan Merge Order**: Understand which groups must merge first ---- - -## When to Use This Workflow - -### Use collaborative-plan-parallel when: -- Complex tasks with multiple independent sub-systems -- Want true parallel development with multiple developers/codex instances -- Need structured multi-branch development strategy -- Tasks have clear domain boundaries with minimal cross-dependencies -- Large projects requiring faster completion through parallelization - -### Use collaborative-plan-with-file (original) when: -- Smaller tasks with high inter-domain dependencies -- Single developer/codex instance -- Prefer simpler linear execution -- Cross-domain coordination is critical - -### Consider alternatives when: -- Simple single-domain tasks → use `workflow:lite-plan` -- Exploring ideas → use `workflow:brainstorm-with-file` -- Analyzing code → use `workflow:analyze-with-file` -- Ready to execute existing plan → use `workflow:unified-execute-parallel` with GROUP parameter --- diff --git a/.codex/prompts/collaborative-plan-with-file.md b/.codex/prompts/collaborative-plan-with-file.md index 2ba46fdb..301fb67c 100644 --- a/.codex/prompts/collaborative-plan-with-file.md +++ b/.codex/prompts/collaborative-plan-with-file.md @@ -385,26 +385,4 @@ User resumes: TASK="same task" --- -## When to Use This Workflow - -### Use collaborative-plan-with-file when: -- Complex tasks requiring multi-domain decomposition -- Need structured planning with conflict detection -- Tasks spanning multiple modules or systems -- Want documented planning process for team review -- Preparing for multi-step execution workflows - -### Use direct execution when: -- Simple, single-domain tasks -- Clear implementation path without ambiguity -- Quick follow-up to existing planning session - -### Consider alternatives when: -- Exploring ideas without clear direction → use `workflow:brainstorm-with-file` -- Analyzing existing code/system → use `workflow:analyze-with-file` -- Lightweight planning for simple features → use `workflow:lite-plan` -- Ready to execute existing plan → use `workflow:unified-execute-with-file` - ---- - **Now execute collaborative-plan-with-file for**: $TASK diff --git a/.codex/prompts/unified-execute-with-file.md b/.codex/prompts/unified-execute-with-file.md index aa7d66eb..1368eebb 100644 --- a/.codex/prompts/unified-execute-with-file.md +++ b/.codex/prompts/unified-execute-with-file.md @@ -434,27 +434,6 @@ Complete --- -## When to Use This Workflow - -### Use unified-execute-with-file when: -- Ready to execute a complete plan from planning workflow -- Need reliable sequential task execution with tracking -- Want automatic git commits for audit trail -- Executing plans from brainstorm, analysis, or collaborative-plan workflows -- Need to validate plan before full execution (--dry-run) - -### Use direct CLI execution when: -- Single task that doesn't need full plan structure -- Quick implementation without tracking overhead -- Small changes that don't need git history - -### Consider alternatives when: -- Still planning/exploring → use `workflow:brainstorm-with-file` or `workflow:analyze-with-file` -- Need complex task planning → use `workflow:collaborative-plan-with-file` -- Debugging or troubleshooting → use `workflow:debug-with-file` - ---- - ## Command Examples ### Standard Execution