skills.rest
sorafujitani
sorafujitaniCOMMUNITY
Explore all skills by this author →
Website𝕏@sorafujitaniGitHub

plan:dry-coding

Plan code implementations with structured steps and file templates.

1|Updated Jan 20, 2026
Search Tags:#workflow#planning#coding#plan#code-review#dry-run
One-click install
npx skills add https://github.com/sorafujitani/claudedot --skill plan-dry-coding
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan:dry-coding
Source: https://github.com/sorafujitani/claudedot/tree/main/skills/plan%3Adry-coding
Command: npx skills add https://github.com/sorafujitani/claudedot --skill plan-dry-coding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode surfaces detailed implementation plans without editing actual files, enabling investigation, code planning, and review in a safe, review-friendly format.

Core Features & Use Cases

  • Generate deterministic, step-by-step implementation plans
  • Provide structured templates for files, directories, and code outline
  • Use in architectural reviews, feature scoping, and design demonstrations to align stakeholders

Quick Start

Describe a detailed, review-ready implementation plan for a feature without editing any files.

Frequently Asked Questions about plan:dry-coding

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

FAQPage Schema
How do I plan code implementations without modifying actual files?▼

You can plan code implementations without modifying actual files by generating a structured, deterministic plan with defined steps and file templates for review. This keeps your codebase safe during architecture reviews and feature scoping.

What is a dry-run approach for architectural reviews and feature scoping?▼

A dry-run approach for architectural reviews describes hypothetical code and structured templates without executing or editing files. It produces review-ready guidance to align stakeholders on feature design safely before actual implementation begins.

Can I generate step-by-step implementation plans for code review only?▼

Yes, you can generate step-by-step implementation plans strictly for code review only. This process yields a deterministic plan with clearly defined steps, file templates, and review-ready guidance without touching your actual codebase.

Does plan-mode coding work for creating file and directory templates without touching the codebase?▼

Plan-mode coding works for creating hypothetical file and directory templates by outlining structured code designs without touching the codebase. It provides a deterministic, review-friendly format to demonstrate features safely.

When should I use a hypothetical code plan instead of direct coding?▼

You should use a hypothetical code plan instead of direct coding during architectural reviews, feature scoping, or design demonstrations. This approach aligns stakeholders through review-ready guidance without the risk of altering actual files.

What is the best way to align stakeholders on a feature design before writing code?▼

The best way to align stakeholders on a feature design before writing code is producing a structured, deterministic implementation plan with file templates. This review-ready format demonstrates hypothetical code safely without editing actual files.

Related Skills

Explore More Software Engineering Skills→
TrecekTrecek
1

plan-arc

Propose a target architecture with components, boundaries, and diagrams.

Community
Advanced
Space-DinosaursSpace-Dinosaurs
12

agent-architect

Generate a concrete technical implementation plan from codebase analysis.

Official
Advanced
t-stringst-strings

Global Naming

Enforces global naming conventions across files, modules, and artifacts.

Official
Basic
semicolon-devteamsemicolon-devteam

generate-mockup

Generate UI mockups from design requirements using the 21st_magic_component_builder.

Official
Advanced