Skip to content
Skills Library
Programming · Planning

concise-planning

/concise-planning

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

Repository
rei-skills ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Original author description

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

How it works

  1. Goal
  2. Workflow
  3. Plan Template
  4. Checklist Guidelines
  5. When to Use
Original SKILL.md headings · 67 lines, 221 words
SKILL.md preview
---
name: concise-planning
description: "Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist."
risk: unknown
source: rootcastle-rei
---

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

---

> 🏰 **Rei Skills** — Curated by [Rootcastle Engineering & Innovation](https://www.rootcastle.com) | Batuhan Ayrıbaş  
> Engineering Beyond Boundaries | admin@rootcastle.com

Versions

RepositoryScoreLicence
This page · rootcastleco/rei-skills100MIT
FrancoStino/opencode-skills-collection100MIT
davila7/claude-code-templates100MIT
craftos-dev/craftbot100MIT
hybridlabor-api/aos100Apache-2.0

Database snapshot: 13.11.2026 · package version 7a03aa3ad390 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100create-plan
    Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
  • 100create-plan
    Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
  • 90ct
    Plan implementation for a sufficiently clear feature or scoped task, including after /nf or /product. Use for 'create task', 'plan implementation', or 'technical decomposition'. Save a concise, executable plan in the existing task; use /nf for unresolved feature discovery and /si for implementation.
  • 90ct
    Plan implementation for a sufficiently clear feature or scoped task, including after /nf or /product. Use for 'create task', 'plan implementation', or 'technical decomposition'. Save a concise, executable plan in the existing task; use /nf for unresolved feature discovery and /si for implementation.
  • 100plan
    Create a concise, evidence-backed implementation plan in the repository planning area when the user explicitly asks for a plan.
  • 100plan
    Research and write an actionable implementation plan without implementing it. Use when the user asks to plan, design an approach, or inspect a change before coding; stop applying the planning restriction once the user explicitly asks to implement.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.