writing-plans

Convert high-level specs into testable implementation roadmaps with tasks and commit notes.

4|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/mykaarma/kaarma-skills --skill writing-plans-mykaarma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/mykaarma/kaarma-skills/tree/main/skills/writing-plans
Command: npx skills add https://github.com/mykaarma/kaarma-skills --skill writing-plans-mykaarma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers often start with vague specs and struggle to translate them into a concrete, testable plan for implementation.

Core Features & Use Cases

  • Generates structured, bite-sized tasks with clear deliverables and commit notes.
  • Defines where to save plans, how to integrate with worktrees, and how to track progress.
  • Useful for feature development, refactors, and complex-ticket breakdowns across teams.

Quick Start

Provide a feature name and spec; the skill will emit a task-by-task implementation plan.

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

To turn a feature spec into an implementation plan, you provide the feature name and spec details to generate a structured, task-by-task roadmap with clear deliverables and commit notes.

What is the best way to break down complex software development tickets into testable tasks?

Breaking down complex software development tickets involves converting high-level requirements into bite-sized tasks that map out file layouts, test cases, and documentation in a reproducible workflow.

Can I integrate generated implementation plans with git worktrees?

Yes, generated implementation plans define where to save files and how to integrate with git worktrees to track progress, ensuring an isolated and reproducible development environment.

Does this task breakdown approach work for large-scale redesigns across multiple teams?

Yes, this task breakdown approach applies to large-scale redesigns across multiple teams by capturing requirements mapping, file layouts, and commit notes in a DRY workflow.

Why should I use a structured plan for refactoring and bug fixes?

Using a structured plan for refactoring and bug fixes prevents vague specifications from causing implementation struggles, translating high-level changes into concrete, testable roadmaps.