writing-plans

Name: writing-plans
Availability: InStock
Author: GaryOcean

Generate step-by-step implementation plans for software development tasks.

Updated Feb 16, 2026

Search Tags:#planning #tdd #documentation #software development #implementation #task breakdown

Ready to run

npx skills add https://github.com/GaryOcean428/vex-agent --skill writing-plans-garyocean428

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/GaryOcean428/vex-agent/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/GaryOcean428/vex-agent --skill writing-plans-garyocean428

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of creating clear, actionable implementation plans for software development tasks, ensuring engineers have all necessary context and step-by-step guidance.

Core Features & Use Cases

Comprehensive Planning: Generates detailed plans including file modifications, code snippets, testing procedures, and commit messages.
Structured Task Breakdown: Divides complex tasks into small, manageable steps suitable for TDD and frequent commits.
Use Case: Before starting a new feature, use this Skill to generate a plan that outlines every test to write, every line of code to implement, and every command to run, ensuring a smooth development process.

Quick Start

Use the writing-plans skill to create an implementation plan for adding user authentication.

Frequently Asked Questions about writing-plans

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

FAQPage Schema

How do I generate a detailed implementation plan for software development tasks?▼

To generate a detailed implementation plan, provide your software development task to get step-by-step guidance. The plan outlines specific files to modify, code to write, tests to execute, and commit messages to use, ensuring clarity for engineers with limited context.

What is the best way to break down complex software features into manageable TDD steps?▼

Breaking down complex software features into manageable TDD steps involves dividing tasks into small increments suitable for frequent commits. This approach supports TDD, YAGNI, and DRY principles for efficient development workflows by outlining every test to write and command to run.

Can I use structured task breakdown for adding user authentication without prior context?▼

Yes, structured task breakdown works for adding user authentication without prior context. Generating a comprehensive plan outlines every line of code to implement and every command to run, ensuring a smooth development process for engineers with limited project context.

Does implementation planning support YAGNI and DRY principles for efficient development workflows?▼

Implementation planning explicitly supports YAGNI and DRY principles for efficient development workflows. The generated plans structure complex tasks into small, manageable steps suitable for TDD and frequent commits, ensuring developers only build what is necessary without duplication.

What should be included in a software implementation plan to ensure clarity for engineers?▼

A software implementation plan should include comprehensive details like file modifications, code snippets, testing procedures, and commit messages. Providing these specific elements ensures engineers have all necessary context and step-by-step guidance before starting a new feature.