Refactor workflows to enhance task attachment and execution model

- Updated auto-parallel.md to clarify the task attachment model, emphasizing the orchestration of tasks through attachment rather than delegation. Improved descriptions of phases and execution flow.
- Revised plan.md, tdd-plan.md, test-fix-gen.md, and test-gen.md to simplify lifecycle patterns, replacing detailed patterns with concise lifecycle summaries.
- Modified reference-page-generator.md to streamline the component extraction process, focusing on layout templates and removing unnecessary complexity in the operations.
- Enhanced error handling and output messages across various workflows to improve clarity and user guidance.
This commit is contained in:
catlog22
2025-11-11 19:52:58 +08:00
parent 7d77b0e6f7
commit a393d95cf9
6 changed files with 194 additions and 495 deletions

View File

@@ -337,23 +337,7 @@ Quality Gate: Consider running /workflow:action-plan-verify to validate TDD task
- No user intervention required between phases
- TodoWrite dynamically reflects current execution state
### Lifecycle Pattern
```
Initial: [Phase 1: pending] [Phase 2: pending] [Phase 3: pending] [Phase 5: pending]
Phase 3 Invoked (ATTACHED):
[Phase 1-2: completed] [Phase 3.1: in_progress] [Phase 3.2: pending] [Phase 3.3: pending] [Phase 5: pending]
Phase 3 Completed (COLLAPSED):
[Phase 1-2: completed] [Phase 3: completed] [Phase 5: pending]
Phase 5 Invoked (ATTACHED, generates TDD tasks):
[Phase 1-3: completed] [Phase 5.1: in_progress] [Phase 5.2: pending] [Phase 5.3: pending]
Phase 5 Completed (COLLAPSED, each IMPL task contains Red-Green-Refactor cycle):
[Phase 1-3: completed] [Phase 5: completed] [Phase 6: in_progress]
```
**Lifecycle Summary**: Initial pending tasks → Phase invoked (tasks ATTACHED) → Sub-tasks executed sequentially → Phase completed (tasks COLLAPSED to summary) → Next phase begins (conditional Phase 4 if conflict_risk ≥ medium) → Repeat until all phases complete.
### TDD-Specific Features