Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Concise Coding Task Planner

agent planning skill risk: low

Concise Coding Task Planner

Generates a single actionable plan with atomic steps for a coding task by scanning context, asking at most 1-2 questions, and outputting a structured markdown template with approac…

SKILL 1 file

SKILL.md
Download 
---
name: antigravity-awesome-skills-concise-planning-b1a5360a
description: "Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist."
---
# 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.

## 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.

REQUIRED CONTEXT

  • README.md
  • docs
  • relevant code files

ROLES & RULES

  1. Read README.md, docs, and relevant code files.
  2. Identify constraints (language, frameworks, tests).
  3. Ask at most 1–2 questions and only if truly blocking.
  4. Make reasonable assumptions for non-blocking unknowns.
  5. Use the following structure for the plan.
  6. Each step should be a single logical unit of work.
  7. Use verb-first phrasing for action items.
  8. Name specific files or modules when possible.
  9. Use this skill only when the task clearly matches the scope described above.
  10. Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  11. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Plan, Scope, Action Items, Open Questions
Constraints
  • use exact Plan template with Approach, Scope (In/Out), Action Items (6-10 atomic verb-first tasks), Validation, and Open Questions
  • atomic steps only
  • ask at most 1-2 clarifying questions if blocking

SUCCESS CRITERIA

  • Turn a user request into a single, actionable plan with atomic steps.
  • Produce 6-10 atomic, ordered, verb-first tasks.
  • Include at least one validation/testing item.
  • Limit open questions to at most 3.

FAILURE MODES

  • May produce a plan when inputs, permissions, or success criteria are missing.
  • May skip environment-specific validation or expert review.

CAVEATS

Dependencies
  • README.md
  • docs
  • relevant code files
Missing context
  • Explicit input format or example user request
  • How to handle non-coding tasks that might be presented
Ambiguities
  • "When to Use" references "the overview" which is not present in the prompt.
  • The phrase "execute the workflow or actions described in the overview" is vague.

QUALITY

OVERALL
0.82
CLARITY
0.85
SPECIFICITY
0.90
REUSABILITY
0.80
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Replace the vague "When to Use" sentence with a clear trigger condition such as: "Use when the user explicitly asks for a plan or checklist for a coding task."
  • Add one concrete before/after example of a user request and resulting plan.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT