crow-pet-work-queue

name	crow-pet-work-queue
description	Turn approved SPEC.MD files or workflow definitions into markdown work items for harness or agent builders, then track verification and handoff state.

crow.pet Work Queue

Use this skill when an approved spec or workflow definition should become builder-ready queued work without introducing a runner, daemon, or external issue tracker.

Workflow

1. Read the task record and approved SPEC.MD or workflow definition.
2. Create one markdown work item from ../../templates/work-item.md.
3. Copy spec identity, optional architecture identity, optional workflow identity, run identity, idempotency key, selected profiles, goal, capability needs, acceptance criteria, and verification into the work item.
4. Route permission-sensitive or state-changing work through crow-pet-policy-gate.
5. Use the Capability Broker to bind requested capabilities to the safest available harness, tool, model, or adapter.
6. Select the builder skill or harness adapter.
7. Mark the work item ready when it can be handed to a builder.
8. Mark it needs-human, blocked, built, failed, or accepted as evidence arrives. Gatekeeper interrupts move it through paused and cancelled as first-class transitions.
9. Record the handoff report path and artifacts.
10. Return a concise status update.

Progressive Disclosure

Load ../../templates/work-item.md only when creating or checking a queued work item.

Load ../../templates/SPEC.md only when validating the linked build contract.

Load ../../templates/workflow-definition.md only when the work item instantiates a reusable workflow.

Load ../../templates/skill-architecture.md only when the linked spec has an architecture_id or the builder needs execution architecture constraints.

Load ../../adapters/patterns/work-queue.md only when explaining, exporting, or evaluating queue behavior.

Load ../../adapters/patterns/compiled-workflow.md only when a work item references a workflow definition or run ID.

Load ../../adapters/patterns/capability-broker.md only when semantic capabilities need concrete builder or adapter bindings.

Load ../../adapters/patterns/tool-capability-profile.md only when a queued work item needs a reusable, sensitive, or cross-runtime tool binding.

Load ../crow-pet-policy-gate/SKILL.md when the work item includes external writes, repo writes, auth-sensitive workflows, publication, spending, destructive actions, or sensitive context.

Load the selected builder skill only after the work item is ready.

Load contract.md and rubric.md only for acceptance or evaluation.

Dependency Edges

• delegates_to: selected builder skill such as crow-pet-codex-delegate, crow-pet-image, or another harness-backed specialist.
• uses_adapter: adapters/patterns/work-queue.md, adapters/patterns/compiled-workflow.md when needed, adapters/patterns/capability-broker.md, adapters/patterns/tool-capability-profile.md when needed, and selected harness, tool, model, or target adapters.
• loads_context: task record, approved SPEC.MD, optional workflow definition, optional skill architecture plan, work item, policy decision, and context capsule only when task memory affects execution.
• evaluates_with: contract.md, rubric.md, linked SPEC.MD, linked workflow definition, and handoff report.

Rules

• The work queue is a markdown package surface, not a background scheduler.
• One work item tracks one builder-ready unit of work.
• When workflow_id is present, the work item is one run instance of that workflow definition.
• SPEC.MD remains the build contract when present; the workflow definition remains the reusable procedure when present.
• The work item tracks lifecycle, assignment, evidence, and handoff.
• Preserve parallel read, sequenced write; do not run write stages in parallel.
• Block or ask before retrying write stages without a matching idempotency key.
• v.NEXT: GitHub Issues, Linear, event buses, and other trackers can become adapters; they are not current core behavior.
• Do not mark work accepted without verification evidence.