concise-planning

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "concise-planning" with this command: npx skills add poletron/custom-rules/poletron-custom-rules-concise-planning

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

  1. Minimal Interaction
  • Ask at most 1–2 questions and only if truly blocking.

  • Make reasonable assumptions for non-blocking unknowns.

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

lancedb

No summary provided by upstream source.

Repository SourceNeeds Review
General

trpc

No summary provided by upstream source.

Repository SourceNeeds Review
General

javascript-mastery

No summary provided by upstream source.

Repository SourceNeeds Review
General

coding-standards

No summary provided by upstream source.

Repository SourceNeeds Review