writing-plans

Convert product specs into executable implementation plans with tasks and file paths.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Me1e/ralphthon --skill writing-plans-me1e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Me1e/ralphthon/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/Me1e/ralphthon --skill writing-plans-me1e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps engineers transform a raw product spec or requirements into a complete, execution-ready implementation plan that a developer can follow without context.

Core Features & Use Cases

  • Converts high-level goals into concrete tasks with exact file paths, test steps, and commit messages.
  • Supports planning across code, tests, docs, and deployment, with structured task granularity.
  • Generates plans saved to docs/plans/YYYY-MM-DD-<feature-name>.md for traceability.

Quick Start

Provide a spec or requirements for a multi-step task, and this skill will generate a detailed, bite-sized plan.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a product spec into an executable implementation plan?

To turn a product spec into an implementation plan, provide your requirements to generate a detailed, bite-sized task structure. This translates high-level goals into concrete steps with exact file paths, test procedures, and commit messages for developers.

What is the best way to break down multi-step development tasks for engineers?

The best way to break down multi-step development tasks is generating a structured plan covering code, tests, docs, and git records. This process converts high-level goals into bite-sized tasks with exact file paths and test steps.

How does planning for TDD workflows generate git commit structures?

Planning for TDD workflows generates git commit structures by translating specs into concrete tasks. Each task includes specific code changes, test steps, and predefined commit messages to ensure traceable, bite-sized development increments.

Can I use this to generate development plans for multi-step feature releases?

Yes, you can use this to generate development plans for multi-step feature releases. It supports planning across code, tests, docs, and deployment, saving structured task breakdowns to docs/plans/YYYY-MM-DD-<feature-name>.md for full traceability.

Where are generated implementation planning docs saved in the repository?

Generated implementation planning docs are saved to docs/plans/YYYY-MM-DD-<feature-name>.md. This file structure includes a header and detailed task breakdown, ensuring execution-ready plans are traceable within your repository.