T-WX0H-complete-task-next-rename-skill-consumers

Status: closed/obsoleted · Impact: low · Complexity: small

Goal

T-0015 (merged in PR #484) renamed the dispatch verb sdlc task sort → sdlc task next and moved the op to apps/sdlc/lib/model/entities/task/ops/next.ts (at plugin/lib/… until the T-1RLU tree move). The live skill consumers were updated correctly (orchestrate/SKILL.md and task-work/SKILL.md both shell task next), but a few maintained docs and doc-comments still name the removed sdlc task sort verb. Sweep those so no current-facing source presents a verb that no longer exists.

Today

The verb is gone (sdlc task sort exits unknown command 'sort'); sdlc task next is the only dispatch verb. These maintained locations still name the old verb as if it were live:

Location	Role today
`docs/skills/orchestrate.md`	Per-skill Mermaid doc; the Step-4 node reads `sdlc task sort` (line 41), describing a command that errors
`apps/sdlc/cli/README.md`	Uses `["task", "sort"]` as the canonical path-shape example for a registry op (line 5)
`apps/sdlc/lib/registry.ts`	Doc-comment uses `["task","sort"]` as the path-shape example (line 9)

Historical records that correctly preserve the old name and are not in scope: the T-0015 / T-ZSSE / T-3VD8 task specs, decision/milestone/capability/plan docs, task-help.before.txt golden, the next.ts / next.test.ts “renamed from” comments, and orchestrate/invariants.yaml:54 (“renamed from sdlc task sort in T-0015”).

Proposed

Every maintained, current-facing reference names sdlc task next (or ["task","next"]). Historical/explanatory references to the old name remain untouched. No runtime behavior changes — docs and comments only.

Approach

Update the docs/skills/orchestrate.md Step-4 flowchart node sdlc task sort → sdlc task next (the docs site is gitignored and rebuilt at deploy — no committed mirror to regenerate).
Update the path-shape example in apps/sdlc/cli/README.md and the doc-comment in apps/sdlc/lib/registry.ts from ["task","sort"] to ["task","next"].
Run the doc/quality gates (docs generate --check, rumdl) and confirm green.

Files to touch

Location	Kind	Change
`docs/skills/orchestrate.md`	modify	Step-4 Mermaid node `sdlc task sort` → `sdlc task next`
`apps/sdlc/cli/README.md`	modify	Path-shape example `["task", "sort"]` → `["task", "next"]`
`apps/sdlc/lib/registry.ts`	modify	Doc-comment path-shape example `["task","sort"]` → `["task","next"]`

Acceptance criteria

AC-1: grep -rn "task sort" docs/skills/ apps/sdlc/cli/README.md apps/sdlc/lib/registry.ts returns no matches.
AC-2: docs/skills/orchestrate.md’s Step-4 node reads sdlc task next.
AC-3: No change to any file under docs/planning/tasks/, docs/planning/decisions/, docs/planning/milestones/, apps/sdlc/cli/tests/goldens/, or the next.ts/next.test.ts historical comments.

Out of scope

Historical task/decision/milestone/capability/plan docs and golden snapshots that name task sort as a record of the pre-rename state — these stay verbatim (T-0015 §“leave its task sort references as historical record”).
Closing T-0015’s own lingering open/ready task file + worktree — that is a separate /sdlc:task-review / /sdlc:project-cleanup item.
The scheduled-cron frozen-skill-body artifact (see Discovery context) — operational, not a source change.

Dependencies

none — T-0015 already merged (#484); this is residual cleanup.

Discovery context

Surfaced 2026-06-30 by the autonomous /sdlc:orchestrate loop: a tick’s Step 4 ran sdlc task sort and got unknown command 'sort'. Root cause of the runtime error was the cron job carrying a frozen copy of the pre-#484 skill body; the on-disk skills were already correct. Auditing the rename surfaced these residual doc/comment references as the only genuine source leftovers.

← Back to Tasks