wo-plan

Research codebases and produce ordered file-level implementation plans for work orders.

Updated Aug 23, 2026

Search Tags:#planning #codebase #implementation #work-order #sprint readiness

Ready to run

npx skills add https://github.com/mattfuster/aisef-setup --skill wo-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wo-plan
Source: https://github.com/mattfuster/aisef-setup/tree/main/.claude/skills/wo-plan
Command: npx skills add https://github.com/mattfuster/aisef-setup --skill wo-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create file-level implementation plans for specific work orders by researching the repository and producing an ordered list of file changes.

Core Features & Use Cases

Research the codebase before planning to ensure alignment with existing patterns and conventions.
Generate an implementation plan that lists target files in a precise, ordered sequence across models, repositories, services, API routes, and UI layers.
Present the plan for approval and attach it to the work order, enabling the backlog -> ready transition.
Use cases include preparing WO-123 for sprint readiness and coordinating across engineering roles to implement defined changes.

Quick Start

Create an implementation plan for WO-123 to move the work order from backlog to ready.

Frequently Asked Questions about wo-plan

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

FAQPage Schema

How do I plan file-level implementation steps for a specific work order?▼

Plan file-level implementations by researching the codebase and producing an ordered list of file changes. The plan targets files across models, repositories, services, APIs, and UI layers to ensure all architectural layers are covered.

What is the best way to move a work order from backlog to sprint ready?▼

Move a work order from backlog to ready by creating an implementation plan that lists target files in a precise sequence. The plan is attached to the work order after it is presented for approval, enabling the sprint readiness transition.

Does the implementation plan enforce existing codebase conventions and patterns?▼

The implementation plan requires strict adherence to existing conventions and patterns. It researches the codebase before planning to ensure alignment and flags scope concerns for potential work order splits when boundaries are exceeded.

Can I coordinate multi-file updates across different engineering roles with this approach?▼

Coordinate multi-file updates across engineering roles by generating a plan that guides teams through cross-layer patterns. The ordered sequence spans models, repositories, services, API routes, and UI layers to synchronize implementation efforts.

When should I split a work order instead of proceeding with a single implementation plan?▼

Split a work order when the planning process flags scope concerns during codebase research. If the required file changes exceed manageable boundaries or cross too many layers, the plan recommends potential splits before applying changes.