skills.rest
joshua3403
joshua3403COMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Convert specs or requirements into task-by-task implementation plans with file paths and commands.

Updated Feb 2, 2026
Search Tags:#planning#documentation#TDD#workflows#software-engineering#spec-to-plan
One-click install
npx skills add https://github.com/joshua3403/giit-template --skill writing-plans-joshua3403
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/joshua3403/giit-template/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/joshua3403/giit-template --skill writing-plans-joshua3403

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts a spec or requirements into a comprehensive, task-by-task implementation plan for engineers who may have zero context about the codebase.

Core Features & Use Cases

  • Generate bite-sized tasks with exact file paths to touch, test scaffolds, and required commands.
  • Document testing, documentation, and commit steps to ensure traceable delivery.
  • Save the plan to docs/plans/YYYY-MM-DD-<feature-name>.md and support versioned naming; ideal for complex features or refactors.

Quick Start

Provide a clear spec for the feature. Run the writing-plans skill in a dedicated worktree. The plan is generated and saved to docs/plans/YYYY-MM-DD-<feature-name>.md with executable steps and file references.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert software requirements into an actionable implementation plan?▼

To convert software requirements into an implementation plan, provide a clear spec to generate bite-sized tasks with exact file paths, test scaffolds, and required commands. This enforces DRY, YAGNI, and TDD principles while producing traceable executable steps.

What is the best way to plan a complex feature refactor for engineers with no codebase context?▼

Planning a complex feature refactor involves outlining required files, tests, commands, and documentation into a comprehensive task-by-task plan. This ensures traceable delivery for engineers who have zero context about the codebase by providing precise execution steps.

How does test-driven development integrate with spec-to-plan workflows?▼

Test-driven development integrates into spec-to-plan workflows by enforcing TDD principles during plan generation. The process outlines required test scaffolds and documentation steps alongside exact file paths to ensure executable and traceable feature delivery.

Do I need to run this in a dedicated worktree to generate feature documentation?▼

You need to run this in a dedicated worktree to generate feature documentation effectively. The plan is then saved to docs/plans/YYYY-MM-DD-<feature-name>.md, supporting versioned naming ideal for complex features and refactors.

Can I use this for both new feature development and complex refactors?▼

You can use this for both new feature development and complex refactors. It applies to both by converting specs into comprehensive task-by-task implementation plans with executable steps, required files, and precise commands for traceable delivery.

Related Skills

Explore More Software Engineering Skills→
evanfang0054evanfang0054

brainstorming

Transform user ideas into detailed project designs with scope and architecture.

Community
Intermediate
josorio7122josorio7122
1

plan

Generate sequentially ordered implementation plans for software development tasks.

Community
Intermediate
EntroVyxEntroVyx
3

plan

Generate structured markdown implementation plans with TDD-based steps.

Community
Intermediate
zai-orgzai-org
588

writing-plans

Create Markdown implementation plans with files, tests, docs, and milestones from specs.

Official
Advanced