Skip to content
Skills Library
Management & product · Planning

simple-plan

/simple-plan

Lightweight planning for small, quick changes. Combines propose, spec, and (optionally) design into one conversational pass, then writes tasks.md so the change is ready for implementation. Activates when users ask for "simple plan", "quick plan", "plan this", or "planning mode" for a change that doesn't warrant the full propose/spec/design ceremony.

Licence
MIT
Last repository change
26.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
2
URLs in SKILL.md
0
Deprecation

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

Licence

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

What to check before installing
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Lightweight planning for small, quick changes. Combines propose, spec, and (optionally) design into one conversational pass, then writes tasks.md so the change is ready for implementation. Activates when users ask for "simple plan", "quick plan", "plan this", or "planning mode" for a change that doesn't warrant the full propose/spec/design ceremony.

Triggers from the description

simple planquick planplan thisplanning mode
Original author description

Lightweight planning for small, quick changes. Combines propose, spec, and (optionally) design into one conversational pass, then writes tasks.md so the change is ready for implementation. Activates when users ask for "simple plan", "quick plan", "plan this", or "planning mode" for a change that doesn't warrant the full propose/spec/design ceremony.

How it works

  1. Process
  2. Artifact requirements
Original SKILL.md headings · 99 lines, 493 words
SKILL.md preview
---
name: simple-plan
description: >
  Lightweight planning for small, quick changes. Combines propose, spec, and (optionally) design
  into one conversational pass, then writes tasks.md so the change is ready for implementation.
  Activates when users ask for "simple plan", "quick plan", "plan this", or "planning mode" for
  a change that doesn't warrant the full propose/spec/design ceremony.
---

# Simple Plan

Plan a small change in one focused conversation. Produce a concise `proposal.md`, one spec per
capability, an optional `design.md`, and a `tasks.md` handoff. The artifacts must be self-contained for
an implementing agent with no conversation history.

## Process

1. Understand the problem, desired behavior, success criteria, and scope. Lightly inspect related
   specifications and relevant code so questions and artifacts reflect the existing system.
2. Use `codagent:ask-questions` to resolve the decisions behind the proposal, specs, and any design:
   - **Proposal:** the problem, desired outcome, success criteria, scope boundaries, and any choice
     between real alternatives that changes product scope or direction.
   - **Specs:** observable behavior, boundaries, errors, and edge cases that affect behavior or scope.
   - **Design:** consequential architectural choices that repository context cannot safely resolve.

   Recommend a default when useful, decide low-risk implementation details from repository context,
   and do not use a generic approval question as discovery.
3. Decide whether `design.md` is necessary. Default to no; write one only for a consequential
   architectural choice, non-obvious rationale, migration, integration strategy, or implementation
   constraint that the implementer otherwise would not know.
4. Present the proposed capability set, key requirements, design-doc decision, output location, and
   the consequential assumptions or defaults you selected, so the user can correct them. Wait for
   approval before writing.
5. Write all artifacts in one pass, then check them together for missing decisions or contradictions.
   Return to the user for any new behavioral or scope decision instead of inventing one.

Follow a project-defined location. Otherwise propose `~/.agent-skills/changes/<kebab-slug>/` at the
approval step. Do not run separate proposal, spec, and design phases, and do not write a detailed task
breakdown.

## Artifact requirements

### `proposal.md`

Keep the proposal brief: why, high-level changes, new and modified capabilities, out of scope, and
impact.

```markdown
## Why
<problem or opportunity>

## What Changes
- <high-level change>

## Capabilities

### New Capabilities
- `<name>`: <brief description>

### Modified Capabilities
- `<existing-name>`: <changed requirements>

## Out of Scope
<explicit exclusions>

## Impact
<affected code, APIs, dependencies, or users>
```

### `specs/<capability>/spec.md`

Specifications are the load-bearing artifact. Use SHALL or MUST, observable behavior, and at least one
`#### Scenario:` with WHEN/THEN per requirement. For a modified requirement, copy the complete existing
requirement and all scenarios under `## MODIFIED Requirements` before editing it. If behavior truly
depends on an unresolved architectural choice, mark the scenario
`<!-- deferred-to-design: <reason> -->` and resolve it in the design.

Use `## REMOVED Requirements` with **Reason** and **Migration**, and `## RENAMED Requirements` with
FROM and TO, when those delta operations apply.

```markdown
## ADDED Requirements

### Requirement: <name>
<normative behavior>

#### Scenario: <name>
- **WHEN** <condition>
- **THEN** <observable result>
```

### `design.md` when needed

Record only the context, approach, decisions and rationale, risks or trade-offs, and migration details
needed for implementation.

### `tasks.md`

Write one placeholder entry linking every artifact:

```markdown
- [ ] Implement the change described by these files:
  - [proposal.md](proposal.md)
  - [specs/<capability>/spec.md](specs/<capability>/spec.md)
  - [design.md](design.md) <!-- only when written -->
```

Versions

The database has no other skills named simple-plan.

Database snapshot: 13.11.2026 · package version 963ae3e2447f (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

  • 100planning-flow-quick
    Use when the user wants a quick plan for a small coding change — "quick plan", "plan this small fix", "/planning-flow-quick <ask>" — such as a renamed title, a corrected message, a one-function bug fix, or a small option, where the change still needs to follow the repository's…
  • 100spec-driven-planning
    Plan new features using spec-driven workflow — auto-picks Quick (single plan.md) or Full (3-file EARS spec) mode. Use when creating features, writing requirements, or designing architecture.
  • 100plan-only
    Plan-only mode that replicates Claude Code's built-in plan mode workflow but stops after the user approves the plan — no auto-execution. Use when the user wants to plan without executing, says "plan only", "just plan", "plan but don't execute", or when another skill needs…
  • 100spec
    Size a change (simple / smol / medium / big) and write the matching spec docs - plan mode, design.md, input→proposal→design, or research→proposal→design→tasks→validation. Use when the user asks to spec, plan, design, or scope a feature or change before coding, or invokes /easy-spec:spec.
  • 100chore
    Capture a simple task that does not need planning (CHORE + TASK in readyToWork by default, or registration-only with --no-task). Use when PM mentions "simple task", "chore", "small task", "housekeeping", "quick task", "мелкая задача", "чора", or any request to log routine work…
  • 100notion-spec-to-implementation
    Converts Notion product or technical specs into implementation plans, linked tasks, and evidence-based progress updates. Use for planning or implementing a spec, creating tasks from requirements, or reconciling implementation with spec changes.

Feedback and reports

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