jared/cc-os

Watch

Fork 0

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

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 referenced this issue

2026-07-10 17:22:35 +00:00

os-backlog slice 7: SessionStart injection note + /to-issues routing #16

jared referenced this issue

2026-07-12 19:43:33 +00:00

os-status: unified /os-status:fix setup/update skill (ADR-026) #21

jared commented

2026-07-12 19:54:23 +00:00

Author

Owner

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 referenced this issue

2026-07-12 20:10:55 +00:00

os-backlog: cache resolved Planka board id in .cc-os/config #22

jared referenced this issue from a commit

2026-07-12 21:27:25 +00:00

docs: ADR-026 — unified /os-status:fix setup/update command (refs #21, #14)

jared referenced this issue from a commit

2026-07-12 21:27:25 +00:00

os-status + os-backlog: /os-status:fix unified setup/update + /os-backlog:route tracker onboarding (closes #21, refs #14, ADR-026)

jared referenced this issue from a commit

2026-07-12 21:27:25 +00:00

os-backlog: align .cc-os/config with os-status key=value contract (refs #14)

jared commented

2026-07-12 22:25:29 +00:00

Author

Owner

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

jared referenced this issue

2026-07-12 22:25:51 +00:00

os-backlog slice 7: SessionStart injection note + /to-issues routing #16

jared referenced this issue from a commit

2026-07-23 16:22:55 +00:00

os-sdlc: lint batch 1 -- stock rubocop cops for Sandi-Metz method-length/complexity (issues #14, #30)