writing-plans

Generate step-by-step implementation plans for software development tasks.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/MrAlexisCord/chatbot-prototype --skill writing-plans-mralexiscord
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/MrAlexisCord/chatbot-prototype/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/MrAlexisCord/chatbot-prototype --skill writing-plans-mralexiscord

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, step-by-step implementation plans for software development tasks, ensuring clarity and reducing ambiguity for engineers.

Core Features & Use Cases

  • Decomposition: Breaks down complex features into bite-sized, actionable tasks.
  • Contextualization: Provides engineers with all necessary information, including file modifications, code snippets, testing instructions, and documentation references.
  • Standardization: Enforces best practices like TDD, DRY, and YAGNI through a structured planning process.
  • Use Case: When given a new feature specification, this Skill generates a comprehensive plan that an engineer can follow with minimal prior knowledge of the codebase.

Quick Start

Use the writing-plans skill to create an implementation plan for the new user authentication feature.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate detailed implementation plans for multi-step software development tasks?

Implementation plans decompose complex features into bite-sized, actionable tasks detailing file modifications, code implementation, testing procedures, and documentation requirements, ensuring engineers can follow specifications with minimal prior codebase knowledge.

How do I break down complex software features into actionable engineering tasks?

Break down complex software features by applying task decomposition to generate contextualized steps, providing engineers with necessary code snippets, file modifications, and testing instructions while enforcing best practices like TDD, DRY, and YAGNI principles.

Does automated implementation planning support test-driven development practices?

Automated implementation planning supports test-driven development by enforcing TDD, DRY, and YAGNI principles through a structured planning process, ensuring testing procedures and documentation requirements are detailed for every generated task step.

Can I use generated implementation plans for direct execution or subagent handoffs?

Generated implementation plans support both direct execution and subagent handoffs, allowing engineers to review the structured steps and then execute the specified file modifications and code implementations directly or delegate them to subagents.

What is the best way to standardize software implementation documentation for new features?

Standardize software implementation documentation by using a structured planning process that generates comprehensive plans with detailed file modifications, code snippets, testing instructions, and documentation references for new feature specifications.

When should I avoid using automated task decomposition for software development?

Avoid using automated task decomposition for simple, single-step modifications or when lacking clear feature specifications, as the structured planning process targets multi-step tasks requiring detailed file modifications and testing procedures.