writing-plans

Convert specs and requirements into structured implementation plans with tasks, file paths, and tests.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill writing-plans-chris-chai-minjae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill writing-plans-chris-chai-minjae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate vague specs into comprehensive, executable implementation plans that guide developers and subagents.

Core Features & Use Cases

  • Produce step-by-step task breakdowns with precise file paths, code templates, testing commands, and documentation touchpoints.
  • Support TDD-driven workflows by embedding tests and verification steps for each task.
  • Facilitate collaboration on multi-person projects by providing a shared, reproducible plan structure.

Quick Start

Create a complete implementation plan for the provided spec, detailing tasks, files, tests, and verification 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 software specs into actionable task breakdowns?

Implementation plans for complex software features support multi-step workflows and cross-team collaboration. They provide a shared, reproducible structure with architecture notes, precise file paths, and testing commands to coordinate multi-person projects effectively.

Does implementation planning support TDD-driven workflows?

Implementation planning is best suited for complex software features, multi-step workflows, and cross-team collaboration. It translates vague specs into comprehensive, executable plans, making it ideal for precise task breakdowns rather than simple, single-file edits.

What is the best way to structure implementation plans for cross-team collaboration?

The best way to structure implementation plans for cross-team collaboration is generating a shared, reproducible plan with a clear goal, architecture notes, task-by-task steps, and exact file paths. This ensures precise task breakdowns across multiple developers.

What should be included in an implementation plan to guide subagents effectively?

An implementation plan to guide subagents effectively should include a clear goal, architecture notes, task-by-task steps, exact file paths, code templates, testing commands, and verification criteria. This provides comprehensive, executable guidance for automated development.