writing-plans

Convert project specs into executable implementation plans with tasks and tests.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gqf2008/hermez-ai --skill writing-plans-gqf2008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/gqf2008/hermez-ai/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/gqf2008/hermez-ai --skill writing-plans-gqf2008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps teams transform vague specs into comprehensive, executable plans that outline concrete tasks, required files, testing steps, and example code to ensure clear handoffs.

Core Features & Use Cases

  • Create bite-sized, 2-5 minute tasks with explicit file paths and test expectations.
  • Enforce TDD-driven workflows and frequent commits to improve consistency and traceability.
  • Guide multi-step feature development and subagent handoffs with structured plan headers and task formats.

Quick Start

Provide your project spec and I will generate a structured, bite-sized implementation plan you can execute task-by-task.

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 project spec into an executable implementation plan?

You can break down complex multi-step features by generating a structured plan with bite-sized tasks, explicit file paths, test expectations, and example code to guide developers or subagents through development.

Can I enforce a TDD-driven workflow through my implementation plan?

Yes, you can enforce a TDD-driven workflow and frequent commits within your implementation plan to improve consistency and traceability across multi-step feature development and subagent handoffs.

Does this work for subagent handoffs in multi-step feature development?

This works for subagent handoffs by generating structured plan headers and task formats that guide multi-step feature development with bite-sized tasks, explicit file paths, and clear acceptance criteria.

What is the best way to structure bite-sized tasks for software development?

The best way to structure bite-sized tasks for software development is to create 2-5 minute tasks with explicit file paths, test expectations, and example code to ensure clear handoffs and traceability.