skills.rest
leonardoteodoroo
leonardoteodorooCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with tasks, files, tests, and commits.

Updated Feb 3, 2026
Search Tags:#planning#documentation#worktree#plans#best-practices#software-development#task-management
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill writing-plans-leonardoteodoroo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill writing-plans-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams structure and document comprehensive implementation plans for multi-step tasks before touching code. It guides engineers to outline required files, testing strategies, documentation, and commit history to ensure alignment and repeatable execution.

Core Features & Use Cases

  • End-to-end task planning: generate step-by-step instructions covering files, tests, docs, and commits.
  • Contextual planning in a dedicated worktree: keeps codebase changes isolated during brainstorming.
  • Plan storage and traceability: saves plans to docs/plans/YYYY-MM-DD-<feature-name>.md for easy retrieval and audits.
  • Execution handoff guidance: suggests required sub-skills to drive plan execution (e.g., subagent-driven-development or executing-plans).

Quick Start

Create a new implementation plan for a feature by outlining all tasks, files, tests, and commits in a single document.

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 multi-step software development tasks?▼

To generate an implementation plan for multi-step software development tasks, you outline required files, testing strategies, documentation, and commits to ensure alignment and repeatable execution before coding begins.

What should be included in software feature planning documentation?▼

Software feature planning documentation should include a header, task sections, file paths, testing strategies, commit history, and a handoff guide to ensure comprehensive task decomposition and traceability.

How do I store implementation plans for traceability and easy retrieval?▼

Store implementation plans for traceability by saving the markdown documents under docs/plans/YYYY-MM-DD-<feature-name>.md, ensuring easy retrieval and audits for your software development project.

Does task planning work in an isolated codebase worktree for brainstorming?▼

Yes, task planning works in a dedicated worktree to keep codebase changes isolated during brainstorming, ensuring that outlining required files and testing strategies does not impact the main branch.

What's the best way to transition from task planning to code execution?▼

The best way to transition from task planning to code execution is by following the execution handoff guidance within the plan, which suggests required sub-skills like subagent-driven-development or executing-plans.

Related Skills

Explore More Software Engineering Skills→
zhuyingcoderzhuyingcoder

writing-plans

Convert vague specs into structured implementation plans with versioned artifacts.

Community
Intermediate
beratcelik1beratcelik1
1

work

Execute development plans into tasks, code changes, tests, and commits.

Community
Intermediate
LayerDynamicsLayerDynamics

planning-ext-list

List saved implementation plans from docs/plans/ sorted by date descending.

Community
Basic
yamk12nfuyamk12nfu

implement-from-spec

Convert requirements documents into executable implementations with subagent orchestration.

Community
Advanced