workflow-engineer-fix-slicelisted
Install: claude install-skill MartinKChen/harness-claude-code
# workflow-engineer-fix-slice
Address slice-review findings on a single slice. Dispatched after the slice review (the `runReviewSlice()` fan-out in `implement-slice`) returns a BLOCK verdict. Scope is read from the most recent slice-review comment on the slice (newer than the slice branch's last `Refs #<slice#>` commit), with user directives in the same window overriding.
In the new model, E2E passing is a separate earlier phase (`workflow-engineer-diagnose-e2e` + `workflow-engineer-fix-e2e`); this fix loop only addresses the reviewer's findings. The calling workflow re-runs the slice review after the fix — this skill does no re-validation and flips no labels.
## When to activate
Activate this skill whenever:
- The dispatch prompt opens with `Fix the review feedback on slice #<n>`.
- The user types `/workflow-engineer-fix-slice`, or phrases like "fix slice #<n> per the reviewer findings".
Do NOT activate to pass E2E acceptance (use `workflow-engineer-diagnose-e2e` / `workflow-engineer-fix-e2e`), to fix a PR (use `workflow-engineer-fix-pr`), or to implement fresh tasks (use `workflow-engineer-implement-task`).
## Input contract
Read the slice issue #<n> body. Locate the task block(s) in the `## Tasks` checklist (each entry is a header `[ ] \`<id>\` · **<type>** · blocked-by <ids|—>`, the delivery on the next line, a `covers:` + `contract:`/`entry-source:`/`done:` pointer line, then `scenario:` and a fenced ```gherkin block of named Scenarios). The checklist is the dura