wo-create

Generate Work Orders from blueprints, FRDs, or ad-hoc conversations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mattfuster/aisef-setup --skill wo-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wo-create
Source: https://github.com/mattfuster/aisef-setup/tree/main/.claude/skills/wo-create
Command: npx skills add https://github.com/mattfuster/aisef-setup --skill wo-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation of Work Orders by translating blueprint insights and ad-hoc discussions into actionable tasks, backlog items, and planning scaffolding.

Core Features & Use Cases

  • Automatic WO generation from blueprints or ad-hoc triggers to accelerate planning.
  • Backlog management and intake triage to prepare WOs for sprint planning.
  • Clear ownership and scoping to ensure WOs can ship via independent PRs.

Quick Start

Tell me to break down a blueprint into work orders or to create an ad-hoc WO, and I will generate the initial backlog entries.

Frequently Asked Questions about wo-create

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

FAQPage Schema
How do I break down a blueprint into actionable work orders?

Breaking down a blueprint into work orders involves decomposing requirements and FRDs into actionable backlog items. Each work order is scoped for a single PR, assigned to a single owner, and tracked with clear acceptance criteria for sprint planning.

What is the best way to create ad-hoc work orders from conversations?

Creating ad-hoc work orders from conversations translates unstructured discussions into structured backlog entries. The skill generates intake items ready for triage, ensuring each work order has clear ownership and is sized for an independent PR.

How does backlog triage work for sprint planning?

Backlog triage for sprint planning organizes generated work orders by reviewing intake items and preparing them for assignment. The process ensures each work order is properly scoped for a single PR and has defined acceptance criteria before sprint commitment.

Can I generate work orders from an FRD for requirements breakdown?

Yes, you can generate work orders from an FRD for requirements breakdown. The skill automates the translation of functional requirements documents into scoped backlog items, ensuring each work order maps to a single PR with a designated owner.

Do I need a blueprint to create work orders, or can I start from ad-hoc requests?

You do not need a blueprint to create work orders. The skill supports both blueprint decomposition and ad-hoc triggers, allowing you to generate backlog items directly from conversations or immediate requirements without prior documentation.

Why should each work order be scoped for a single PR?

Scoping each work order for a single PR ensures clear ownership and independent shipping capability. This constraint streamlines backlog management by keeping work orders actionable and simplifies tracking during sprint planning and intake triage.