mcpField
C
concise-planning

concise-planning

github.com/sickn33Agent workflows48.7k1.1k installsUpdated today
Repository

About concise-planning

A skill that turns coding requests into short, actionable plans for tasks needing clear scope and validation. It emphasizes atomic, ordered steps and asks questions only when essential information is blocking.

Key features

  1. 01Review project context and constraints
  2. 02Define included and excluded scope
  3. 03Create ordered atomic steps
  4. 04Include validation such as testing
  5. 05Limit questions to blocking gaps

Use cases

  1. 01Breaking a feature request into coding steps
  2. 02Defining boundaries for a refactoring task
  3. 03Preparing an implementation checklist with test validation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill concise-planning

After installing, type/concise-planningin Claude Code to confirm it loaded.

Details

From the project README

Concise Planning

Goal

Turn a user request into a single, actionable plan with atomic steps.

Workflow

1. Scan Context
  • Read README.md, docs, and relevant code files.
  • Identify constraints (language, frameworks, tests).
2. Minimal Interaction
  • Ask at most 1–2 questions and only if truly blocking.
  • Make reasonable assumptions for non-blocking unknowns.
3. Generate Plan

Use the following structure:

  • Approach: 1-3 sentences on what and why.
  • Scope: Bullet points for "In" and "Out".
  • Action Items: A list sized to the actual task, with atomic, ordered actions (Verb-first).
  • Validation: At least one item for testing.

Plan Template

# Plan

<High-level approach>

## Scope

- In:
- Out:

## Action Items

- [ ] <Step 1: Discovery>
- [ ] <Step 2: Implementation>
- [ ] <Step 3: Implementation>
- [ ] <Step 4: Validation/Testing>
- [ ] <Step 5: Rollout/Commit>

## Open Questions

- <Question 1 (max 3)>

Checklist Guidelines

  • Atomic: Each step should be a single logical unit of work.
  • Verb-first: "Add...", "Refactor...", "Verify...".
  • Concrete: Name specific files or modules when possible.

When to Use

Use when the user asks for a coding plan and the outcome, scope, dependencies and verification should become a short ordered checklist.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported