메뉴
List incomplete Dockyard work orders via MCP workorder_list_pending. Use when driving a queue, standup summaries, or “what’s left” across all issues; optional filters date and/or issue. Results sort by date, issue, then WO number.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | dockyard-list-pending-work-orders |
| description | List incomplete Dockyard work orders via MCP workorder_list_pending. Use when driving a queue, standup summaries, or “what’s left” across all issues; optional filters date and/or issue. Results sort by date, issue, then WO number. |
Dockyard registers workorder_* as MCP tools, not resources — an empty MCP resource list does not mean Dockyard is offline. Prefer invoking this tool directly; if it is missing, use dockyard pending (same DOCKYARD_ROOT). See dockyard-session-guide for the full picture.
date only), or single issue on a day (date + issue).workorder_list_pending with optional { date?, issue? }.pending array entries: each has date, issue, id, status (always pending).Typical loop: list pending → workorder_get for the first item → do the work → workorder_complete.
List work order ids and statuses via MCP workorder_list for a date and repo (optional issue). Use for one track (--issue) or all issues under a repo (omit issue).
How to use Dockyard in this chat: work orders live under DOCKYARD_ROOT (default ~/.dockyard). Dockyard exposes MCP tools named workorder_* — not MCP resources, so “list resources” will not show Dockyard. Prefer tool calls for workorder_list_pending / workorder_get / workorder_complete; if tools are missing, use the dockyard CLI or enable MCP via dockyard install-agents and restart the host app. Use when the user says to use Dockyard, drain the queue, or complete work orders.
Mark a Dockyard work order complete in index.json via MCP workorder_complete. Use after the work described in that WO is done and verified; requires date, issue slug, and wo-NNN id.
Load one Dockyard work order’s markdown and status via MCP workorder_get. Use when the user asks to read, review, summarize, or execute a specific WO identified by date, issue slug, and wo-NNN id.
Create a new Dockyard work order on disk via MCP tool workorder_insert. Use when the user wants to queue structured agent work, split a feature into trackable units, or log tasks under a dated issue slug. Requires markdown body with sections from ## Objective through ## Notes; see references/work-order-body-template.md.
Read the next 1-based work order sequence number for a date/issue via MCP workorder_next_number. Use when drafting titles or planning how many WOs to create before calling workorder_insert (the server still assigns the canonical id on insert).