skills.rest
aleksandrov
aleksandrovCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Document structured implementation plans with tasks, files, tests, and commit history.

2|Updated Jan 11, 2026
Search Tags:#planning#requirements#implementation#software-engineering#tests#task-planning
One-click install
npx skills add https://github.com/aleksandrov/instructions --skill writing-plans-aleksandrov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/aleksandrov/instructions/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/aleksandrov/instructions --skill writing-plans-aleksandrov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write comprehensive plans for multi-step development tasks before touching code, ensuring clear guidance for files touched, code snippets, tests, and expected outcomes.

Core Features & Use Cases

  • Provides a structured template to document tasks, required files, and test commands.
  • Guides engineers to produce repeatable, testable implementation plans before implementation.
  • Enables project-wide traceability by standardizing planning artifacts.

Quick Start

Create a detailed implementation plan that lists the touched files, changes, tests, and expected results.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create a structured implementation plan before coding a multi-step feature?▼

A task implementation plan standardizes feature development by defining goals, architecture, tech stack, feature-branch name, and explicit task steps including file changes and test commands before coding begins.

What should be included in software engineering task planning for multi-step development?▼

Multi-step task planning requires a defined template with sections for goals, architecture, tech stack, a dedicated feature-branch name, and explicit task steps including file changes and test commands.

How do I document expected outcomes and tests for a feature before implementation?▼

Document expected outcomes and tests by listing touched files, code snippets, required test commands, and expected results within a structured implementation plan template before writing code.

Can I use a predefined template to plan requirements and file changes for my development workflow?▼

Yes, a predefined plan template documents requirements, identifies touched files, and specifies test commands, ensuring repeatable and testable implementation plans for feature development workflows.

Why do I need to define a feature-branch name and architecture before writing code?▼

Defining a feature-branch name and architecture before coding ensures project-wide traceability and provides clear guidance for files touched, code snippets, tests, and expected outcomes.

Related Skills

Explore More Software Engineering Skills→
dralgorhythmdralgorhythm
111

designing-systems

Design scalable software systems with C4 diagrams and trade-off analysis.

Community
Advanced
saranskumarsaranskumar

gsd-execute

Create a finalized SPEC file and execute the PLAN, EXECUTE, VERIFY, COMMIT workflow.

Community
Advanced
softmgsoftmg

Pair Programming

Coordinate role-based pair programming sessions with automated testing and verification.

Official
Advanced
BrennonTWilliamsBrennonTWilliams
7

ll-refine-issue

Refine software issue documentation via codebase research and gap analysis.

Community
Intermediate