skills.rest
MarbleSodas
MarbleSodasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate implementation plans decomposing features into testable engineering tasks.

Updated Apr 9, 2026
Search Tags:#workflow#tdd#documentation#implementation planning#git commits#subagent-driven-development
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill writing-plans-marblesodas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill writing-plans-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted engineering time by turning ambiguous feature requests into explicit, file-by-file implementation plans with verification steps.

Core Features & Use Cases

  • Bite-sized TDD task breakdown: Produces 2–5 minute tasks that follow the full failing-test → minimal code → passing-test → commit loop.
  • Zero-context onboarding: Writes plans that assume the implementer knows little about the codebase and the problem domain.
  • Execution-ready handoff: Includes an approach for dispatching each task to subagents using subagent-driven-development, with review gates.

Quick Start

Ask the AI to generate an implementation plan for your feature and include exact file paths, complete code snippets, test commands, and verification steps.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down feature requirements into testable implementation tasks?▼

Implementation plans decompose features into bite-sized, step-by-step engineering tasks using a TDD-style structure of failing tests, minimal code, passing tests, and frequent git commits. This breakdown produces 2–5 minute tasks that ensure precise, file-by-file development guidance.

How do I create zero-context implementation plans for subagent-driven development?▼

You generate execution-ready implementation plans that assume the implementer knows little about the codebase. These plans include exact file paths, complete code snippets, and verification steps, enabling direct dispatch to subagents with review gates.

What is the best way to structure TDD workflow tasks for developers with no codebase context?▼

The best way is using a TDD-style task structure that provides zero-context onboarding. It writes explicit plans with exact file paths, complete code snippets, test commands, and runnable verification steps, ensuring developers can execute without prior domain knowledge.

Can I use implementation planning to enforce DRY and YAGNI discipline in multi-step development?▼

Yes, implementation planning enforces DRY and YAGNI discipline by decomposing multi-step development into testable tasks. It generates precise, file-by-file instructions with frequent commit guidelines, preventing wasted engineering time from ambiguous feature requests.

Does implementation planning include exact file paths and runnable verification commands?▼

Yes, implementation planning includes exact file paths, complete code snippets, test commands, and runnable verification steps. This explicit file-by-file structure ensures execution-ready handoff and precise guidance for implementers lacking codebase context.

Related Skills

Explore More Software Engineering Skills→
BradliebsBradliebs

ce-plan

Transform feature descriptions into structured implementation plans with repo-relative file paths.

Community
Advanced
ArtemioPadillaArtemioPadilla
3

subagent-orchestration

Dispatch specialized subagents with model selection and two-stage review loops.

Community
Advanced
zeronx798zeronx798

plan

Generate structured markdown implementation plans for software development tasks.

Community
Advanced
ihatesea69ihatesea69
3

illustration-generator

Generate prompts for hand-drawn infographic-style illustrations for dev.to articles.

Community
Basic