writing-plans

Creates detailed implementation plans with step-by-step tasks in Markdown for engineers.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/act70255/SkillsBundle --skill writing-plans-act70255
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/act70255/SkillsBundle/tree/main/planning/skills/writing-plans
Command: npx skills add https://github.com/act70255/SkillsBundle --skill writing-plans-act70255

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps organize and execute multi-step tasks by providing comprehensive implementation plans, assuming the engineer has zero context for the codebase and questionable taste.

Core Features & Use Cases

  • Comprehensive Planning: Document all necessary information for each task, including file paths, code, testing, and documentation.
  • Bite-Sized Tasks: Break down each task into small, actionable steps for easy execution.
  • Task Structure: Follow a consistent structure for each task, including writing failing tests, implementing minimal code, and running tests.
  • Execution Handoff: Provide execution options for subagent-driven or parallel sessions.

Quick Start

Use the writing-plans skill to create an implementation plan for the 'feature-X' task.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan for complex coding tasks?

To create an implementation plan for complex coding tasks, you break down work into bite-sized, actionable steps using Markdown to document file paths, code, and testing procedures for minimal-context execution.

What is the best way to document code tasks for developers with no context?

The best way to document code tasks for developers with no context is providing comprehensive implementation plans that include necessary file paths, coding practices, testing procedures, and step-by-step execution instructions.

How do I structure step-by-step execution plans for software engineering tasks?

You structure step-by-step execution plans for software engineering tasks by following a consistent task structure: writing failing tests, implementing minimal code, running tests, and documenting all necessary information in Markdown.

Do I need to know file paths and testing procedures to use implementation planning?

Yes, implementation planning requires knowledge of file paths, coding practices, and testing procedures to ensure all necessary information is included for engineers executing the documented tasks with minimal context.

Can implementation plans be handed off to parallel development sessions?

Yes, implementation plans can be handed off to parallel development sessions by providing execution options specifically designed for subagent-driven or parallel session workflows.