work-scope

Decompose feature work into reviewable, single-purpose pull requests.

2|1|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/jamestexas/agents --skill work-scope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-scope
Source: https://github.com/jamestexas/agents/tree/main/skills/work-scope
Command: npx skills add https://github.com/jamestexas/agents --skill work-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose feature work into a sequence of reviewable, single-purpose PRs before coding begins, preventing large, unmanageable PRs.

Core Features & Use Cases

  • Accepts inputs like Linear tickets, GitHub issues, or free-form problem statements to anchor scope.
  • Phase-driven discovery: gather context, map the change surface, and decompose into independent work units.
  • Produces a sequence of focused PRs with a single purpose, each testable and mergable on its own.

Quick Start

Describe the feature or ticket, then generate a plan to decompose it into a sequence of focused PRs.

Frequently Asked Questions about work-scope

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

FAQPage Schema
How do I decompose a large feature into reviewable pull requests before coding?

Decomposing a large feature into reviewable pull requests involves breaking multi-file changes into a sequence of single-purpose, testable PRs. The workflow guides context gathering and change-surface discovery to map out independent units with clear dependencies.

What is the best way to split a multi-file change into single-purpose PRs?

Splitting a multi-file change into single-purpose PRs requires mapping the change surface and decomposing work into independent, testable units. Each generated PR must be mergable on its own while maintaining clear dependency sequences.

Can I use a Linear ticket ID or GitHub issue to anchor project planning and PR decomposition?

Yes, you can use a Linear ticket ID or GitHub issue to anchor project planning and PR decomposition. The workflow accepts these inputs alongside free-form problem statements to anchor scope and generate a focused PR sequence.

How does feature splitting prevent large unmanageable pull requests?

Feature splitting prevents large unmanageable pull requests by enforcing a phase-driven discovery process before coding begins. This approach ensures work is decomposed into a sequence of focused, single-purpose PRs that are independently testable and mergable.

Do I need a complete feature description to start decomposing work into reviewable PR units?

No, you do not need a complete feature description to start decomposing work into reviewable PR units. The workflow accepts Linear tickets, GitHub issues, or free-form problem statements to anchor scope and begin the change-surface discovery process.