propose-plan

Translate high-level decisions into a Git plan with branch, atomic commits, and verification steps.

6|3|Updated Sep 13, 2017
One-click install
npx skills add https://github.com/tomholford/dotfiles --skill propose-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propose-plan
Source: https://github.com/tomholford/dotfiles/tree/main/claude/skills/propose-plan
Command: npx skills add https://github.com/tomholford/dotfiles --skill propose-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Propose Plan helps teams translate high-level decisions into an executable sequence of actions, including a branch name, ordered atomic commits, and verification steps, so work moves from discussion to delivery without back-and-forth.

Core Features & Use Cases

  • Generate a concrete implementation plan tailored to the current codebase.
  • Define an atomic commit sequence with clear messages and correct dependency order.
  • Provide a ready-to-run rollout plan for feature branches, fixes, or refactors.

Quick Start

Outline a concrete plan you would implement in code, including a branch name, atomic commits, and verification steps.

Frequently Asked Questions about propose-plan

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

FAQPage Schema
How do I translate high-level decisions into an executable git workflow?

To translate decisions into a git workflow, you define a structured output that includes a branch name, a sequence of ordered atomic commits, and explicit verification steps. This moves work from discussion to delivery without back-and-forth.

What is the best way to plan atomic commits for a codebase change?

Planning atomic commits involves defining a sequence of commits with clear messages and correct dependency order tailored to the current codebase. This provides a ready-to-run rollout plan for feature branches, fixes, or refactors.

Can I generate a step-by-step plan for feature branches and verification steps?

Yes, you can generate a concrete implementation plan for feature branches that explicitly includes verification steps. It applies when a user needs a step-by-step plan for features, fixes, or changes across a codebase.

How do I structure a code review plan with ordered commits?

Structuring a code review plan requires defining an atomic commit sequence with clear messages and correct dependency order. This enforces a structured output that moves work from discussion to delivery.

Do I need a specific environment to generate an implementation plan for fixes and refactors?

No specific environment is needed to generate an implementation plan for fixes and refactors. The Skill applies when a user needs a step-by-step plan for changes across a codebase, requiring only a high-level decision as input.