plan

Generate structured markdown planning documents for software development workflows.

Updated May 5, 2026
One-click install
npx skills add https://github.com/iani-kuli/harness_bro --skill plan-iani-kuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/ported/plan
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill plan-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents disorganized development by forcing a structured, thoughtful planning phase before any code is written or modified.

Core Features & Use Cases

  • Structured Planning: Creates consistent, actionable markdown plans that include goals, assumptions, and step-by-step implementation details.
  • Safety-First Workflow: Ensures the AI remains in a read-only planning state, preventing accidental code execution or file mutation during the design phase.
  • Use Case: When starting a complex refactoring task, use this skill to generate a comprehensive plan that outlines the necessary file changes and validation steps before you begin implementation.

Quick Start

Use the plan skill to create a detailed implementation strategy for the new authentication module.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a markdown project plan for software development?

Generate structured markdown project plans to define software development workflows, project scope, and task breakdowns before writing code. This ensures a safety-first, read-only design phase that prevents accidental file mutations.

What is the best way to outline a refactoring strategy before modifying code?

The best way to outline a refactoring strategy is creating a comprehensive markdown plan detailing necessary file changes and validation steps. This keeps the workflow in a read-only planning state, preventing accidental code execution during the design phase.

Do I need specific directory structures for storing markdown planning documents?

Yes, storing markdown planning documents requires adherence to specific file naming conventions and directory structures within your workspace environment. This organization ensures plans are consistently accessible during the development workflow.

Can I use planning workflows to assess project risks and assumptions?

Yes, planning workflows assess project risks and assumptions by generating structured markdown documents. These plans explicitly include project goals, assumptions, and step-by-step implementation details to guide the software development process.

Why does the planning phase prevent code execution?

The planning phase prevents code execution to enforce a safety-first workflow, keeping the system in a read-only state. This avoids accidental file mutation while you scope the project and break down tasks.

When should I not use a structured markdown plan for development?

Avoid using a structured markdown plan for simple tasks that do not require project scoping or risk assessment. It is designed for complex workflows needing a comprehensive implementation strategy before modifying code.