Repository navigation
docs: add the missing Next sections to SDLC skills #6281
Copy link
Copy link
Closed
Task
3 / 33 of 3 issues completed
Copy link
Labels
good first issueGood entry point for new contributors.Good entry point for new contributors.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.Nice-to-have, cosmetic, or speculative; opportunistic.work-class: mechanicalDeterministic, trivially reversible maintenance: dependency bumps, lint/format, sync.Deterministic, trivially reversible maintenance: dependency bumps, lint/format, sync.
Description
Problem
.claude/rules/skill-bodies-state-current-rules.md requires a ## Next section in any skill that has a natural successor. These SDLC skills lack one:
- Planning:
prd(has Composition at:334),wayfind(Composition:174),devils-advocate("Workflow position":238),questionnaire,audit-answers - Architecture and design:
architecture:improve,architecture:record-decision,domain-driven-design:curate-language - Review and verify:
review:quality-gate,review:fanout,verification:confirm(has "Skill chaining":143),verification:measure,toolchain:check - Ship:
source-control:pull-request,source-control:babysit-prs,source-control:worktree - Upkeep:
codebase-health:audit,improvement:find,coupling:reduce,code-tidying:tidy,code-tidying:batch-simplify - Session:
session-flow:running-retro,session-flow:show-options
The bug-path and test-path skills are covered by their own issues. Also, /planning:plan's ## Next names only implement (plugins/planning/skills/plan/SKILL.md:386-388). It never names implement-dispatch, decompose or design-handoff.
Proposed fix
Add ## Next per the rule's format, following the chain confirmed in the discovery session:
discover → shape → design → plan → [decompose] → implement → test → review → verify → ship → [retro]
This should land after the design-spine issue, so the Next sections encode the final chain.
Acceptance
- Every skill listed has a
## Nextin the rule's exact format, or a one-line reason it has no successor. - Plan's
## Nextcovers its outcomes: implement, implement-dispatch, decompose.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
good first issueGood entry point for new contributors.Good entry point for new contributors.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.Nice-to-have, cosmetic, or speculative; opportunistic.work-class: mechanicalDeterministic, trivially reversible maintenance: dependency bumps, lint/format, sync.Deterministic, trivially reversible maintenance: dependency bumps, lint/format, sync.
Type
Fields
No fields configured for Task.
Activity
github-actions commentedon Oct 4, 2026
Thanks for the detailed report. I understand this as: several SDLC skills across Planning, Architecture, Review, Ship, Upkeep, and Session plugins are missing the
## Nextsection required by.claude/rules/skill-bodies-state-current-rules.md, and/planning:plan's existing## Nextonly namesimplement, omittingimplement-dispatchanddecompose. The listed skills, line references, and the proposed successor chain give enough detail to scope the work directly.One open question for sequencing: the issue notes this should land after "the design-spine issue" so the
## Nextsections reflect the final chain, but doesn't link that issue by number — worth confirming which one that is before starting, so the successor chain is accurate.I didn't find an existing open issue duplicating this specific scope (closed issues #3947, #3959, and #4066 covered earlier rounds of adding
## Nextsections, but not these particular skills).Automated triage. A maintainer reviews it.
kyle-sexton commentedon Oct 18, 2026
This was generated by AI during backlog shaping.
This issue is split into 3 pieces, each sized for one lane PR. 14 of the 23 listed skills still lack a
## Nexton origin/main (the other 9, and plan's implement/implement-dispatch/decompose coverage, landed via #7053 and earlier work), and the design-spine prerequisite #6278 merged in #6299; 14 SKILL.md files plus a fragment per plugin split into three groups under 10 files each.Filed pieces are sub-issues of this one, and the paced queue admits them to the lane. Unfiled pieces wait on the blocker shown. The owner approved this split in an attended backlog-shaping session on 2026-10-18.