writing-plans

Generate implementation plans with task decomposition, file touchpoints, and testing strategies.

1|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/darthlinuxer/Agentic-Skills --skill writing-plans-darthlinuxer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/darthlinuxer/Agentic-Skills/tree/main/writing-plans
Command: npx skills add https://github.com/darthlinuxer/Agentic-Skills --skill writing-plans-darthlinuxer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to produce thorough, executable plans for complex, multi-component tasks, ensuring every necessary step, file touchpoints, and validation approach is captured before implementation.

Core Features & Use Cases

  • Comprehensive implementation plan documents detailing required files to touch, code samples, testing strategy, and verification steps.
  • Bite-sized Task Granularity: breaks work into small, verifiable tasks aligned with TDD, DRY, and YAGNI.
  • Collaboration and tracking: saves plans to docs/plans/YYYY-MM-DD-<feature-name>.md and supports branch isolation for isolated development.

Quick Start

Ask the Skill to generate a complete implementation plan for a new feature, then follow the plan step-by-step to implement and verify it.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan for a complex multi-component software project?

To create an implementation plan for a complex multi-component project, you generate a structured plan document detailing required file touchpoints, task decomposition, testing strategies, and verification steps to guide development.

What is task decomposition in software engineering and how does it help with TDD?

Task decomposition breaks complex work into bite-sized, verifiable tasks aligned with TDD, DRY, and YAGNI principles, ensuring every step is small enough to test and validate before moving forward.

Can I use a structured plan document for branch isolation during feature development?

Yes, a structured plan document supports branch isolation by saving plans to dated markdown files like docs/plans/YYYY-MM-DD-<feature-name>.md, allowing developers to track and execute features in isolated branches.

Does this planning approach work for projects starting from zero-context briefs?

Yes, this planning approach works from zero-context briefs by generating comprehensive implementation plans that capture required files, code samples, and verification protocols through to final delivery.

What's the best way to plan file touchpoints and testing strategies for new features?

The best way to plan file touchpoints and testing strategies is to generate a complete implementation plan document that outlines every necessary file modification, code sample, and validation approach before starting implementation.