skills.rest
ClyptAI
ClyptAIOFFICIAL
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with task breakdowns, file changes, tests, and commits.

Updated Mar 8, 2026
Search Tags:#planning#testing#documentation#implementation#version-control#task-decomposition
One-click install
npx skills add https://github.com/ClyptAI/Clypt-Backend --skill writing-plans-clyptai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ClyptAI/Clypt-Backend/tree/main/.agents/skills/superpowers/skills/writing-plans
Command: npx skills add https://github.com/ClyptAI/Clypt-Backend --skill writing-plans-clyptai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams generate comprehensive implementation plans from a formal spec or requirements before coding, reducing ambiguity and ensuring traceability.

Core Features & Use Cases

  • Structured plan generation: maps specs to a file structure with tasks, touched files, tests, and commits.
  • Plan scope and decomposition: splits work into manageable tasks across subsystems or features.
  • Plan storage and version control: saves plans to docs/superpowers/plans with date and feature name for easy discovery and auditing.

Quick Start

Provide a complete implementation plan in a dedicated worktree and save it to docs/superpowers/plans/YYYY-MM-DD-writing-plans.md

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan from a spec before coding?▼

Implementation plans are generated by mapping a formal spec to a structured file with task breakdowns, touched files, tests, and version-controlled commits. This reduces ambiguity and ensures traceability before engineers begin coding.

What is task decomposition and how does it help with multi-step software tasks?▼

Task decomposition splits multi-step software work into manageable tasks across subsystems or features. It maps specifications into concrete file changes and associated tests, reducing ambiguity and ensuring traceability throughout the development process.

How do I structure version-controlled commits in a software development plan?▼

Version-controlled commits are structured by defining concrete file changes and corresponding tests within the task breakdowns of an implementation plan. This ensures traceability and maps each commit to specific planned features.

Can I create a software implementation plan without providing any prior context?▼

Yes, you can create an implementation plan with zero-context input. The process drafts a comprehensive plan directly from a formal spec, saving it to a dated markdown file for easy discovery and auditing.

What is the best way to document and store development plans for auditing?▼

Development plans are documented with a header, task breakdowns, file changes, and tests, then saved to docs/superpowers/plans with a date and feature name. This ensures easy discovery and auditing of the implementation history.

When should I not use automated plan generation for software tasks?▼

Automated plan generation is not suited for single-step tasks or projects lacking a formal spec. It requires a defined specification to decompose work into structured tasks, files, tests, and commits effectively.

Related Skills

Explore More Software Engineering Skills→
ATTCKDigitalATTCKDigital
50

smith-specify

Creates formal feature specifications from natural language descriptions.

Official
Advanced
doitiandoitian
14

writing-plans

Generate bite-sized implementation tasks with file paths, tests, docs, and commits from a spec.

Community
Advanced
yairbedermanyairbederman

writing-plans

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

Community
Intermediate
EdgeAppEdgeApp
1

asana-plan

Generate structured technical implementation plans from Asana task URLs.

Official
Advanced