concise-planning – Coding skill for AI agents
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
Install the concise-planning skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/concise-planning-f15a3.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /concise-planning – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/concise-planning-f15a3.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $concise-planning – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/concise-planning-f15a3.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /concise-planning – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/concise-planning-f15a3.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /concise-planning – then describe the task you want done.
SKILL.md content
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.
Related skills
- conductor-revert – Git-aware undo by logical work unit (track, phase, or task)
- rust-async-patterns – Master Rust async programming with Tokio, async traits, error handling, and concurrent…
- python-debugpy – Debug Python: pdb REPL + debugpy remote (DAP).
- context-driven-development – Guide for implementing and maintaining context as a managed artifact alongside code…
- convex – Convex reactive backend expert: schema design, TypeScript functions, real-time…
- convex-backend – Build reactive backends with Convex functions, schema validation, auth integration, and…
- copilot-delegate – Delegate coding tasks to the GitHub Copilot CLI (`copilot`) only when the user…
- copilot-sdk – Build applications that programmatically interact with GitHub Copilot. The SDK wraps the…