writing-plans

Create end-to-end implementation plans for software features with task breakdowns.

1|Updated Jan 5, 2023
One-click install
npx skills add https://github.com/riez/dots --skill writing-plans-riez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/riez/dots/tree/main/.config/agentic/skills/writing-plans
Command: npx skills add https://github.com/riez/dots --skill writing-plans-riez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before touching code, the skill lets you craft comprehensive, end-to-end implementation plans that document required steps, touched files, tests, docs, and a clear commit strategy so engineers can proceed with confidence.

Core Features & Use Cases

  • Generate bite-sized, task-driven implementation plans for features, bugs, or experiments.
  • Document which files to touch, code changes, testing strategy, and required docs.
  • Facilitate collaboration by providing a shared, repeatable plan template for handoffs and reviews.

Quick Start

Ask me to generate a complete implementation plan for a feature, including task breakdown, touched files, tests, docs, and a recommended commit sequence.

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 software feature before writing code?

An implementation plan breaks a feature into executable tasks covering file changes, testing strategy, documentation, and commit history. It guides engineers through task decomposition so they can proceed with confidence before touching code.

What is task decomposition in software engineering planning?

Task decomposition splits a feature specification into bite-sized, actionable steps. It identifies which files to touch, required code changes, and testing needs, providing a repeatable template for handoffs and reviews.

How do I document file changes and testing strategy for a new feature?

Document file changes and testing strategy using a structured implementation plan template. The plan records touched files, code modifications, required documentation, and a clear commit sequence to facilitate team collaboration.

Can I generate a step-by-step implementation plan from an existing specification?

Yes, if a spec exists but code changes are not yet defined, you can generate a complete end-to-end plan. It translates the specification into a task-driven breakdown covering tests, docs, and commit history.

What's the best way to plan a commit sequence for a multi-step software task?

Planning a commit sequence requires mapping out all file touches and code changes first. A structured implementation plan provides a recommended commit order that keeps the history clean and the changes reviewable.

When do I need a structured implementation plan for software engineering tasks?

You need a structured implementation plan when a feature spec exists but requires task decomposition before coding. It ensures risk assessment, documentation, and testing strategies are defined to support confident execution.