writing-plans

Generate implementation plans with file paths, code snippets, and test commands.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill writing-plans-geargrindadmin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Geargrindadmin/gg-agentic-harness/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill writing-plans-geargrindadmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating detailed, step-by-step implementation plans for software development tasks, ensuring clarity and reducing ambiguity for engineers.

Core Features & Use Cases

  • Comprehensive Planning: Generates plans with exact file paths, code snippets, testing instructions, and commit messages.
  • Bite-Sized Tasks: Breaks down complex features into small, actionable steps suitable for frequent commits and TDD.
  • Use Case: When tasked with implementing a new user authentication flow, this Skill will produce a detailed plan outlining every test to write, every file to modify, and every command to run, making the development process efficient and predictable.

Quick Start

Use the writing-plans skill to create an implementation plan for adding a new user profile page.

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 complex software development tasks into step-by-step implementation plans?

Implementation plans break down complex software development tasks by generating bite-sized steps with exact file paths, code snippets, testing commands, and commit messages. This reduces ambiguity and ensures predictable, efficient development.

What is the best way to generate a task breakdown that follows TDD principles?

To generate a task breakdown following TDD principles, create plans that outline every test to write, file to modify, and command to run. This enforces adherence to TDD, DRY, and YAGNI principles for frequent, actionable commits.

How do I create implementation plans with exact file paths and code snippets for engineers with limited context?

Creating implementation plans with exact file paths and code snippets involves detailing every modification and testing instruction required. This provides engineers with limited context a clear, comprehensive guide for multi-step software features.

Can I use detailed planning to automate my user authentication flow implementation?

Detailed planning can automate user authentication flow implementation by producing a comprehensive plan outlining every test, file modification, and command needed. This makes multi-step feature implementation efficient and predictable.

Does planning documentation need to include testing commands and commit messages?

Planning documentation should include testing commands and commit messages to ensure clarity and reduce ambiguity. This enforces bite-sized, actionable steps suitable for frequent commits and strict TDD adherence.