plan-small

Generate a structured plan file at .plans/<slug>/plan.md for single-PR changes.

30|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/hawkyre/hawk-skills --skill plan-small
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-small
Source: https://github.com/hawkyre/hawk-skills/tree/main/skills/plan-small
Command: npx skills add https://github.com/hawkyre/hawk-skills --skill plan-small

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and formalize small, single-PR changes into a reproducible plan document, ensuring a clear, auditable process.

Core Features & Use Cases

  • Formal plan generation for small feature changes that fit in one PR.
  • Self-review and MUST-FIX/SHOULD-FIX application to the plan before user presentation.
  • Outputs the plan to .plans/<slug>/plan.md and guides the user through a gated workflow.

Quick Start

Run the plan-small skill to create a structured plan for a small change; it will generate a .plans/<slug>/plan.md and present it for review.

Frequently Asked Questions about plan-small

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

FAQPage Schema
How do I create a structured plan for a single-PR code change?

To create a structured plan for a single-PR code change, use a planning assistant to generate guiding questions, core assumptions, and a self-review stage, outputting an auditable plan file to .plans/<slug>/plan.md.

What is a self-review stage in an automated workflow plan?

A self-review stage in an automated workflow plan applies MUST-FIX and SHOULD-FIX improvements to the generated plan before presenting it to the user, ensuring the final document is auditable and refined.

Can I use a planning assistant for larger multi-PR feature updates?

No, this planning assistant is designed specifically for small changes that fit within a single PR, such as individual feature, endpoint, component, or config updates, and is not suited for multi-PR scopes.

What's the best way to ensure my small code changes are auditable before implementation?

The best way to ensure small code changes are auditable is to enforce gated workflows that generate a formal plan document, requiring user review of core assumptions and self-review improvements before implementation begins.

Does the generated plan file get saved to a specific location?

Yes, the generated plan file is saved to a specific location in your repository at .plans/<slug>/plan.md, providing a reproducible artifact for the proposed single-PR change.

Why does my planning workflow include a question gate?

A planning workflow includes a question gate to ensure all guiding questions and core assumptions are formally addressed and reviewed before the final plan file is generated and implementation proceeds.