メニュー
Create, edit, comment, link, prioritize, and close Scope tickets from Codex. Use when the user asks for ticket changes or when work progress should be recorded.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Plan, track, and report on multi-step work using the Scope kanban (local CLI + web UI). Use when the user asks you to scope/plan a project, list open work, mark a ticket done, link a branch/PR, or coordinate with other agents on shared state. Don't use for one-off questions or trivial single-edit requests.
Summarize the current Scope board, identify active work, and choose the next ticket. Use when starting a session, resuming work, or giving status.
Attach branches and PRs to Scope tickets and prepare handoff comments. Use when creating branches, opening PRs, finishing work, or handing work to another agent.
Coordinate multiple Codex agents working in one Scope workspace. Use when tasks are parallelized, handed off, blocked, or updated by several agents.
Break a user request into Scope epics, stories, and bugs before implementation. Use for feature work, refactors, investigations, and broad tasks that need visible progress.
Plan, track, and report multi-step work using Scope. Use when the user wants Codex to manage project state, open tickets, progress, bugs, branches, PRs, or agent coordination.
| name | ticket-ops |
| description | Create, edit, comment, link, prioritize, and close Scope tickets from Codex. Use when the user asks for ticket changes or when work progress should be recorded. |
| metadata | {"short-description":"Operate Scope tickets"} |
Read state before writing:
scope --json ticket show SCP-123
Use CLI commands rather than editing .scope/scope.db.
Common operations:
scope status SCP-123 in_progress --by codex
scope ticket edit SCP-123 --priority high
scope comment SCP-123 "Useful implementation note." --by codex
scope link add SCP-123 blocked_by SCP-130
scope status SCP-123 done --by codex
For several changes, use scope batch --by codex so readers see one coherent
history entry sequence.