skills.rest
Adrian-opo
Adrian-opoCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with file paths, code samples, tests, and verification steps.

Updated Feb 25, 2026
Search Tags:#planning#tdd#codebase#implementation#engineering#tasks#docs
One-click install
npx skills add https://github.com/Adrian-opo/multitool-app --skill writing-plans-adrian-opo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Adrian-opo/multitool-app/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/Adrian-opo/multitool-app --skill writing-plans-adrian-opo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates comprehensive, implementation-ready plans for engineers who have zero context about a codebase.

Core Features & Use Cases

  • Create step-by-step tasks with exact file paths, code samples, tests, docs, and verification steps.
  • Use cases include onboarding a new feature, performing refactors, or migrating to new architectures with minimal domain knowledge.
  • Supports DRY, YAGNI, and TDD principles to keep plans concise and actionable.

Quick Start

Ask the writing-plans skill to generate a complete implementation plan by specifying the feature name and scope, and it will save the plan to docs/plans/YYYY-MM-DD-<feature-name>.md

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 for an unfamiliar codebase?▼

Implementation plans for unfamiliar codebases provide exact file paths, code samples, tests, and verification steps. They are designed for engineers with zero context, ensuring clear tasks and acceptance criteria suitable for a TDD workflow.

What is the best way to structure implementation tasks for a TDD workflow?▼

The best way to structure implementation tasks for a TDD workflow is using exhaustive plans with clear prerequisites and acceptance criteria. This approach applies DRY and YAGNI principles to keep tasks concise and actionable for test-driven development.

Can I use this for refactoring or migrating to new architectures with minimal domain knowledge?▼

Yes, you can use this for refactoring or migrating architectures with minimal domain knowledge. It supports use cases like onboarding new features and performing refactors by outlining exact files, tests, and docs for unfamiliar projects.

How do I save and document generated engineering plans?▼

To save and document generated engineering plans, specify the feature name and scope. The system automatically saves the complete implementation plan to the docs/plans directory using a YYYY-MM-DD-<feature-name>.md file format.

Does this planning approach work for design-to-deploy tasks across unfamiliar projects?▼

Yes, this planning approach works for design-to-deploy tasks across unfamiliar projects. It generates comprehensive plans outlining exact files, code samples, tests, and docs, ensuring each plan satisfies an exhaustive structure for engineers with zero context.

Related Skills

Explore More Software Engineering Skills→
Happyverse-TeamHappyverse-Team

pdd

Convert rough ideas into design documents, implementation plans, and prioritized todo lists.

Official
Basic
weipingweiping
34

writing-plans

Generate step-by-step implementation plans with file, code, and test instructions.

Community
Intermediate
tech-leads-clubtech-leads-club
5.0k

nx-generate

Generate libraries and applications using Nx generators in a monorepo.

Official
Intermediate
lagz0nelagz0ne
2

writing-plans

Generate end-to-end implementation plans from product specs with frontmatter metadata.

Community
Basic