Concise planning

Skill lingxling/awesome-skills-cn/antigravity-awesome-skills/skills/concise-planning

热门Skills中文cn学习版+教程，提供7000+Skills，集成claude skills (11w+Star) | awesome-openclaw-skills (4w+Star) | ui-ux-pro-max-skill (4w+Star)等10余个热门Skill项目

Install

npx -y skills add lingxling/awesome-skills-cn --skill concise-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

SKILL.md

1.8 KB, 385 tokens by cl100k_base, as published. Nobody here has run it

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 of 6-10 atomic, ordered tasks (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

This skill is applicable to execute the workflow or actions described in the overview.

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.