writing-plans

Translate project specifications into executable implementation plans with tasks, tests, and file paths.

1|Updated Apr 30, 2025
One-click install
npx skills add https://github.com/lucasfth/config --skill writing-plans-lucasfth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/lucasfth/config/tree/main/.hermes/skills/software-development/writing-plans
Command: npx skills add https://github.com/lucasfth/config --skill writing-plans-lucasfth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This service provides a structured approach to translating a project spec or requirements into a complete, executable implementation plan, ensuring nothing is overlooked and enabling fast handoffs.

Core Features & Use Cases

  • Generates step-by-step tasks with exact file paths, required tests, and concrete code examples.
  • Enforces a consistent plan structure (headers, task sections, and commit guidelines) to streamline collaboration with subagents and maintainers.
  • Useful for breaking down multi-step features, onboarding new contributors, and documenting complex workflows.

Quick Start

Provide a complete, task-by-task implementation plan for a multi-step feature with exact file paths, tests, and example commands.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn project specifications into an executable implementation plan?

Turning project specifications into an executable implementation plan requires translating requirements into bite-sized tasks with exact file paths, required tests, and concrete code examples. This ensures structured task breakdown for fast handoffs.

What is the best way to break down a multi-step feature for developer onboarding?

Breaking down a multi-step feature for developer onboarding involves generating step-by-step tasks with exact file paths and commit guidelines. This creates a consistent plan structure that streamlines collaboration across diverse codebases.

How do I create an implementation plan that includes TDD task breakdown?

Creating an implementation plan with TDD task breakdown involves structuring bite-sized tasks that specify required tests alongside concrete code examples. This enforces a consistent plan format with headers and task sections for maintainers.

Can I use structured implementation plans for design handoffs across different codebases?

Structured implementation plans can be used for design handoffs across diverse codebases by providing a consistent format with header guidance and exact file paths. This approach ensures nothing is overlooked during multi-step feature development.

Does generating task-by-task documentation help with subagent collaboration?

Generating task-by-task documentation helps with subagent collaboration by enforcing a consistent plan structure with headers and commit guidelines. This structured format streamlines handoffs and maintains workflow continuity across contributors.