writing-plans

Create structured implementation plans with file-level task breakdowns before coding.

Updated May 2, 2026
One-click install
npx skills add https://github.com/Qunnnn/agents --skill writing-plans-qunnnn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Qunnnn/agents/tree/main/skills/general/writing-plans
Command: npx skills add https://github.com/Qunnnn/agents --skill writing-plans-qunnnn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers transform unclear specifications into structured implementation plans that reduce uncertainty before code changes begin.

Core Features & Use Cases

  • Implementation Planning: Creates comprehensive plans with file mappings, architecture considerations, testing steps, and execution tasks.
  • Task Decomposition: Breaks large development work into small actionable steps with clear ownership and verification points.
  • Use Case: A developer receiving a new feature request can use this Skill to generate a complete plan covering affected files, implementation details, validation steps, and commit points before writing code.

Quick Start

Use the writing-plans skill to create an implementation plan for the provided feature requirements.

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 codebase changes into actionable steps?▼

You break down codebase changes by generating a complete plan that covers affected files, implementation details, validation steps, and commit points to reduce uncertainty before writing code.

Does this implementation planning approach work for architecture planning?▼

Yes, this implementation planning approach works for architecture planning by applying structured task decomposition and plan documentation conventions to multi-step software development workflows.

What's the best way to document engineering workflows before coding?▼

The best way to document engineering workflows is to use plan documentation conventions that specify file-level task breakdowns, testing steps, and execution tasks for feature specifications.

When do I need to write a detailed plan for codebase changes?▼

You need to write a detailed plan for codebase changes when handling multi-step software development tasks that require file-level task breakdowns and testing steps to reduce uncertainty.