skills.rest
ydemir
ydemirCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate structured implementation plans with standard headers and bite-sized tasks.

Updated Feb 28, 2026
Search Tags:#workflow#planning#tdd#software-engineering#task-breakdown#implementation-plan#git-commit
One-click install
npx skills add https://github.com/ydemir/openclawmaster --skill writing-plans-ydemir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ydemir/openclawmaster/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/ydemir/openclawmaster --skill writing-plans-ydemir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate comprehensive implementation plans for multi-step tasks before touching code, ensuring clear guidance for engineers, testers, and docs.

Core Features & Use Cases

  • Bite-sized task planning: breaks complex work into actionable steps with ownership and estimates.
  • Standardized planning document: enforces a consistent header and structure for easy sharing and auditing.
  • Deterministic workflow: guides steps from test-driven development to commits, keeping changes traceable.
  • Save and organize plans: saves plans to docs/plans/YYYY-MM-DD-<feature-name>.md for versioned planning.

Quick Start

Initiate planning for a feature and save the resulting plan to docs/plans/YYYY-MM-DD-<feature-name>.md.

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 a multi-step software feature into an actionable implementation plan?▼

Implementation plans break down multi-step software features into bite-sized, actionable tasks with ownership and estimates, ensuring clear guidance for engineers, testers, and documentation teams.

What is the best way to structure feature planning documents for test-driven development?▼

Feature planning documents enforce a standardized header and deterministic workflow, guiding steps from test-driven development to git commits to keep code changes traceable and reproducible.

Does this task planning workflow save implementation plans to a specific versioned location?▼

Task planning workflows save generated implementation plans to a fixed, versioned location at docs/plans/YYYY-MM-DD-<feature-name>.md for consistent organization and easy auditing.

Can I use this implementation planning approach for tasks with clear engineering and testing boundaries?▼

Implementation planning applies specifically when starting tasks with clear boundaries across engineering, testing, and documentation to ensure reproducible execution steps.

Why generate an implementation plan before touching code for complex feature work?▼

Generating an implementation plan before touching code ensures clear guidance for engineers, testers, and docs, preventing scope creep and keeping changes traceable through a deterministic workflow.

Related Skills

Explore More Software Engineering Skills→
adiomasadiomas

initializer-protocol

Initialize autonomous coding tasks with project detection and state machine setup.

Community
Basic
minhhhminhhh

writing-plans

Generate structured implementation plans with files, tests, and commit history.

Community
Intermediate
Jeff-StapletonJeff-Stapleton
1

implementation

Automate story implementation, build verification, and version control operations.

Community
Advanced
phyter1phyter1

breakdown

Convert architectural documents into structured development issues and task lists.

Community
Intermediate