skills.rest
elophanto
elophantoCOMMUNITY
Explore all skills by this author →
Website𝕏@elophantoGitHub

writing-plans

Create step-by-step implementation plans from high-level specifications.

116|9|Updated Feb 18, 2026
Search Tags:#planning#documentation#project-management#quality-control#task-decomposition#engineering-plans
One-click install
npx skills add https://github.com/elophanto/EloPhanto --skill writing-plans-elophanto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/elophanto/EloPhanto/tree/main/skills/writing-plans
Command: npx skills add https://github.com/elophanto/EloPhanto --skill writing-plans-elophanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate a high-level specification into a detailed, action-oriented implementation plan, reducing ambiguity and rework.

Core Features & Use Cases

  • Structured task breakdown: maps a spec to concrete tasks, files to touch, tests to write, and docs to update.
  • Guardrails and quality checks: enforces no placeholders, requires a formal plan header, and includes self-review steps.
  • Real-world use: used at project kickoffs to align engineers, designers, and product managers on scope and milestones.

Quick Start

Create a new implementation plan in docs/plans following the required header and Task Structure, then save it as a markdown file.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a high-level specification into an executable implementation plan?▼

Implementation plans require a formal header, task decomposition, concrete file changes, tests, and checkpoints. Guardrails enforce no placeholders and include self-review steps to ensure the plan is comprehensive, action-oriented, and ready for engineering execution.

What is the best way to structure task decomposition for cross-functional software projects?▼

Implementation plans require a formal header, task decomposition, concrete file changes, tests, and checkpoints to ensure comprehensive coverage and reduce ambiguity across cross-functional software projects.

Can I use a structured plan format for project kickoffs to align engineers and product managers?▼

Implementation plans require a formal header, task decomposition, concrete file changes, tests, and checkpoints to ensure comprehensive coverage and reduce ambiguity across cross-functional software projects.

Do I need to specify concrete file changes and tests when creating engineering plans?▼

Implementation plans require a formal header, task decomposition, concrete file changes, tests, and checkpoints to ensure comprehensive coverage and reduce ambiguity across cross-functional software projects.

How to start writing implementation plans in markdown for software engineering tasks?▼

Implementation plans require a formal header, task decomposition, concrete file changes, tests, and checkpoints to ensure comprehensive coverage and reduce ambiguity across cross-functional software projects.

Related Skills

Explore More Software Engineering Skills→
igoorstraviinsky-devigoorstraviinsky-dev

speckit-tasks

Convert plan.md and spec.md into dependency-aware task lists.

Community
Intermediate
fred29910fred29910

writing-plans

Generate structured implementation plans outlining files, tests, and milestones.

Community
Advanced
maroffomaroffo
16

bujo-sync

Synchronize tasks bidirectionally between Bullet Journal notes and ClickUp or Linear.

Community
Advanced
ccstudentccccstudentcc

writing-plans

Generate executable implementation plans with task decomposition, file mapping, and test plans.

Community
Advanced