writing-plans

Generate step-by-step implementation plans with exact file paths, tests, and commit commands.

38|12|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/databrickslabs/coding-agents-databricks-apps --skill writing-plans-databrickslabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/databrickslabs/coding-agents-databricks-apps/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/databrickslabs/coding-agents-databricks-apps --skill writing-plans-databrickslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent implementation, missed requirements, and poor test coverage that occurs when engineers with minimal codebase context work on multi-step coding tasks, by generating a complete, actionable implementation plan with all necessary details.

Core Features & Use Cases

  • Bite-Sized Task Breakdown: Splits multi-step coding tasks into 2-5 minute actionable steps, each with a single clear objective.
  • Complete Implementation Guidance: Includes exact file paths, test code, minimal implementation snippets, and exact git commit commands for every step.
  • Best Practice Enforcement: Embeds TDD, DRY, and YAGNI principles into every plan, with explicit test pass/fail checks for each step.
  • Use Case: For example, when adding a new Databricks Unity Catalog permission check to an existing user management module, this skill generates a full plan with failing tests, implementation steps, and validation commands to ensure consistent, tested code.

Quick Start

Use the writing-plans skill to create a step-by-step implementation plan for adding a new rate-limiting feature to the existing API endpoint module.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create a step-by-step implementation plan for a multi-step coding task?

A step-by-step implementation plan breaks multi-step coding tasks into 2-5 minute actionable steps, each with a single clear objective, exact file paths, test code, and minimal implementation snippets. This eliminates context gaps for engineers with minimal codebase knowledge.

What is task breakdown in software development and how does it enforce TDD?

Task breakdown in software development splits large features into bite-sized steps that embed Test-Driven Development, DRY, and YAGNI principles. Each step includes explicit test pass/fail checks, failing tests, implementation snippets, and validation commands.

Can I use code planning workflows for bug fixes and code refactoring?

Yes, code planning workflows apply to feature implementation, bug fixes, and code refactoring. They generate comprehensive plans with exact git commit commands and test code to ensure consistent, tested delivery across all these software development scenarios.

What's the best way to plan code implementation for engineers unfamiliar with a codebase?

The best way to plan code implementation for engineers unfamiliar with a codebase is generating a plan with 2-5 minute task granularity. This includes exact file paths, implementation snippets, and commit commands to satisfy requirements for consistent delivery.

Why does implementation planning require exact file paths and git commit commands for every step?

Implementation planning requires exact file paths and git commit commands for every step to eliminate context gaps and missed requirements. This detailed actionable guidance ensures consistent, tested delivery when engineers have minimal codebase context.