writing-plans

Generate implementation plans for multi-step software tasks with date-based filenames.

69|19|Updated Jan 26, 2026

Search Tags:#planning #templates #documentation #task breakdown #plans #software-engineering

Ready to run

npx skills add https://github.com/alffei/skill_share --skill writing-plans-alffei

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/alffei/skill_share/tree/main/superpowers-antigravity/skills/writing-plans
Command: npx skills add https://github.com/alffei/skill_share --skill writing-plans-alffei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate comprehensive implementation plans for multi-step tasks based on an existing spec or requirements before coding.

Core Features & Use Cases

Structured planning: Create end-to-end implementation plans outlining touched files, code structure, tests, and docs.
Pre-coding guidance: Provides bite-sized tasks to ensure DRY, YAGNI, and TDD principles are followed.
Use Case: When starting a new feature, produce a plan that details the steps, artifacts, and verification criteria.

Quick Start

Use the writing-plans skill to create an implementation plan for a new feature. Save the plan to docs/plans/YYYY-MM-DD-<feature-name>.md with the standard header and a task-by-task breakdown.

Frequently Asked Questions about writing-plans

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

FAQPage Schema

How do I generate an implementation plan for a multi-step software development task?▼

To generate an implementation plan, provide your existing spec or requirements to create a structured task breakdown. The plan outlines touched files, code structure, tests, and verification criteria before you begin coding.

What is task breakdown in software engineering planning and when do I need it?▼

Task breakdown divides a multi-step feature into bite-sized coding tasks to enforce DRY, YAGNI, and TDD principles. You need it when starting a new feature that requires structured pre-coding guidance and detailed documentation.

How to create an implementation plan that enforces DRY, YAGNI, and TDD principles?▼

Create an implementation plan by feeding your feature spec into the planner, which structures the work into bite-sized tasks. This enforces DRY, YAGNI, and TDD principles by detailing specific steps, artifacts, and verification criteria.

Does this implementation plan generator work with existing requirements and specs?▼

Yes, this implementation plan generator works directly with your existing specs or requirements. It uses them as the input to produce a comprehensive end-to-end plan with a task-by-task breakdown.

Where are generated implementation plans saved and what format do they use?▼

Generated implementation plans are saved as markdown files in the docs/plans directory. They use a date-based filename format, specifically docs/plans/YYYY-MM-DD-<feature-name>.md, ensuring chronological organization.

What should a software implementation plan include for pre-coding guidance?▼

A software implementation plan should include touched files, code structure, tests, and documentation. It provides bite-sized tasks and verification criteria to ensure structured pre-coding guidance and adherence to engineering principles.