root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-3502): add comment-triggered retriage when task is in triage status

Browse Source 
Merged four commits implementing comment-driven retriage: triage rules now respond to specific comment patterns (Step 1) and surface needs-replan feedback inputs in the UI (Step 2), with documentation for the new behavior and a bug fix restoring workspace typecheck defaults. Changes span the core ta

Fusion-Task-Id: FN-3502
This commit is contained in:
Fusion
2026-05-05 13:32:10 -07:00
committed by gsxdsm
parent 61bf81d6b8
commit 57c67b6bbd
8 changed files with 200 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/task-management.md
View File

@@ -231,6 +231,20 @@ This file is the contract for execution and review.
Steering comments can be injected mid-run into active executor sessions.
### User comments and triage re-consideration
User comments can trigger **re-triage** for already-planned but non-executing work:
- `triage` + `awaiting-approval` → user comment sets `status: "needs-replan"`
- `triage` or `todo` with a real (non-bootstrap-stub) `PROMPT.md` → user comment sets `status: "needs-replan"`
- `triage` or `todo` with only bootstrap-stub/unplanned prompt content → no re-triage transition
Execution ownership is preserved for active work:
- User comments on `in-progress` and `in-review` tasks do **not** re-route those tasks back through triage.
- Agent/system comments do **not** trigger comment-driven re-triage.
This is distinct from steering comments: steering feedback targets the currently running executor session, while comment-driven re-triage requests a fresh specification pass for planned work.
## Refinement Tasks
`fn task refine <id>` creates a new planning task that depends on the original done/in-review task.