sdlc-2-planning-and-task-breakdown

Decompose software specifications into dependency-aware task lists with acceptance criteria.

2|Updated Apr 30, 2026

Search Tags:#planning #development #architecture #agile #sdlc #task-breakdown

Ready to run

npx skills add https://github.com/ShaggyD/agent-toolkit --skill sdlc-2-planning-and-task-breakdown

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdlc-2-planning-and-task-breakdown
Source: https://github.com/ShaggyD/agent-toolkit/tree/main/development/sdlc-2-planning-and-task-breakdown
Command: npx skills add https://github.com/ShaggyD/agent-toolkit --skill sdlc-2-planning-and-task-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the common issue of agent drift and project stalling by enforcing a structured planning phase that breaks down complex requirements into manageable, verifiable units of work before implementation begins.

Core Features & Use Cases

Dependency Mapping: Visualizes the relationship between components to ensure foundational work is completed first.
Vertical Slicing: Guides the agent to build complete, testable feature paths rather than horizontal layers, ensuring the system remains in a working state.
Verification Checkpoints: Integrates explicit acceptance criteria and testing steps into every task to ensure high-quality, reliable output.
Use Case: When tasked with building a new user authentication system, this skill will break the project into specific tasks like database schema setup, API endpoint creation, and UI integration, ensuring each piece is verified before moving to the next.

Quick Start

Use the sdlc-2-planning-and-task-breakdown skill to generate an implementation plan for the current project specification.

Frequently Asked Questions about sdlc-2-planning-and-task-breakdown

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

FAQPage Schema

How do I break down complex software specifications into actionable tasks?▼

Breaking down complex software specifications into actionable tasks involves decomposing high-level requirements into ordered, dependency-aware task lists with explicit acceptance criteria. This prevents scope creep by enforcing structured planning before implementation begins.

What is vertical slicing in agile development planning?▼

Vertical slicing in agile development planning is a technique that guides building complete, testable feature paths rather than horizontal layers. This ensures your system remains in a working state throughout the development lifecycle.

How do I prevent agent drift and project stalling during software implementation?▼

Preventing agent drift and project stalling requires enforcing a structured planning phase that maps component dependencies and integrates verification checkpoints. This ensures foundational work is completed and verified first.

How do I add verification checkpoints to a task breakdown plan?▼

Adding verification checkpoints to a task breakdown plan involves integrating explicit acceptance criteria and testing steps into every decomposed task. This ensures high-quality, reliable output before moving to the next component.

Can I use this task breakdown approach for a user authentication system?▼

You can use this task breakdown approach for a user authentication system by splitting the project into specific tasks like database schema setup, API endpoint creation, and UI integration. Each piece is verified before moving to the next.

What is the best way to map dependencies for software architecture planning?▼

The best way to map dependencies for software architecture planning is to visualize relationships between components to ensure foundational work is completed first. This dependency mapping prevents implementation errors across complex features.