skills.rest
Rawgrowth-Consulting
Rawgrowth-ConsultingOFFICIAL
Explore all skills by this author →
GitHub

writing-plans

Generate task-by-task implementation plans from feature specifications.

Updated Apr 23, 2026
Search Tags:#workflow#planning#tdd#documentation#software-engineering#task-breakdown#implementation-plan
One-click install
npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill writing-plans-rawgrowth-consulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Rawgrowth-Consulting/rawclaw-agent/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill writing-plans-rawgrowth-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague feature ideas or requirements into actionable, ready-to-implement plans that specify exact file paths, complete code examples, tests, and documentation steps, ensuring consistency and traceability across development tasks.

Core Features & Use Cases

  • End-to-end planning: Produces a full implementation plan from a spec, including file changes, tests, and verification steps.
  • ** Bite-sized tasks**: Breaks work into 2–5 minute tasks to encourage incremental progress and frequent commits.
  • TDD-first guidance: Emphasizes test-driven development, documentation, and dry/ YAGNI principles to keep scope focused.
  • Plan structure templates: Provides a consistent header, task sections, and verification steps that are copy-paste-ready.
  • Execution handoff: Ready to hand off to subagents per task for spec compliance and code quality reviews.

Quick Start

Propose an end-to-end implementation plan for a new feature, starting from a clean repo and following the plan structure.

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 feature specification into an implementation plan?▼

Bite-sized tasks are broken down into 2–5 minute increments. This task breakdown encourages incremental progress and frequent commits, making complex software engineering tasks easier to manage and track.

Does test-driven development planning work with cross-team handoffs?▼

An effective implementation plan includes explicit file paths, complete code examples, testing steps, and documentation checks. It provides a consistent header, structured task sections, and verification steps that are copy-paste-ready for developers.

When do I need task breakdown for software engineering workflows?▼

You need task breakdown for multi-step software features, complex integration tasks, and cross-team handoffs. Applying task breakdown converts vague feature ideas into actionable, ready-to-implement plans ensuring consistency and traceability.

What's the best way to structure implementation plans for subagent execution?▼

The best way to structure implementation plans for subagent execution is to generate copy-paste-ready sections with verification steps. This structure creates a seamless execution handoff for subagents to review spec compliance and code quality per task.

Related Skills

Explore More Software Engineering Skills→
timsvoicetimsvoice

specimin-spec

Convert natural language feature requests into structured draft specifications.

Community
Advanced
HarriesHarries

writing-plans

Convert complex software tasks into structured implementation plans with file paths and acceptance criteria.

Community
Advanced
dohernandezdohernandez

task

Define and enforce a scoped workflow for non-bugfix software tasks.

Community
Advanced
Prathmesh2000Prathmesh2000
1

task-planner

Break down high-level requirements into structured task lists with dependencies.

Community
Advanced