planning-first

Produce an implementation plan before coding with file paths and verification steps.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/t0lab/harness-kit --skill planning-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-first
Source: https://github.com/t0lab/harness-kit/tree/main/.agents/skills/planning-first
Command: npx skills add https://github.com/t0lab/harness-kit --skill planning-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning-first prevents wasted implementation effort and fragile reviews by requiring a clear, actionable plan before writing code, ensuring the team implements the right solution in a reviewable way.

Core Features & Use Cases

  • Two-mode discipline: Light mode for trivial single-file changes and Full mode for multi-file or architecturally-novel work.
  • Five-phase workflow: Explore code and history, ask one clarifying question at a time, propose 2–3 approaches, write an immediately actionable plan, and gate execution on explicit approval with stop-on-failure verification.
  • Use case: Use when a user asks to "implement X", "build Y", "add a feature", or "refactor Z" to avoid rework and ensure mergeable, testable phases.

Quick Start

Ask the planning-first skill to create a full, actionable implementation plan for the requested feature starting with an exploratory read of the codebase and two recommended approaches.

Frequently Asked Questions about planning-first

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

FAQPage Schema
How do I create an implementation plan before coding to avoid wasted work?

A planning-first approach prevents wasted implementation effort by requiring a clear, actionable plan before writing code. It applies to multi-step, multi-file, or architecturally-novel development tasks to ensure the team builds the right solution in a reviewable way.

What is the best way to plan a multi-file software refactoring task?

The best way to plan a multi-file software refactoring task is to use a structured workflow that explores code history, asks clarifying questions, proposes approaches, and writes an actionable plan with per-task file paths and verification steps before execution begins.

How do I structure an actionable implementation plan for a new software feature?

Structure an actionable implementation plan by proposing two to three approaches, enumerating per-task file paths, defining verification steps, and gating code execution on explicit approval to ensure mergeable, testable phases and stop-on-failure verification.

When do I need a detailed architecture plan for software development?

You need a detailed architecture plan for software development when handling multi-step, multi-file, or architecturally-novel tasks. User requests like implementing, building, adding, or refactoring features require this discipline to avoid incorrect implementations and rework.

Does a pre-coding plan work for single-file changes or only multi-file refactoring?

A pre-coding plan works for both single-file changes and multi-file refactoring. Light mode handles trivial single-file changes, while Full mode manages multi-file or architecturally-novel work by proposing approaches and gating execution on approval.