skills.rest
danieldekay
danieldekayCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with file paths, test strategies, and commit messages.

1|2|Updated Jan 7, 2026
Search Tags:#planning#documentation#implementation#workflows#task-management#software-engineering
One-click install
npx skills add https://github.com/danieldekay/copilot-config-promptops --skill writing-plans-danieldekay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/danieldekay/copilot-config-promptops/tree/main/skills/writing-plans
Command: npx skills add https://github.com/danieldekay/copilot-config-promptops --skill writing-plans-danieldekay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of detailed implementation plans from a spec, turning vague requirements into a concrete, executable plan.

Core Features & Use Cases

  • Generate structured task breakdowns with files, tests, and commits.
  • Produce a repeatable planning process for software features, infrastructure changes, and research tasks.
  • Provide a standardized plan template that teams can adapt and reuse.

Quick Start

Provide a full implementation plan for a feature from its spec, outlining tasks, files, tests, and commit steps.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate a detailed implementation plan from a software feature spec?▼

To generate an implementation plan from a spec, you provide the feature requirements and the skill outputs a concrete plan document with precise file paths, test strategies, and commit messages using a standardized template.

Can I use this for infrastructure changes and research tasks, or only software features?▼

Yes, you can use this planning process for infrastructure changes and research tasks. It is applicable to any scenario where step-by-step execution and structured task breakdowns are needed.

What is included in a standardized task breakdown for software engineering?▼

A standardized task breakdown includes structured steps outlining the specific files to modify, the test strategies to apply, and the commit messages to use for each phase of the implementation.

What's the best way to turn vague software requirements into an executable plan?▼

The best way to turn vague requirements into an executable plan is to automate the creation of a detailed, step-by-step plan document that specifies exact file paths, test strategies, and commit steps.

Are there limitations to automating implementation plan generation for complex tasks?▼

Automating implementation plans requires a clear input spec to function correctly; limitations arise when initial requirements are too ambiguous to generate precise file paths and test strategies.

Does the generated plan document provide specific commit messages for task management?▼

Yes, the generated plan document provides specific commit messages as part of its standardized template, ensuring the execution workflow is fully mapped out for task management.

Related Skills

Explore More Software Engineering Skills→
aperepelaperepel
7

interview

Conduct adaptive interviews to generate structured Markdown specifications.

Community
Advanced
JKKN-InstitutionsJKKN-Institutions

writing-plans

Generate bite-sized implementation plans with file paths, code, and tests.

Official
Basic
anderson-0anderson-0
4

status

Inspect implementation plan progress from status.yaml files without altering execution state.

Community
Basic
DergaczDergacz

10x-init

Create a standardized project context directory with change tracking and documentation folders.

Community
Basic