Wayfinder map: os-backlog issue lifecycle & templates #239
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#239
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Destination
A decided design for the full os-backlog lifecycle — capture → refine → check-out → work → close — including issue templates (adopted from os-sdlc's spec-and-ticket layer) and how wayfinder-style map/child/assembly decomposition plugs in. Done when nothing is left to decide before implementing the changes.
Notes
Planning only: this map produces decisions, not plugin edits. Consult: plugins/os-sdlc/reference/spec-and-ticket-layer.md, plugins/os-backlog/skills/, docs/agents/issue-tracker.md, ADR-0042. Decided at charting: os-sdlc's spec/ticket templates are the starting authority (adopt/promote, not fresh design). Related open issue: #186 (deterministic ticket-filing CLI surface) — implementation dependency, not a decision here. The eventual autonomous loop's pane/worktree orchestration layer is herdr-cli (~/dev/ruby-gems/herdr-cli/).
Default skills for tickets: /grilling, /domain-modeling.
Decisions so far
Inventory backlog operations we may be overlooking — nine candidate operations os-backlog lacks (triage sweep, stale grooming, duplicate detection, dependency audit, size metrics, label hygiene, re-estimation, map rollup, PR intake); full detail in docs/research/backlog-operations-inventory.md on branch research/backlog-operations-inventory.
Define issue tiers: capture vs ticket vs map — three structural tiers, never asserted by labels; captures may rest indefinitely (refine only at intent-to-work); full template required only for handoff (ready-for-agent falsifiability test); maps triggered by refinement failure and stay HITL; no partial execution of mixed tickets — decision children with weighted recommendations, recommender-blind ≥85% sweep, all decisions close before assembly.
Choose the canonical home for shared issue templates — templates promoted to
plugins/os-backlog/references/templates/(spec/ticket/capture), os-sdlc links rather than inlines; capture tier is a minimal title +## Contexttemplate, refine adds the rest.Design the refine step: upgrading a capture to workable — agent end-to-end refine (enhanced triage skill) at pick-up or standalone; fills full template, adr-find, links, decision children + blind sweep; self-applies readiness labels, falsified downstream; may close duplicate/done captures with evidence.
Design the check-out process — claim = assignee + start comment (universal); staleness + falsifiability checkpoint before work on ready-for-agent pickups (bounce to refine on any clarifying question); fixed context-load: ticket + spec + linked ADRs + decision-children resolutions.
Design the close process and resolution comments — three-part resolution comment (done / evidence links / out-of-scope-or-captured) mandatory on agent closes; merge approval subsumes the review label for pipeline-worked tickets; recurring occurrences use the same comment shape without closing.
How wayfinder decomposition plugs into os-backlog — map spawn is flag + human charts (refine bounces, never auto-charts); wayfinder's labels/
Map:/Blocked byconventions adopted as-is; assembly ticket created at charting and agent-maintained;wayfinder:<type>supersedes readiness labels, map children skipped in readiness sweeps.Define the weighted-decision block format and threshold sweep — fenced YAML block (recommendation/confidence/reversal_cost/reasoning) below the prose memo; threshold hardcoded in a tested Ruby sweep CLI the recommender never loads; sweep auto-closes passers with the three-part resolution comment and routes failures to
ready-for-human.Should template/section compliance be linted? — yes: deterministic validator in os-backlog's Ruby CLI (tier computed, sections checked against canonical templates), run at refine-exit (gates self-applied
ready-for-agent) and rerun at handoff pickup; never at capture.Assemble the os-backlog lifecycle design — assembled into docs/os-backlog-lifecycle.md + ADR-0092..0096 on branch design/os-backlog-lifecycle; implementation work items enumerated; route complete.
Not yet specified
Out of scope
All 10 child decisions (#240-249) closed; #247 assembled into docs/os-backlog-lifecycle.md + ADR-0092..0096 on branch design/os-backlog-lifecycle. Map's destination (a decided design) is reached; closing per its own done-criteria.