multiAI Summary Pending
concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
28,273 stars
bysickn33
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/concise-planning/SKILL.md --create-dirs "https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/plugins/antigravity-awesome-skills-claude/skills/concise-planning/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/concise-planning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How concise-planning Compares
| Feature / Agent | concise-planning | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ```markdown # 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.