skills.rest
plastikaweb
plastikawebCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Converts a high-level spec into a structured implementation plan with tasks, file paths, and test steps.

1|Updated Oct 12, 2022
Search Tags:#workflow#planning#software engineering#TDD#task decomposition#plan documentation
One-click install
npx skills add https://github.com/plastikaweb/plastikspace --skill writing-plans-plastikaweb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/plastikaweb/plastikspace/tree/main/.agent/skills/writing-plans
Command: npx skills add https://github.com/plastikaweb/plastikspace --skill writing-plans-plastikaweb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert a vague requirement or spec into a complete, executable implementation plan. It eliminates guesswork by outlining tasks, files to touch, tests to write, and verification strategies before code is written.

Core Features & Use Cases

  • Comprehensive Implementation Plans: Document every step, files to touch, tests to write, and verification strategies.
  • TDD-Driven Workflows: Aligns with test-first development, including failing-to-pass cycles and commit checkpoints.
  • Plan Document Output: Generates a ready-to-save plan file that can be versioned and reviewed.

Quick Start

Provide a high-level feature name and requirements to the skill. The plan will be generated and saved at docs/plans/YYYY-MM-DD-<feature-name>.md

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I convert a high-level software spec into an executable implementation plan?▼

An implementation plan translates high-level software requirements into a structured document detailing component tasks, exact file paths, code steps, and verification strategies. It eliminates guesswork by outlining every step required before writing code.

What is the best way to document task decomposition for test-driven development?▼

Task decomposition for test-driven development is documented by generating a plan file that aligns with test-first workflows. This plan outlines failing-to-pass test cycles, exact file paths, and commit checkpoints to guide iterative development.

How do I create a TDD workflow plan that includes commit checkpoints?▼

You create a TDD workflow plan with commit checkpoints by inputting feature requirements to generate a structured plan. The output aligns with test-first development, documenting failing-to-pass test cycles and recommended commit messages for each step.

Can I version and review generated software development plans?▼

Yes, you can version and review generated software development plans. The process outputs a ready-to-save plan file at docs/plans/YYYY-MM-DD-<feature-name>.md, which can be committed to your repository for versioning and team review.

Does the generated implementation plan include exact file paths and test steps?▼

Yes, the generated implementation plan includes exact file paths and test steps. It produces a comprehensive document detailing component tasks, files to touch, code and test steps, and verification strategies to guide execution.

Related Skills

Explore More Software Engineering Skills→
qq824045252-ship-itqq824045252-ship-it

superpowers-writing-plans

Convert high-level specs into task-by-task implementation plans with file touchpoints.

Community
Advanced
mraakashshahmraakashshah
5

executing-beads

Automate the TDD cycle with failing tests, minimal implementation, refactoring, and atomic commits.

Community
Intermediate
tech-leads-clubtech-leads-club
5.0k

nx-generate

Generate libraries and applications using Nx generators in a monorepo.

Official
Intermediate
billydeeii136billydeeii136

writing-plans

Generates detailed implementation plans for complex software development tasks.

Community
Advanced