writing-plans

Generate structured, test-driven implementation plans for software development tasks.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/projectedanx/hermes-agent --skill writing-plans-projectedanx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/projectedanx/hermes-agent/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/projectedanx/hermes-agent --skill writing-plans-projectedanx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of vague, overwhelming project requirements by forcing a structured, TDD-based decomposition of work into manageable, 2-5 minute tasks.

Core Features & Use Cases

  • Structured Planning: Enforces a standardized document format including architecture, tech stack, and granular task lists.
  • TDD Integration: Mandates a test-driven development cycle for every task to ensure code quality and reliability.
  • Use Case: When tasked with building a new authentication module, this skill will break the requirement down into specific, verifiable steps like creating the user model, adding password hashing, and writing unit tests for each component.

Quick Start

Use the writing-plans skill to generate a detailed implementation plan for the new user authentication feature.

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 complex software development goals into manageable tasks?

To break down complex software development goals, you need a structured decomposition approach that enforces granular task breakdown. This skill generates detailed implementation plans, dividing vague project requirements into verifiable 2-5 minute tasks for consistent execution.

What is the best way to write a test-driven development plan for a new feature?

Writing a test-driven development plan requires mandating a TDD cycle for every task to ensure code quality. This skill generates structured documentation enforcing TDD principles, exact file path specification, and standardized architecture details for your feature design.

Does this structured planning approach work for architectural planning and subagent task delegation?

Yes, structured planning applies directly to architectural planning and subagent task delegation workflows. It generates standardized documents with tech stack details and granular task lists, ensuring delegated subagent tasks have exact file paths and verifiable steps.

How do I create an implementation plan that specifies exact file paths and task lists?

Creating an implementation plan with exact file paths requires a standardized document format. This skill enforces granular task breakdown and precise file path specification within its structured output, ensuring every development step is mapped for consistent execution.

Why should I use TDD principles for decomposing overwhelming project requirements?

Using TDD principles for decomposing requirements solves the problem of vague project scopes by forcing verifiable steps. This skill mandates a test-driven development cycle for every 2-5 minute task, ensuring code reliability and preventing overwhelming project backlogs.