writing-plans

Translate a spec into a task-level implementation plan with files, tests, and commits.

7|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/fratilanico/apex-os-bad-boy --skill writing-plans-fratilanico
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/fratilanico/apex-os-bad-boy/tree/main/writing-plans
Command: npx skills add https://github.com/fratilanico/apex-os-bad-boy --skill writing-plans-fratilanico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate a spec into a concrete implementation plan that outlines tasks, milestones, and required artifacts before touching code.

Core Features & Use Cases

  • Generates a structured implementation plan from a feature or problem statement, including task breakdown, required files, tests, and commit steps.
  • Guides teams through an end-to-end workflow from planning to execution, with a reusable plan document format and versioned saves.
  • Use Case: A product manager provides a spec and a software engineer uses the plan to execute the tasks with clear checkpoints.

Quick Start

Provide a feature name or spec to generate an executable plan that can be saved to docs/plans.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I translate a feature spec into a task-level implementation plan?

To translate a spec into an implementation plan, provide the feature requirements to generate a structured document. The output includes a header, Task N sections with required files, tests, and commit steps, saved to docs/plans/YYYY-MM-DD-<feature-name>.md.

What is the best way to break down software development tasks from a spec before coding?

Breaking down development tasks from a spec involves generating a plan document with task-level sections. This process outlines milestones, required files, tests, and commit checkpoints, ensuring clear execution steps before touching code.

How do I generate a development plan with commit steps and test requirements?

Generating a development plan with commit steps requires inputting a feature name or problem statement. The plan document structures each task with required files, specific tests, and commit instructions, providing end-to-end workflow guidance.

Can I use this engineering workflow for multi-step task management with existing requirements?

Yes, this engineering workflow applies to software projects where requirements already exist. It takes existing specs and creates a concrete, multi-step task breakdown with versioned saves for team execution.

Does the generated plan document save automatically to a specific file path?

The generated plan document saves to a specific versioned path at docs/plans/YYYY-MM-DD-<feature-name>.md. This ensures all implementation plans are consistently archived and accessible for future reference.

When do I need a task-level breakdown with files and tests for my project?

A task-level breakdown with files and tests is needed when translating a product spec into executable engineering work. It provides clear checkpoints and required artifacts, guiding teams from planning to code execution.