skills.rest
beyondwen
beyondwenCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with tasks, files, tests, and documentation from specifications.

Updated Mar 30, 2026
Search Tags:#workflow#planning#documentation#specifications#software-engineering#task-breakdown
One-click install
npx skills add https://github.com/beyondwen/track-record-new --skill writing-plans-beyondwen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/beyondwen/track-record-new/tree/main/.gemini/skills/writing-plans
Command: npx skills add https://github.com/beyondwen/track-record-new --skill writing-plans-beyondwen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to convert vague specifications into a concrete, step-by-step implementation plan that guides engineering work before writing code.

Core Features & Use Cases

  • Structured planning: Break down complex features into clear tasks, files, tests, and milestones.
  • Spec-to-plan conversion: Translate a product requirement or technical spec into actionable plan documents and checkpoints.
  • Collaborative review: Provide plan templates and reviewer prompts to enable quick validation and alignment.

Quick Start

Create a new plan in the dedicated workspace and outline the feature’s file changes, testing steps, and commit milestones.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert software specifications into an actionable implementation plan?▼

Implementation planning breaks down complex, multi-subsystem features into structured milestones, specific file changes, and testing steps to ensure technical alignment before coding begins.

How do I break down complex features into tasks for multiple development teams?▼

Task breakdown translates multi-subsystem feature specs into discrete file changes, testing checkpoints, and commit milestones, enabling distributed teams to execute complex software engineering work.

What is the best way to structure a technical plan before writing code?▼

A structured plan template specifies required file changes, testing procedures, commit milestones, and formal reviewer prompts, enabling quick validation and alignment before coding begins.

Does implementation planning work for features spanning multiple subsystems?▼

Yes, implementation planning specifically applies to complex features spanning multiple subsystems and teams, converting vague product requirements into concrete, step-by-step documentation and actionable checkpoints.

Can I include reviewer prompts and commit milestones in my task planning workspace?▼

Yes, a dedicated planning workspace fulfills plan template requirements by incorporating sections for file changes, testing steps, commit milestones, and formal reviewer prompts to ensure quick validation.

When do I need to generate a step-by-step plan from a product requirement?▼

You need to generate a step-by-step plan from a product requirement when facing vague specifications for multi-step software tasks, ensuring engineering work is guided by concrete tasks and documentation before writing code.

Related Skills

Explore More Software Engineering Skills→
dralgorhythmdralgorhythm
111

designing-systems

Design scalable software systems with C4 diagrams and trade-off analysis.

Community
Advanced
FourthWizFourthWiz
2

implement

Convert development plans into tested code with commits and PRs.

Community
Advanced
QunnnnQunnnn

writing-plans

Create structured implementation plans with file-level task breakdowns before coding.

Community
Advanced
royhenengelroyhenengel

plan

Generate spec-driven implementation plans for software development tasks.

Community
Intermediate