skills.rest
bakwankawa
bakwankawaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate implementation plans from specs into timestamped Markdown files.

1|Updated Feb 1, 2026
Search Tags:#planning#documentation#TDD#workspaces#software-engineering#spec-to-plan#task-decomposition
One-click install
npx skills add https://github.com/bakwankawa/lazy-code-skill --skill writing-plans-bakwankawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/bakwankawa/lazy-code-skill/tree/main/.cursor/skills/superpowers/writing-plans
Command: npx skills add https://github.com/bakwankawa/lazy-code-skill --skill writing-plans-bakwankawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to translate a vague spec into concrete, actionable steps for code changes, tests, and docs.

Core Features & Use Cases

  • Comprehensive Implementation Plans: Generate detailed, task-by-task instructions including touched files, code, tests, docs, and verification criteria.
  • Workspace-Centric Storage: Save plans to .cursor/plans/ with timestamped filenames, ensuring reproducibility within the user's workspace.
  • Guided Workflows: Enforce DRY, YAGNI, and Test-Driven Development practices and support dedicated worktrees for brainstorming.

Quick Start

Use the writing-plans skill to create the implementation plan for a new feature specification.

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 feature spec before coding?▼

Yes, you can break complex bugs into actionable steps by processing the bug report through the task-decomposition workflow. It outputs a structured plan detailing code changes, test updates, and verification criteria formatted as a timestamped .md file in your workspace.

Does this approach support Test-Driven Development and DRY principles?▼

Yes, the generated plans enforce Test-Driven Development, DRY, and YAGNI practices. The workflow integrates these guidelines directly into the task-by-task instructions, ensuring your implementation steps align with standard software engineering methodologies.

Can I use this planning method for unfamiliar codebases?▼

Yes, this planning method is specifically designed for navigating unfamiliar codebases. It translates vague requirements into concrete steps for code changes and tests, helping you understand the necessary modifications before you start writing code.

Where are the generated implementation plans stored?▼

Generated implementation plans are stored in your project workspace. They are automatically formatted and saved as markdown files in the `.cursor/plans/` directory using a YYYY-MM-DD-<feature-name>.md naming convention for reproducibility.

Do I need external tooling to create multi-step task plans?▼

No external tooling is required to create multi-step task plans beyond your project workspace. The process operates entirely within your local environment to generate and save the documentation without needing additional dependencies.

Related Skills

Explore More Software Engineering Skills→
Agentic-Engineering-AgencyAgentic-Engineering-Agency
3

specsafe-new

Generate a new specification file for the SpecSafe TDD workflow.

Official
Basic
Strategic-AutomationStrategic-Automation
6

plan

Generate markdown planning documents with goals, steps, tests, and risks.

Official
Intermediate
KarlinskySKarlinskyS

writing-plans

Generate step-by-step implementation plans for multi-parameter software features with TDD cycles and commit instructions.

Community
Intermediate
eusouwillnuneseusouwillnunes

gerente

Create and manage Obsidian project tasks with YAML frontmatter and ISO 8601 timestamps.

Community
Advanced