writing-plans

Generate implementation plans with YAML frontmatter and markdown saved to docs/plans.

Updated Dec 20, 2023
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill writing-plans-thiago-cruz-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Thiago-Cruz-eng/Hibrygame/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill writing-plans-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing implementation plans upfront prevents costly rework by clarifying scope, file touchpoints, testing strategy, and execution handoff before any code changes.

Core Features & Use Cases

  • Multi-step engineering planning: Breaks work into bite-sized tasks with explicit commands and expected outcomes so an engineer can execute with low ambiguity.
  • File- and test-aware instructions: Specifies exact paths to create/modify and ties each change to a concrete test to run.
  • Execution-ready handoff: Produces a saved plan document and prompts an option for subagent-driven or parallel execution workflows.

Quick Start

Use the writing-plans skill when you have requirements for a multi-step task and want an engineer-ready plan saved under docs/plans with task-by-task guidance.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan for a complex engineering task?

You generate an implementation plan by providing task requirements to produce a structured markdown document with granularized steps, exact file modifications, deterministic testing commands, and commit-ready checkpoints saved under docs/plans.

What is task granularization in software engineering planning?

Task granularization breaks multi-step engineering work into bite-sized tasks with explicit commands and expected outcomes, ensuring engineers can execute changes with low ambiguity and clear execution handoff.

Do I need existing codebase context to generate engineering handoff documentation?

No, you do not need existing codebase context. The generated implementation plans provide comprehensive file- and test-aware instructions so teams can execute complex changes without prior codebase knowledge.

Can I use test-driven development commands in a multi-step engineering plan?

Yes, the implementation plan ties each specified file modification to a concrete test-driven development command to run, ensuring deterministic testing throughout the execution workflow.

What's the best way to structure git workflow checkpoints for task breakdown?

The best way to structure git workflow checkpoints is through a saved plan document that includes commit-ready checkpoints for each granularized task, prompting options for subagent-driven or parallel execution workflows.

Why does implementation planning prevent costly rework before touching code?

Implementation planning prevents rework by clarifying scope, file touchpoints, testing strategy, and execution handoff upfront, ensuring teams execute complex changes with low ambiguity before any code changes occur.