writing-plans

Generate implementation plans with tasks and TDD steps as Markdown.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/aimskr/aims-claude-toolkit --skill writing-plans-aimskr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/aimskr/aims-claude-toolkit/tree/main/skills/writing-plans
Command: npx skills add https://github.com/aimskr/aims-claude-toolkit --skill writing-plans-aimskr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers generate detailed, bite-sized implementation plans with clear tasks, required steps, and testing guidance, reducing ambiguity before coding.

Core Features & Use Cases

  • Plan generation: Produce structured, task-by-task plans including files touched, tests, and docs.
  • TDD alignment: Create steps following Test-Driven Development practices to guide incremental implementation.
  • Plan capture: Save Plan mode output as structured Markdown in a designated docs/plans path for documentation and traceability.

Quick Start

Start by outlining the feature and generate a detailed plan, then save it with Plan mode to docs/plans.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate a detailed implementation plan for a new software feature?

To generate an implementation plan, outline your feature and the tool will produce a structured, task-by-task breakdown including files touched, tests, and required documentation steps.

What is the best way to plan Test-Driven Development steps before coding?

Planning TDD steps involves creating an incremental task list that defines required tests and expected outcomes before writing code, which this tool integrates directly into your feature plans.

How does saving implementation plans as Markdown in a docs folder help traceability?

Saving plans as Markdown under a consistent docs/plans path captures the structured output directly in your repository, providing version-controlled documentation and traceability for feature workflows.

Can I use this workflow for planning refactors and new modules, or is it only for new features?

Yes, you can use this planning workflow for multi-step features, code refactors, and new modules. It generates bite-sized tasks and TDD steps to reduce ambiguity before coding begins.

What should be included in a task management plan for software engineering workflows?

A comprehensive task management plan should include bite-sized tasks, specify files to be touched, outline required tests, and define necessary documentation to guide structured implementation.