skills.rest
g-zenr
g-zenrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan

Decompose feature scopes into user stories, tasks, and risk assessments.

Updated Feb 13, 2026
Search Tags:#project management#task breakdown#agile#sprint planning#user stories#scrum
One-click install
npx skills add https://github.com/g-zenr/relay-api --skill plan-g-zenr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/g-zenr/relay-api --skill plan-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of breaking down large scopes or features into actionable user stories and tasks, ensuring clarity and efficient sprint planning.

Core Features & Use Cases

  • Scope Decomposition: Breaks down complex requirements into manageable vertical slices (stories).
  • Task Generation: Creates detailed, actionable tasks for each story.
  • Dependency Management: Orders stories based on identified dependencies.
  • Risk Assessment: Identifies technical and external risks associated with each story.
  • Use Case: A product manager needs to plan the next sprint for a new feature. They provide the feature's scope to this Skill, which then generates a structured sprint plan including stories, tasks, and risk assessments.

Quick Start

Use the plan skill to break down the scope of adding user authentication to the relay API.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I break down a large feature into user stories for sprint planning?▼

To break down features for sprint planning, decompose the project scope into well-defined user stories and granular tasks. This methodology structures requirements into vertical slices, ensuring clarity and efficient sprint execution.

What is the best way to structure agile user stories with acceptance criteria and risk assessments?▼

Structuring agile user stories requires defining acceptance criteria, identifying affected files, and estimating complexity. This generates a comprehensive sprint plan document that orders stories by dependency and includes detailed technical risk assessments.

How do I generate a sprint plan document ordered by task dependencies?▼

Generating a sprint plan ordered by task dependencies involves analyzing your feature scope to identify relationships between tasks. The output is a comprehensive sprint plan that sequences stories based on identified dependencies and technical risks.

Can I use this approach to manage task breakdown for a new API authentication scope?▼

Yes, you can manage task breakdown for an API authentication scope by providing the feature requirements. The process outputs a structured sprint plan including user stories, actionable tasks, and risk assessments tailored to that specific scope.

When do I need to decompose project scope into vertical slices for scrum?▼

You need to decompose project scope into vertical slices for scrum when a large feature requires clear, manageable user stories. This ensures your sprint planning includes granular tasks, acceptance criteria, and accurate complexity estimates.

Related Skills

Explore More Product & Management Skills→
darkroomengineeringdarkroomengineering
41

discovery

Guide structured interviews to define project scope and requirements.

Official
Intermediate
ldk-hubldk-hub

bmad-sprint-planning

Generate sprint-status.yaml from epic files with status detection and validation.

Community
Advanced
mahg-esmahg-es
3

pm-status

Generate sprint and project status reports with metrics and blockers.

Official
Intermediate
WebWakaHubWebWakaHub
20

Senior Project Manager

Convert project specifications into development task lists with acceptance criteria.

Official
Intermediate