plan-issues

Decompose scoped software changes into dependency-aware implementation work plans.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/robertolopezlopez/agent-skills --skill plan-issues-robertolopezlopez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-issues
Source: https://github.com/robertolopezlopez/agent-skills/tree/main/skills/core/plan-issues
Command: npx skills add https://github.com/robertolopezlopez/agent-skills --skill plan-issues-robertolopezlopez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps transform understood software changes into clear, dependency-aware implementation plans when teams need actionable work breakdowns instead of open-ended investigation.

Core Features & Use Cases

  • Vertical Slice Planning: Break features, fixes, and refactors into small end-to-end work items with clear ownership and validation paths.
  • Dependency Analysis: Identify blockers, sequencing needs, and relationships between implementation tasks before execution begins.
  • Use Case: Prepare a ready-to-execute plan from a scoped feature request by defining ordered work items, agent suitability, and recommended follow-on workflows.

Quick Start

Ask the plan-issues skill to decompose this scoped change into dependency-aware vertical slices with validation steps.

Frequently Asked Questions about plan-issues

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

FAQPage Schema
How do I break down a scoped software change into an implementation work plan?

Vertical slice planning breaks features, fixes, and refactors into small end-to-end work items that deliver value independently. Each slice includes clear ownership boundaries and validation paths, ensuring implementation tasks are executable, testable, and properly sequenced before development begins.

How do I identify task dependencies and sequencing for a feature implementation?

Dependency analysis identifies blockers, sequencing needs, and relationships between implementation tasks before execution begins. This process maps task relationships within the work plan, ensuring proper coordination and revealing execution order constraints across vertical slices.

Can I use this for refactoring and bug fixes or is it only for new features?

Yes, dependency-aware work plan decomposition applies to feature requests, bug fixes, and refactoring scenarios. As long as the change scope and goals are already understood, the Skill transforms any scoped software change into executable vertical slices with validation steps.

What's the best way to prepare a scoped change for execution readiness?

You need a scoped software change where goals are already understood and clearly defined. This Skill does not perform open-ended investigation; it requires structured input ready for task slicing, dependency identification, and validation planning to produce an actionable implementation work plan.