planning

Generate atomic implementation plans with exact file paths and verification commands.

3|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/alunadev/ald-skills --skill planning-alunadev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/alunadev/ald-skills/tree/main/skills/planning
Command: npx skills add https://github.com/alunadev/ald-skills --skill planning-alunadev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of breaking down complex features into manageable, executable steps, ensuring a clear and testable path from design to implementation.

Core Features & Use Cases

  • Atomic Task Breakdown: Divides work into single-commit tasks.
  • TDD Enforcement: Mandates writing failing tests before implementation.
  • Detailed Specifications: Requires exact file paths and code snippets.
  • Use Case: After a design is approved, use this skill to generate a step-by-step plan for developers, including specific tests to write and code to implement for each small task.

Quick Start

Use the planning skill to create a detailed implementation plan for the new user authentication feature.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I break down complex software features into atomic tasks for implementation?

Atomic task breakdown divides complex features into manageable, single-commit steps. This approach scopes work to individual commits, providing exact file paths, code snippets, and verification commands for a clear, testable path from design to implementation.

How do I enforce Test-Driven Development principles during task breakdown?

TDD enforcement in task planning mandates writing failing tests before implementation. By generating detailed specifications that pair exact code snippets with specific tests to write, the development cycle remains verifiable and strictly adheres to Test-Driven Development principles.

What is the best way to plan a commit strategy for TDD-focused development?

A TDD-focused commit strategy scopes tasks to individual commits with exact file paths and verification commands. This ensures granular task management and a verifiable development cycle, mapping each small test and code implementation step to a single commit.

Do I need an approved design before generating an implementation plan?

An approved design is required before generating an implementation plan. The planning process takes this approved design and creates detailed, atomic, step-by-step implementation instructions, including specific tests and code snippets for developers to execute.

How to generate step-by-step implementation plans with exact file paths and code snippets?

Generating step-by-step implementation plans involves transforming an approved design into atomic tasks. It requires detailed specifications with exact file paths, code snippets, and verification commands to satisfy the need for granular task management and verifiable development cycles.