skills.rest
gmliao
gmliaoCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate standardized implementation plans for multi-step coding tasks.

1|Updated Nov 22, 2025
Search Tags:#planning#documentation#workflows#software-engineering#plan-execution#task-breakdown
One-click install
npx skills add https://github.com/gmliao/swift-state-tree --skill writing-plans-gmliao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/gmliao/swift-state-tree/tree/main/.agent/skills/Superpowers/writing-plans
Command: npx skills add https://github.com/gmliao/swift-state-tree --skill writing-plans-gmliao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams articulate a clear, actionable plan for multi-step tasks before coding, reducing ambiguity and rework.

Core Features & Use Cases

  • Comprehensive task planning: outlines the entire feature work, including files to touch, tests to write, docs to check, and commit history.
  • DRY, TDD-driven planning: emphasizes reusability, test-driven steps, and frequent commits to maintainable progress.
  • Plan execution guidance: provides a ready-to-follow plan with bite-sized tasks suitable for collaboration or solo work.

Quick Start

Create a new plan document for a feature, saved to docs/plans/YYYY-MM-DD-<feature-name>.md, and start by listing the tasks in bite-sized steps, followed by the minimal implementation notes.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a software feature spec into actionable implementation steps?▼

Task breakdown for software engineering involves generating a standardized plan structure from your spec. This process outlines files to touch, tests to write, and commits, saving the actionable plan to docs/plans with a date-based filename.

What is the best way to plan multi-step engineering tasks before coding?▼

The best way to plan multi-step engineering tasks is generating a comprehensive document emphasizing reusability and test-driven steps. This creates a ready-to-follow plan with bite-sized tasks, reducing ambiguity and rework before coding begins.

How do I create a TDD-driven plan with frequent commits for feature development?▼

A TDD-driven plan is created by outlining feature work into bite-sized, test-first steps within a standardized plan structure. The generated document emphasizes reusability and frequent commits to maintain traceable execution progress.

Do I need any specific dependencies to generate task execution workflows?▼

No dependencies are required to generate task execution workflows. The skill operates independently to produce standardized plan documents and guide step-by-step execution for software engineering tasks.

Where are generated implementation plans saved in my project?▼

Generated implementation plans are saved directly to docs/plans with a date-based filename formatted as YYYY-MM-DD-<feature-name>.md. This ensures traceable execution and easy access for collaboration or solo work.

Related Skills

Explore More Software Engineering Skills→
NebulaMaoNebulaMao
13

speckit-plan

Generate technical implementation plans from feature specifications.

Community
Advanced
AissenLiuAissenLiu

writing-plans

Generate end-to-end implementation plans with file paths, code examples, and testing steps.

Community
Advanced
DYAI2025DYAI2025

implementation-phase

Guide TDD-driven feature implementation with continuous testing and anti-duplication checks.

Community
Advanced
ThalfmanThalfman

to-issues

Convert project plans into issues with labels and dependencies in an issue tracker.

Community
Intermediate