Skip to content
Skills Library
Programming · Planning

plan

/plan

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.

Repository
openbitfun ↗
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
0
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

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.

Original author description

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.

How it works

  1. Workflow
  2. Plan Artifact
  3. Rules
Original SKILL.md headings · 39 lines, 347 words
SKILL.md preview
---
name: plan
description: 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.
---

# Plan

Produce a concise, evidence-backed implementation plan and leave project source unchanged.

## Workflow

1. Inspect the relevant code, configuration, documentation, and repository instructions using read-only tools. Resolve important behavior and ownership questions before drafting the plan.
2. Ask the user when missing information would materially change the approach. Present concrete options and put the recommended option first. Do not ask whether to proceed merely because research is complete.
3. Use `Task` only for read-only research that materially improves the plan. Keep delegated scopes bounded and synthesize the findings yourself.
4. Use `Write` to create one plan artifact at `.openbitfun/plans/<short-kebab-name>.plan.md`. Use a concise descriptive filename, and do not overwrite a different existing plan blindly.
5. Once the plan artifact is created and meets the format and content requirements, stop tool use and link the file without repeating its contents.

## Plan Artifact

Create the artifact using this complete file structure. The artifact consists of a YAML frontmatter and a non-empty Markdown body whose first line is a level-1 heading.

```markdown
---
name: Short Plan Name
overview: One or two sentence overview
---

# Short Plan Name

...
```

- The plan should be concise and actionable. Focus on high-level meaningful decisions rather than low-level implementation details
- Keep the plan proportional to the request and cite specific workspace-relative files with Markdown links when useful.

## Rules

- Follow the system prompt's `Language Preference` for the plan's `name`, `overview`, Markdown body, and user-facing replies unless the user explicitly requests another language. Keep YAML keys, code identifiers, commands, and file paths unchanged.
- Do not edit project source, change configuration, run mutating commands, or otherwise implement the task while this planning workflow applies. The only permitted mutation is a `.openbitfun/plans/*.plan.md` artifact.
- Before creating a new plan, inspect `.openbitfun/plans` and choose an unused filename.
- For a requested revision, Read the existing plan first and then use Edit or Write only on that same `.openbitfun/plans/*.plan.md` file.
- Once the user explicitly approves the plan or asks to implement, leave this planning workflow and perform the requested work normally.

Versions

RepositoryScoreLicence
This page · gcwing/openbitfun100MIT
mlophez/polix-ai100Apache-2.0
jeremylongshore/tons-of-skills-marketplace100MIT
duronext/jig100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
xoai/sage100MIT
JoDi-27/JoDi-SDD100MIT

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

  • 90plan-review
    Use when reviewing an implementation plan before coding or launching workers to check approach, scope, and repo-convention fit.
  • 100design
    Plan implementation before coding: investigate the repo, write spec and plan, and validate with a peer. Use for "plan", "design approach", "scope", or any coding task needing a plan. Not system-design thinking (/ship:arch-design) or full /ship:auto.
  • 90implementation-plan
    Produce an executable, repository-grounded implementation plan with bounded steps and verification gates. Use for multi-file features or risky changes before coding; not for trivial edits.
  • 100concise-planning
    Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
  • 90sp-planning
    Use when the user asks for a concrete implementation plan for an agreed change before code is written.
  • 100planning-flow
    Use when the user asks for a plan for a coding change — "plan this", "how would we build", "write me a plan for", "/planning-flow <ask>" — before any code is written, especially when the change needs research across a codebase, has open questions only the user can answer, or…

Feedback and reports

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