writing-plans

Create comprehensive implementation plans for multi-step engineering tasks.

Updated Nov 15, 2025

Search Tags:#planning #documentation #engineering #workflows #project-management #task-decomposition

Ready to run

npx skills add https://github.com/billh93/snchz --skill writing-plans-billh93

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when you have a spec or requirements for a multi-step task, before touching code

Core Features & Use Cases

Create comprehensive implementation plans that assume engineers have zero context and potentially questionable taste.
Document file touches, code, tests, docs, and deployment steps. Provide a clear roadmap from tasks to artifacts.
Use for brainstorming, planning, and TDD-oriented workflows to align teams.

Quick Start

Announce at start: I'm using the writing-plans skill to create the implementation plan.

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 multi-step engineering task?▼

To create an implementation plan, use the skill to document required tasks, file touches, code, tests, and deployment steps. This provides a clear roadmap from tasks to artifacts, ensuring team alignment before coding begins.

What is task decomposition in project management workflows?▼

Task decomposition in project management workflows involves breaking down multi-step requirements into specified tasks, artifacts, and checkpoints. This ensures planability and reusability across subsystems for engineering projects.

When do I need to write an implementation plan before writing code?▼

You need to write an implementation plan when you have a spec or requirements for a multi-step task. It articulates scope, files, tests, and docs across subsystems before engineers touch any code, ensuring zero context assumptions.

Can I use this planning approach for TDD-oriented workflows?▼

Yes, you can use this planning approach for TDD-oriented workflows. It supports brainstorming and planning by documenting file touches, required tests, and deployment steps to align teams on task scope and artifacts.

What is the best way to document file touches and deployment steps for engineering projects?▼

The best way to document file touches and deployment steps is to create a comprehensive implementation plan. It provides a clear roadmap from tasks to artifacts, ensuring engineers understand scope, tests, and docs across subsystems.

Does this implementation planning method assume engineers have prior project context?▼

No, this implementation planning method assumes engineers have zero context and potentially questionable taste. It specifies required tasks, artifacts, and checkpoints to ensure planability and reusability without relying on prior knowledge.