writing-plans

Generate implementation plans from high-level specifications with files, tests, and commits.

20|4|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/Alenryuichi/openmemory-plus --skill writing-plans-alenryuichi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Alenryuichi/openmemory-plus/tree/main/.augment/skills/writing-plans
Command: npx skills add https://github.com/Alenryuichi/openmemory-plus --skill writing-plans-alenryuichi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers transform high-level specs into comprehensive, task-by-task implementation plans that clearly indicate what to touch, how to test, and how to commit.

Core Features & Use Cases

  • Generate end-to-end implementation plans from a clear spec, including files to touch, tests to write, docs to update, and commit messages.
  • Align planning with DRY, YAGNI, and TDD principles to keep plans concise and reliable.
  • Use cases include starting new features, major refactors, or architectural changes across codebases.

Quick Start

Provide a complete, task-by-task implementation plan for a requested feature given a detailed spec.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan from a feature spec?

This skill transforms high-level specifications into comprehensive, task-by-task implementation plans for software engineers. It outlines what files to touch, how to test, and how to commit, aligning your workflow with DRY, YAGNI, and TDD best practices.

How do I plan a major codebase refactor step by step?

Planning a major codebase refactor involves converting architectural change specs into an actionable, task-by-task sequence. The output specifies concrete requirements including touched files, tests, documentation, and commit messages for reliable execution.

Does implementation planning work for new features and architectural changes?

Implementation planning works for starting new features, major refactors, and architectural changes across codebases. It transforms high-level specs into clear task management sequences indicating exactly what to touch and how to test.

What is the best way to include TDD principles in a development plan?

The best way to include TDD principles is to use a spec-driven planning approach that advocates DRY, YAGNI, and TDD best practices. This ensures the generated task list concisely outlines required tests alongside file modifications.

What do I need to provide to get a task-by-task implementation plan?

To get a task-by-task implementation plan, you need to provide a detailed, high-level specification of your requested feature. The skill uses this spec to generate end-to-end plans including files to touch, tests, and commit messages.