メニュー
Use when working with a Backlog.md project or its `backlog` CLI/MCP, including creating, reading, refining, updating, completing, or archiving tasks and managing dependencies or milestones.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Draft or revise external communication in the user's concise, direct, informal voice. Use whenever Codex is asked to write, draft, reply, post, or comment on the user's behalf, including posting comments for them without an explicit "as the user" instruction. This skill controls wording only and never grants permission to send or post.
Refine selected backlog items or whole backlog sources into implementation-ready work. Use when asked to clarify, decompose, or prepare work across Markdown, Backlog.md, GitHub Issues, Linear, or another supported provider.
Resolve and operate on backlog sources consistently across loose Markdown, Backlog.md, GitHub Issues, Linear, and other supported providers. Use whenever a backlog command or skill reads or changes provider-backed work.
Resolve human decisions, missing inputs, stale blockers, and decision-only backlog items. Use when asked to unblock work or persist answers across Markdown, Backlog.md, GitHub Issues, Linear, or another supported provider.
Coordinate multiple local agents working from the same backlog or work queue with bounded Worklease claims. Use when selecting, claiming, heartbeating, checkpointing, handing off, or releasing shared work.
Explicit full implementation-review method for correctness, security, performance, maintainability, tests, and likely future failure modes. Use only when a full-review trigger applies to a branch, PR, commit range, changed files, or completed backlog item; do not use for light or style-only review or backlog state mutation.
| name | backlog-md |
| description | Use when working with a Backlog.md project or its `backlog` CLI/MCP, including creating, reading, refining, updating, completing, or archiving tasks and managing dependencies or milestones. |
Treat Backlog.md as a provider-owned task system. Use backlog-source-workflow for source selection, dependency scheduling, and claims; use this skill for provider operations and ticket conventions.
backlog CLI or authorized MCP integration. Never edit its task files directly.--plain for agent-readable output and read the complete item before editing it.references/cli.md as the command map. Consult narrow live help only when the installed version rejects a command or a needed capability is missing.bunx backlog.md only when one-off dependency execution is authorized.Keep implementation tasks, acceptance criteria, and Definition of Done distinct:
### Implementation tasks
- [ ] T1 — one coherent behavioral outcome
### Acceptance criteria
- [ ] AC1 — observable behavior or contract
### Definition of Done
- [ ] DOD1 — final verification or delivery obligation
Implementation tasks are the work sequence. Acceptance criteria describe testable outcomes. Definition of Done is a final quality gate. Preserve checked entries and stable IDs; never reset them without evidence that work was reopened.
Use native Backlog.md plan, AC, and DoD fields. The CLI supports AC/DoD checkbox operations; update the complete plan field when changing a plan checkbox. A checked task records progress but does not by itself complete the provider item.
When creating or refining tickets, use dependencies for required order and parents only for genuine grouping. Split into separate tasks only for independently deliverable outcomes or useful parallelism; otherwise keep one item with bounded implementation tasks.
Complete an item only after its tasks and acceptance criteria are satisfied and required verification/review evidence is recorded. Archive only when requested or required by the project's established workflow.