unioss-scopelisted

# UNIOSS Scope Writer ## Overview Tell a PM/QC reader what changed and what to retest — in business language, not a diff. Follow `../unioss-pipeline/REFERENCE.md` → Shared stage rules, with one deliberate exception: **this skill writes to the ticket folder `.walkthrough/<PREFIX>-[IID]/`, not into a `round-<N>/` subfolder.** `scope.md` spans rounds — one file per ticket, overwritten in place every round so it always reflects the current cumulative scope. Never version it (no `.v2`). **Core principle:** never assume a change is contained — every related area is potentially affected and belongs on the retest list. **Track progress:** create a todo per Workflow step below and check each off as you complete it. ## Philosophy - Never assume anything is certainly correct. - When code changes, all related areas should be considered potentially affected. - The entire related feature should be retested, not just the touched line. ## Input - **Pipeline:** invoked at Step 11 of `unioss-pipeline`, right after GATE 3 accept and **before** the tester (Step 12) — the diff is final by then (GATE 3 already accepted), and the tester consumes this file's affected features/URLs as a coverage source. Reads the round's `changes.md` (+ `api-spec.md` if present) as the starting source of truth, plus every repo the coder touched. - **Standalone** (`/unioss-scope [ticket-number]`): if no round context exists, derive the change set from `git diff` / `git log` against the base branch (`gitlab.bas