concise-planning

Create an implementation_plan.md with goals, proposed changes, and verification.

1|3|Updated May 22, 2025
One-click install
npx skills add https://github.com/minuum/vla --skill concise-planning-minuum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: concise-planning
Source: https://github.com/minuum/vla/tree/main/.agent/skills/concise-planning
Command: npx skills add https://github.com/minuum/vla --skill concise-planning-minuum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures a disciplined planning phase before execution, preventing scope creep and overlooked risks.

Core Features & Use Cases

  • Structured planning: generate an implementation_plan.md with clear goals, scope, and milestones.
  • Risk assessment: identify potential risks, dependencies, and rollback strategies upfront.
  • Review prompts: trigger a user review step for complex tasks to ensure alignment before work begins.

Quick Start

Analyze the request, then draft an implementation_plan.md containing goals, proposed changes, and verification, and prompt the user to review the plan if the task is complex.

Frequently Asked Questions about concise-planning

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

FAQPage Schema
How do I plan feature changes before coding to prevent scope creep?▼

To plan feature changes before coding, generate an implementation_plan.md containing goals, proposed changes, and verification checkpoints to prevent scope creep and ensure a disciplined planning phase before execution.

What is an implementation plan and when do I need it for project management?▼

An implementation plan is a structured document outlining goals, proposed changes, and verification steps. You need it for new features, complex refactors, and ambiguous requests requiring a clear plan before coding begins.

Can I use a structured planning checklist for complex refactoring tasks?▼

Yes, you can use a structured planning checklist for complex refactoring tasks. It produces an implementation_plan.md with clear goals, scope, and milestones, and triggers a user review step to ensure alignment before work begins.

What's the best way to assess risks and dependencies upfront for a new feature?▼

The best way to assess risks and dependencies upfront is to draft an implementation_plan.md that identifies potential risks, dependencies, and rollback strategies before coding or refactoring begins.

Why does project planning fail when handling ambiguous requests?▼

Project planning fails with ambiguous requests when there is no clear plan. Generating an implementation_plan.md with goals, proposed changes, and verification prevents overlooked risks and scope creep.