Design the refine step: upgrading a capture to workable #242
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#242
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?
Map: #239
Blocked by #240
Blocked by #241
Question
Who or what upgrades a raw capture (e.g. #118) into a workable ticket — a skill, a human triage pass, an agent — and at what moment in the lifecycle? What does the refine step add (structure, acceptance criteria, links), and how does it interact with the ready-for-agent / ready-for-human labels?
Constraints inherited from #240's resolution: enhance the installed Matt Pocock triage skill rather than replacing it; recommender must be blind to the automation threshold (separate sweep gate applies it); undecided parts of a ticket become decision children with weighted recommendations, swept at ≥85% confidence + cheap reversal; no partial execution before all decision children close.
Resolution
Decided (grilling session 2026-08-04):
ready-for-agentonce the template is complete and all decision children are closed. No human gate in the hot path; honesty is enforced by #240's falsifiability test — a working agent forced to ask a clarifying question strips the label with a comment.## Context+ repo reading; (b) run/os-adr:findon paths the work will touch, link governing ADRs in Notes-for-implementer; (c) link related issues; (d) spawn decision children with machine-parseable weighted blocks (format: #248), gated by the blind sweep; (e) applyready-for-agent/ready-for-human, route needs-a-map to the human.