jared
/
cc-os
1
0
Fork 0
Code Issues 17 Pull Requests Packages Projects Releases Wiki Activity

os-backlog slice 5: routing/migration skill #14

New Issue
Closed
opened 2026-07-10 17:22:34 +00:00 by jared · 2 comments
jared commented 2026-07-10 17:22:34 +00:00
Owner
Copy Link

Type: Semi · Triage: ready

Parent

PRD: issue #9 (os-backlog plugin). State pointer: Planka card https://planka.hyperthrive.io/cards/1816234194716592051

What to build

The routing/migration skill — the onboarding conversation for a project. It inspects what tracking already exists (Planka board, Forgejo/GitHub issues, in-repo issue files), runs the resolver, proposes a destination per the boundary rule (Planka = state, git issues = specs only; card-as-pointer + issue-chain-as-spec for code efforts; promotion rule when a Planka effort accretes significant code), migrates existing open items mechanically with back-links so nothing is tracked twice, and writes the tracker key to .cc-os/config.

Semi: the mechanical parts (inspection, migration moves, config write) run autonomously; the destination decision and any migration of live project history are named decision gates — stop and confirm with the human.

Acceptance criteria

  • Skill detects each pre-existing tracker type and reports what it found
  • Proposes a destination consistent with the resolver + boundary rule; stops for human confirmation before migrating or writing config
  • Migration preserves history via back-links; no item duplicated across trackers afterward
  • Writes a valid tracker key; the os-status check goes silent on next session start
  • Onboarded against cc-os itself first (rollout pattern), then one more project

Blocked by

  • #11 (tracker key + os-status check)
  • #12 (routing resolver)
**Type:** Semi · **Triage:** ready ## Parent PRD: issue #9 (os-backlog plugin). State pointer: Planka card https://planka.hyperthrive.io/cards/1816234194716592051 ## What to build The routing/migration skill — the onboarding conversation for a project. It inspects what tracking already exists (Planka board, Forgejo/GitHub issues, in-repo issue files), runs the resolver, proposes a destination per the boundary rule (Planka = state, git issues = specs only; card-as-pointer + issue-chain-as-spec for code efforts; promotion rule when a Planka effort accretes significant code), migrates existing open items mechanically with back-links so nothing is tracked twice, and writes the `tracker` key to `.cc-os/config`. Semi: the mechanical parts (inspection, migration moves, config write) run autonomously; the destination decision and any migration of live project history are named decision gates — stop and confirm with the human. ## Acceptance criteria - [ ] Skill detects each pre-existing tracker type and reports what it found - [ ] Proposes a destination consistent with the resolver + boundary rule; stops for human confirmation before migrating or writing config - [ ] Migration preserves history via back-links; no item duplicated across trackers afterward - [ ] Writes a valid `tracker` key; the os-status check goes silent on next session start - [ ] Onboarded against cc-os itself first (rollout pattern), then one more project ## Blocked by - #11 (tracker key + os-status check) - #12 (routing resolver)
jared added the
ready-for-agent
 label 2026-07-10 17:22:34 +00:00
jared commented 2026-07-12 19:54:23 +00:00
Author
Owner
Copy Link

Built in commit 696aefc as /os-backlog:route: inspect + config-write subcommands, tracker format validation, human gates for destination + live-history migration. Suite 54 runs/110 assertions. Left open: rollout acceptance (onboard cc-os itself, then one more project) still pending.

Built in commit 696aefc as /os-backlog:route: inspect + config-write subcommands, tracker format validation, human gates for destination + live-history migration. Suite 54 runs/110 assertions. Left open: rollout acceptance (onboard cc-os itself, then one more project) still pending.
jared commented 2026-07-12 22:25:29 +00:00
Author
Owner
Copy Link

This was generated by AI during triage.

Shipped in commit 696aefc (2026-07-12): /os-backlog:route skill + inspect/config-write CLI subcommands with minitest coverage. cc-os itself is onboarded (.cc-os/config has tracker=planka:cc-os), satisfying the first rollout step. Residual acceptance item — onboard one more project — is an operational hitl conversation, tracked on the Planka board, not a spec gap. Closing.

> *This was generated by AI during triage.* Shipped in commit 696aefc (2026-07-12): /os-backlog:route skill + inspect/config-write CLI subcommands with minitest coverage. cc-os itself is onboarded (.cc-os/config has tracker=planka:cc-os), satisfying the first rollout step. Residual acceptance item — onboard one more project — is an operational hitl conversation, tracked on the Planka board, not a spec gap. Closing.
jared closed this issue 2026-07-12 22:25:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
research/clutter-inventory
Labels
Clear labels   
P0

Priority 0 — drop everything

  
P1

Priority 1 — next up

  
P2

Priority 2 — normal

  
P3

Priority 3 — someday

  
afk-ready

Autonomous end-to-end; closed after verification

  
hitl

Human-owned; never picked up autonomously

  
next

Human-curated next up — AI never applies or removes

  
ready-for-agent

Triage complete; an agent can pick this up

  
review

Shipped semi work awaiting human sign-off

  
semi

Autonomous through mechanical parts; stops at gates; ships to review

  
waiting

Blocked; blocker named in a comment

  
wayfinder:grilling

   
wayfinder:map

   
wayfinder:research

   
wayfinder:task
No Label
P0
P1
P2
P3
afk-ready
hitl
next
ready-for-agent
review
semi
waiting
wayfinder:grilling
wayfinder:map
wayfinder:research
wayfinder:task
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jared/cc-os#14
No description provided.
Delete Branch "%!s(<nil>)"

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?