writing-plans

Generate structured implementation plans with tasks, files, tests, and verification steps.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/yairbederman/EngineeringAgency --skill writing-plans-yairbederman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/yairbederman/EngineeringAgency/tree/main/skills/writing-plans
Command: npx skills add https://github.com/yairbederman/EngineeringAgency --skill writing-plans-yairbederman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate a project spec or requirements into a clear, actionable implementation plan that guides engineers through tasks, tests, and milestones.

Core Features & Use Cases

  • Generate a structured Task N: [Component Name] plan with explicit file touchpoints, test cases, and verification steps.
  • Outline a minimal viable implementation and a roadmap for future enhancements.
  • Provide a reproducible plan that can be reviewed, discussed, and handed off to a team.

Quick Start

Plan a new feature by providing a project spec, and I will return a complete implementation plan ready for execution.

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 from a project spec?

An implementation plan translates project specs into a clear, actionable strategy guiding engineers through tasks, tests, and milestones, ensuring all touchpoints are covered from testing to deployment.

What is included in a structured software implementation plan?

A structured implementation plan defines a task structure with explicit file touchpoints, test cases, verification steps, and a roadmap for future enhancements to ensure comprehensive project coverage.

How do I structure development tasks for a new software feature?

To structure development tasks, the plan organizes specs into a 'Task N: [Component Name]' format, explicitly detailing file touchpoints, test cases, and verification steps for each milestone.

Can I use this to generate a reproducible plan for team handoff?

Yes, this process provides a reproducible, ready-to-implement plan that can be reviewed, discussed, and handed off to a team for execution directly from the provided project spec.

What's the best way to document end-to-end implementation strategies?

The best way to document end-to-end implementation strategies is by translating project specs into a structured plan outlining step-by-step tasks, tests, and milestones from initial setup to deployment.