planning

Create a written plan in docs/plans/ before multi-file coding.

Updated Mar 1, 2026

Search Tags:#planning #architecture #approval #project-scoping #docs/plans #planning-document

Ready to run

npx skills add https://github.com/murphyjoseph/dojo-kit --skill planning-murphyjoseph

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/murphyjoseph/dojo-kit/tree/main/skills/planning
Command: npx skills add https://github.com/murphyjoseph/dojo-kit --skill planning-murphyjoseph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning before implementation reduces rework, clarifies scope, and aligns stakeholders on goals.

Core Features & Use Cases

Written plan in docs/plans/ before coding to define scope, architecture impact, data flow, and testing strategy.
Approval gating to pause implementation until explicit user approval.
Template-driven guidance using the plan-template to standardize artifacts across projects.

Quick Start

Write a plan document in docs/plans/ describing the work to be done and await explicit approval before implementing any code.

Frequently Asked Questions about planning

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

FAQPage Schema

Why create a planning document before starting multi-file coding work?▼

A planning document reduces rework and clarifies scope by aligning architecture, data flow, and testing expectations across UI, data, and API layers before implementation begins.

How do I scope a software project that touches multiple architectural boundaries?▼

Scope multi-file project work by writing a plan in docs/plans/ that defines scope, architecture impact, data flow, and testing strategy, then await explicit user approval before coding.

Can I start implementing code immediately if I have a clear architecture in mind?▼

No, this approach enforces approval gating to pause implementation until explicit user approval is granted, ensuring stakeholders align on goals and scope before any code is written.

What is the best way to standardize project scoping documents across different repositories?▼

Standardize project scoping documents by applying a template-driven approach using a plan template, ensuring consistent artifacts that define scope, architecture impact, and testing strategy.

When do I need to write a formal plan for refactoring across boundaries?▼

You need a formal plan when features touch multiple files, involve UI, data, and API layers, or require refactoring across boundaries, ensuring a written plan is created before implementation.