skills.rest
wimpysworld
wimpysworldOFFICIAL
Explore all skills by this author →
WebsiteGitHub

work-order-format

Defines the document structure for cycle work orders in Linear.

716|31|Updated Mar 13, 2023
Search Tags:#parallel execution#linear#cycle planning#work order#document format#Issue tracking#wave dependencies
One-click install
npx skills add https://github.com/wimpysworld/nix-config --skill work-order-format
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-order-format
Source: https://github.com/wimpysworld/nix-config/tree/main/home-manager/_mixins/agentic/assistants/skills/work-order-format
Command: npx skills add https://github.com/wimpysworld/nix-config --skill work-order-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams coordinating parallel work in Linear need a consistent work order document format so that waves, dependencies, and deferred items are written and patched the same way every time, avoiding drift between creation and update commands.

Core Features & Use Cases

  • Document contract: Specifies the title pattern, cycle parent, and section order (waves, Sequencing, Timing, Deferred) for the single cycle work order document.
  • Wave rules: Enforces wave headings with dependency lines, strict intra-wave parallelism, and stable wave numbering that is never reused or renumbered.
  • Entry formats: Standardizes issue bullets with size and rationale, plus deferred entries with date and reason.
  • Use Case: When a command creates or patches a cycle work order in Linear, this contract ensures Wave 3 reads needs Wave 1, runs parallel with Wave 2 and every issue bullet follows the same key-title-size-reason form.

Quick Start

Use the work-order-format skill to write the cycle work order document for the current Linear cycle.

Frequently Asked Questions about work-order-format

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

FAQPage Schema
How do I structure a cycle work order document in Linear?▼

Title it with the user's first name and cycle number, parent it on the cycle, then list wave sections in order followed by Sequencing, Timing, and Deferred sections. Each wave heading includes a dependency line such as needs Wave 1 or starts immediately.

How do I show dependencies between waves in a work order?▼

Write the dependency in the wave heading after the arrow symbol, listing every prerequisite wave. If the wave is independent of another unfinished wave, append runs parallel with Wave followed by that wave's number.

Can two issues in the same wave run sequentially?▼

No, waves are strictly parallel, so every issue in a wave runs in parallel with every other issue in that wave. A sequential dependency forces the issue into a later wave, and issue-level constraints belong under the Sequencing section.

What happens when a wave becomes empty in a work order?▼

Remove the empty wave's section but never reuse its number, since wave numbering is stable. A new wave takes the next unused number and is appended at the end of the wave sections.

How should deferred issues be recorded in a work order?▼

Add each deferred issue to the Deferred section as a bullet with the issue key, the deferral date, and a one-line reason. Omit the entire Deferred section when it is empty.

Related Skills

Explore More Product & Management Skills→
pkuppenspkuppens

issue-estimate

Assign XS-XL size estimates to issues with concise rationale metadata.

Community
Basic
tinner-deinnotinner-deinno

gsd-execute-phase

Execute workflow phase plans with wave-based parallel orchestration.

Community
Intermediate
tuanldastuanldas

wave-parallelism

Execute independent tasks in parallel waves with dependency analysis and file ownership.

Community
Advanced
GainInsightDevGainInsightDev

af-plan-work-cycles

Plan weekly work cycles and prioritize backlogs using Linear issue states and estimates.

Official
Advanced