scope

Convert design files into atomic tasks with GitHub milestones and issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps transform a design or plan into a structured set of atomic, actionable tasks with milestones and issues for a team to execute.

Core Features & Use Cases

  • Auto-scope a design into atomic tasks with clear boundaries.
  • Generate GitHub milestones and issues per task.
  • Produce a SCOPES.yml with task metadata for project tracking.
  • Use during design-to-implementation planning for product or software projects.

Quick Start

Execute scoping on a design file to generate tasks. You would provide a path to the design file and let the skill output the SCOPES.yml and a plan for GitHub issues.

Frequently Asked Questions about scope

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

FAQPage Schema
How do I convert a design file into atomic executable tasks for a team?

To convert a design file into atomic executable tasks, you need a scoping tool that analyzes the design, identifies task boundaries, and enforces acceptance criteria to ensure each task is complete and actionable for team execution.

How do I generate GitHub milestones and issues from a project plan?

You can generate GitHub milestones and issues from a project plan by using a design-to-tasks scoping tool that parses the plan, breaks it down into atomic tasks, and automatically creates the corresponding milestones and issues for project tracking.

What is a SCOPES.yml manifest and when do I need it for project planning?

A SCOPES.yml manifest is a structured file containing task metadata used for project tracking. You need it during design-to-implementation planning to maintain a clear record of atomic task boundaries, acceptance criteria, and documentation requirements.

Can I automatically break down a software design into actionable sub-tasks?

Yes, you can automatically break down a software design into actionable sub-tasks by running a scoping skill that evaluates the design file, enforces strict task boundaries, and outputs a structured task plan with clear acceptance criteria.

What is the best way to ensure development tasks have clear boundaries and acceptance criteria?

The best way to ensure tasks have clear boundaries and acceptance criteria is to use a design-to-tasks scoping process that enforces these constraints structurally, generating a manifest and issues that define exactly what makes each atomic task complete.