scope

Convert backlog items into detailed development plans with acceptance criteria.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/athan-dial/skills --skill scope-athan-dial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope
Source: https://github.com/athan-dial/skills/tree/main/plugins/dev/skills/scope
Command: npx skills add https://github.com/athan-dial/skills --skill scope-athan-dial

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It simplifies the process of refining and clarifying project scope before development, ensuring clear, verifiable plans.

Core Features & Use Cases

  • Scope Planning: Converts backlog items or freeform ideas into detailed, actionable plans for development.
  • Codebase Exploration: Reads project files to check current states and relevant context.
  • Use Case: A developer can quickly create a scoped plan for a feature request by inputting the backlog ID or description, streamlining pre-development review and task breakdown.

Quick Start

Use the scope skill to create a detailed plan for backlog item 123 or to define a new scope from a user description.

Frequently Asked Questions about scope

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

FAQPage Schema
How do I convert a backlog item into a detailed development plan?

To convert a backlog item into a development plan, input the backlog ID or freeform description. The system reads project context, asks clarifying questions, decomposes tasks, and verifies acceptance criteria to produce an actionable plan.

How does task decomposition work for agile project planning?

Task decomposition for agile project planning works by analyzing your project scope and breaking down high-level backlog ideas into smaller, actionable development tasks with clear, verifiable acceptance criteria.

Can I use codebase exploration to check current project context before scoping a feature?

Yes, you can use codebase exploration to check current project context before scoping. The system reads existing project files to understand current states, ensuring newly scoped development plans align with relevant code.

Do I need existing project files to define a new scope from a user description?

You do not need existing project files to define a new scope. You can input a freeform idea or user description directly, and the system will generate a detailed development plan by asking clarifying questions.

What is the best way to refine project scope before development?

The best way to refine project scope before development is to convert backlog ideas into structured plans using clarifying questions and task decomposition. This ensures clear, verifiable plans are established prior to coding.