writing-plans

Convert software specifications into executable implementation plans with tasks and code samples.

174|23|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/RedWoodOG/Hermes-Desktop --skill writing-plans-redwoodog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/RedWoodOG/Hermes-Desktop/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/RedWoodOG/Hermes-Desktop --skill writing-plans-redwoodog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams transform vague requirements and multi-step specs into precise, executable implementation plans that guide development and handoffs.

Core Features & Use Cases

  • Generate bite-sized tasks with exact file paths, complete code examples, and testing steps.
  • Enforce structured planning with TDD-focused tasks, frequent commits, and clear acceptance criteria.
  • Provide plan documentation suitable for handoff to subagents or teammates, including task sequencing and verification.

Quick Start

Provide a software spec and I will generate a detailed, task-by-task implementation plan with exact file paths, complete code samples, and testing steps.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a software specification into an executable implementation plan?

This approach decomposes multi-step features into bite-sized, verifiable tasks with precise file paths and complete code samples, ensuring every task is scoped and aligned with TDD acceptance criteria.

How do I break down complex workflows into bite-sized development tasks?

Breaking down complex workflows into bite-sized development tasks requires structuring multi-step features into sequenced items with exact file paths, complete code examples, and clear testing steps for frequent commits.

Does generating implementation plans with this approach support TDD workflows?

Generating implementation plans with this approach supports TDD workflows by enforcing structured planning with TDD-focused tasks, frequent commits, and precise acceptance criteria for every scoped item.

Can I use these implementation plans for handoff to subagents or teammates?

Yes, the generated plans provide documentation suitable for handoff to subagents or teammates, including precise task sequencing, exact file paths, complete code samples, and verification steps.

What is the best way to document multi-step feature implementation for engineering teams?

The best way to document multi-step feature implementation is transforming vague requirements into precise plans with exact file paths, complete code examples, and testing steps to guide development.