work-order

Create structured work orders with context, deliverables, verification, and completion criteria.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/disciplin-run-org/jjstack --skill work-order
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-order
Source: https://github.com/disciplin-run-org/jjstack/tree/main/skills/work-order
Command: npx skills add https://github.com/disciplin-run-org/jjstack --skill work-order

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It simplifies creating precise and unambiguous task instructions that ensure clarity and accountability in delegating work.

Core Features & Use Cases

  • Structured Templates: Guides users to generate comprehensive work orders with Context, Deliverables, Verify, and Done when sections.
  • Application Scenarios: Useful for handing off complex tasks between humans and agents, PR descriptions, plan breakdowns, and team handovers.
  • Real-World Example: Draft a detailed work order for a development team to implement a new feature, including clear acceptance criteria and verification steps.

Quick Start

Write a work order for updating the homepage to include a new hero section, specifying context, deliverables, verification, and completion criteria.

Frequently Asked Questions about work-order

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a clear work order for delegating complex tasks?

A structured work order for technical handoffs uses a standardized four-section format covering Context, Deliverables, Verify, and Done when sections. This template ensures unambiguous communication and accountability when delegating work across teams or tools.

What should be included in task delegation instructions for a development team?

Task delegation instructions for a development team should include context, specific deliverables, clear acceptance criteria, and verification steps. Using a structured work order template ensures the technical handover is comprehensive and leaves no ambiguity.

Can I use a structured work order for PR descriptions and plan breakdowns?

Yes, you can use a structured work order for PR descriptions and plan breakdowns. The standardized format is useful for handing off complex tasks between humans and agents, ensuring clear acceptance criteria and verification steps are always documented.

What is the best way to communicate technical handoffs to avoid ambiguity?

The best way to communicate technical handoffs without ambiguity is to generate a detailed work order. By separating Context, Deliverables, Verify, and Done when sections, teams ensure thorough task definition and precise verification across tools.

Does generating a work order require any specific project management dependencies?

Generating a work order requires no specific project management dependencies. It functions as a standalone template to standardize task delegation and team communication, ensuring clear instructions without needing external frameworks or platforms.