task-centered-workflow ยท diff
git:20260331.392bb01 to git:20260331.771b71c
9 added, 0 removed. Audit A to A.
---
description: Execute substantial work through task-centered workflow
alwaysApply: true
---
# Task-Centered Execution Rule
For non-trivial work, use `tasks/` as the source of execution truth.
+ ## Contribution Modes
+
+ - External/community contribution (lightweight mode):
+ - Task folder is optional.
+ - `Task ID: N/A` is allowed for small fixes/docs/issues.
+ - Keep PR summary, validation evidence, and regression notes clear.
+ - Core/maintainer contribution (strict mode):
+ - Use full task-centered workflow for non-trivial changes.
+
## Required Behavior
1. If work spans multiple files/subsystems or requires review traceability:
- create or reuse a `tasks/TASK-.../` folder.
2. Keep these files updated during execution:
- `TASK.md` (scope, acceptance, risks, validation, regression scope)
- `STATUS.md` (progress and blockers)
- `REVIEW.md` (findings and merge readiness)
3. Update `tasks/board.md` whenever status changes.
4. Keep strategic discussion in `todo/*.md`, execution details in `tasks/`.
## Completion Gate
Before declaring work complete:
- acceptance criteria in `TASK.md` are checked or explicitly deferred,
- validation evidence is recorded,
- regression scope is reviewed,
- task board status is updated.