메뉴
DEPRECATED — The backlog/issue distinction no longer exists. All work items are issues (<project>-kanban/issues/<id>-<slug>.<state>.md) from creation. Use backlog-add to capture an issue, to-prd to create a PRD. This skill is kept for reference only.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | backlog-promote |
| description | DEPRECATED — The backlog/issue distinction no longer exists. All work items are issues (<project>-kanban/issues/<id>-<slug>.<state>.md) from creation. Use backlog-add to capture an issue, to-prd to create a PRD. This skill is kept for reference only. |
backlog-promote is no longer needed.
The old pipeline was: backlog-add → backlog-promote → to-prd → to-issues.
The new pipeline is:
backlog-add — creates an issue directly in <project>-kanban/issues/<id>-<slug>.backlog.mdto-prd — creates a numbered, versioned PRD in <project>-kanban/prds/<id>-<slug>.mdgit mv operations: .backlog.md → .active.md → .done.mdThere is no "promotion" step because there is no distinction between a backlog entry and an issue. They are the same file from creation.
Commit task changes from a worktree onto the base branch (read from KANBAN_BASE_BRANCH env var). Use when finishing a kanban task to stage, commit, and cherry-pick changes back to the base ref.
Recover orphaned/dangling commits from kanban headless runs where the AI agent committed in the worktree but the kanban-commit agent failed to cherry-pick to the target branch (commit exists as a dangling object unreachable from any ref). Use when a ai-task-start-kanban-headless run completed/finished but the commit is missing from the target branch, or when investigating "nothing to commit — working tree is clean" in kanban-commit agent output.
Capture a new feature, bug, or tweak idea as an issue file in the project's kanban repo at <project>-kanban/issues/<id>-<slug>.backlog.md. Runs a short grilling pass against the existing domain model so the entry is sharper than a one-liner. Uses sequential IDs (via flock(1)) so files sort naturally even with concurrent agents.
Plan and execute a full git history squash job — analyze commits between two refs, group them into ~10 semantically meaningful squashes, drop irrelevant directories or paths, cherry-pick each group with conflict resolution onto a new branch, and verify the final tree matches the original modulo dropped paths. Use when the user says "reduce commits", "squash branch history", "clean up git history", "rewrite branch", "compress commits", or wants to consolidate a messy branch before merge.
Read the last pi agent session for the current project, extract what was discussed or done, and create issue files (as <project>-kanban/issues/<id>-<slug>.backlog.md) for any work items, bugs, or follow-ups it uncovered. Use when a session ended without wrapping everything up, when the user wants to capture session outcomes, or when you need to preserve context across sessions.
ELIMINATED — Issues are created directly via backlog-add or manually. PRDs reference issues by ID in their frontmatter. This file is kept for reference.