원클릭으로
todo-triage
Use when reviewing pending todos for approval, prioritizing code review findings, or interactively categorizing work items
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when reviewing pending todos for approval, prioritizing code review findings, or interactively categorizing work items
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Inspect live routes and manage optional user-local OpenAI-compatible/LiteLLM extra routes through the kbrouter CLI.
Single user-facing KB completion command. Takes a feature, plan, or manifest from its current state through planning, work, post-work finalization, and configured delivery: local completion, pushed PR, or explicitly configured direct integration and sync.
Configure optional portable per-project lower-tier-attempt and delivery policy.
Large-initiative coordinator for KB workflows. Use for app migrations, framework rewrites, major architecture changes, multi-subsystem initiatives, multiple brainstorms/manifests, long backlogs, or queued execution across related workstreams.
Internal post-work quality and learning phase. Runs kb-review -> resolution gate -> follow-up resolution -> proof/demo evidence -> compound -> learn -> evolve -> memory refresh/compact -> cleanup after kb-work finishes all slices. Normally invoked by kb-work or kb-complete; not the primary user-facing completion command.
Deprecated compatibility alias for kb-complete. Use when an older prompt or workflow says 'kb finish'; delegate the same input to kb-complete and report the kb-complete result.
| name | todo-triage |
| description | Use when reviewing pending todos for approval, prioritizing code review findings, or interactively categorizing work items |
| argument-hint | [findings list or source type] |
| disable-model-invocation | true |
Review unresolved durable work and decide what belongs on root todo.md.
Do not write implementation code during triage. Triage only classifies, prioritizes, merges, parks, or removes work items.
Read in this order:
todo.md active board..context/compound-engineering/todos/ only when a CE skill explicitly
generated file-per-todo findings.For each item, choose one:
| Decision | Action |
|---|---|
| ready | keep on todo.md with owner/status/next action |
| blocked | record blocker and resume condition |
| parked | move under parked/cold-storage section |
| duplicate | merge into the canonical existing item |
| delete | remove only if stale, invalid, or already completed |
Ask the user only when priority, product intent, risk acceptance, or deletion is a real human decision. Otherwise update the board directly.
## Todo Triage
| Item | Decision | Reason | Next action |
|---|---|---|---|
If legacy CE todo files were read, report whether they were converted, left in legacy storage, or no longer relevant.