work-decompose

Decompose work groups into work definitions with dependency graphs and verification criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nathannorthcutt/jlsm --skill work-decompose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-decompose
Source: https://github.com/nathannorthcutt/jlsm/tree/main/.claude/skills/work-decompose
Command: npx skills add https://github.com/nathannorthcutt/jlsm --skill work-decompose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a work group into individual work definitions with clearly delineated scope, dependencies, and acceptance criteria.

Core Features & Use Cases

  • Automatically identify natural boundaries, artifact dependencies, and interface contracts within a work group.
  • Generate a dependency graph that enforces correct ordering between work definitions.
  • Integrate with existing /work structures to bootstrap planning after creating a goal.

Quick Start

Create a work group with /work "<goal>" and run /work-decompose "<group-slug>" to generate initial work definitions.

Frequently Asked Questions about work-decompose

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

FAQPage Schema
How do I decompose a project goal into actionable work definitions?

To decompose a project goal, this Skill analyzes the group's scope, boundaries, and interfaces to generate structured work definitions with dependency graphs and acceptance criteria. It outputs WD-*.md files under the .work/<group-slug>/ directory.

How does dependency graph generation work for work decomposition?

Dependency graph generation works by identifying artifact dependencies and interface contracts within a work group, then structuring the work definitions to enforce correct execution ordering. This ensures tasks are planned and executed in the proper sequence.

Can I use this to generate work definitions for an existing /work structure?

Yes, you can use this to bootstrap planning for an existing /work structure. After creating a work group with /work "<goal>", run /work-decompose "<group-slug>" to automatically generate the initial work definitions.

What is the best way to identify boundaries and interfaces for work planning?

The best way to identify boundaries and interfaces for work planning is to analyze the work group's scope automatically. This approach delineates natural task limits and maps interface contracts to produce a structured plan of work definitions.

Do I need any dependencies to generate work definition markdown files?

No dependencies are required to generate work definition markdown files. The Skill operates independently to analyze your work group and produce draft WD-*.md files with clear dependencies and verification criteria.

What format does the work decomposition output use for project management?

The work decomposition output uses markdown files formatted as WD-*.md, stored under .work/<group-slug>/. Each file represents an individual work definition with a draft status, dependency mappings, and verification criteria.