writing-plans

Generate implementation plans with file paths, code samples, and tests.

Updated Jan 30, 2026

Search Tags:#planning #testing #documentation #software-engineering #task-breakdown #code-samples #implementation-plan

Ready to run

npx skills add https://github.com/liamtran96/msm-car-booking --skill writing-plans-liamtran96

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/liamtran96/msm-car-booking/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/liamtran96/msm-car-booking --skill writing-plans-liamtran96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates comprehensive, task-ready implementation plans for software features when engineers have zero context about the codebase. It articulates exactly what to implement, where to modify, and how to verify success, including file paths, code examples, tests, and documentation touchpoints.

Core Features & Use Cases

Detailed task breakdown: Produces precise, step-by-step tasks covering frontend, backend, tests, and docs.
Zero-context usability: Generates complete plans from a design without requiring prior codebase knowledge.
Verification-focused: Includes testing strategies, acceptance criteria, review checkpoints, and deployment notes.
Planning discipline: Enforces DRY, YAGNI, and TDD principles; saves plans to a standardized location for traceability.

Quick Start

Run the writing-plans skill to generate a complete implementation plan for a new feature, saved to plans/YYYYMMDD-<feature-name>.md.

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 software feature without prior codebase context?▼

To generate a zero-context implementation plan, you input a completed software design and the tool outputs exact file paths, code samples, tests, and documentation steps. It produces task-ready plans without requiring prior knowledge of your codebase.

What is a zero-context engineering plan and when do I need one?▼

A zero-context engineering plan is a comprehensive task breakdown detailing exactly what to implement, where to modify files, and how to verify success. You need one when a design is complete but engineers lack existing codebase knowledge to start coding.

Does the generated implementation plan include testing and verification steps?▼

Yes, the generated implementation plan includes specific testing strategies, acceptance criteria, review checkpoints, and deployment notes. It strictly enforces Test-Driven Development (TDD) principles alongside DRY and YAGNI to ensure verification-focused task breakdowns.

How to create a task breakdown that covers frontend, backend, and documentation?▼

You create a comprehensive task breakdown by running the planning skill on a finished design. It produces precise, step-by-step tasks covering frontend, backend, tests, and documentation touchpoints, saving the plan to a standardized markdown file.

What is the best way to structure implementation plans for traceability?▼

The best way to structure implementation plans for traceability is to save them to a standardized directory using a date-prefixed naming convention. The tool automatically saves generated plans to plans/YYYYMMDD-feature-name.md for consistent retrieval.

Can I generate a task-ready implementation plan if I only have a high-level design?▼

Yes, you can generate a task-ready implementation plan from a high-level design as long as the design phase is complete. The plan articulates exact modification locations, code examples, and verification steps, bridging the gap between design and coding without prior codebase knowledge.