New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Create A Plan

by dojoengine in dojoengine/dojo

Conduct a focused technical planning interview to produce an implementable, parallelizable plan or spec with clear dependencies, risks, and open questions.

Apache-2.0Auto-check passedGame Development

Install Create A Plan

skills CLI
$ npx skills add dojoengine/dojo --skill create-a-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dojoengine/dojo create-a-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dojoengine/dojo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-a-plan .claude/skills/create-a-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-a-plan
GitHub stars
478
Token cost
~1.7k tokens
SKILL.md length
594 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Conduct a focused technical planning interview to produce an implementable, parallelizable plan or spec with clear dependencies, risks, and open questions.

  • Works in 5 steps: Preflight → Discovery → Deep Interview → …
  • Game Development work in your project
  • SKILL.md covers Invocation, Process, Output Format and Interview Flow Example, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Create A Plan is an agent skill from dojoengine/dojo. Conduct a focused technical planning interview to produce an implementable, parallelizable plan or spec with clear dependencies, risks, and open questions.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Game Development. It works with Rust. The repository describes itself as: Dojo is a toolchain for building provable games and applications. The licence is Apache-2.0.

When your agent uses it

  • Game Development work in your project

Example prompts

  • “/create-a-plan”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Preflight
  2. Discovery
  3. Deep Interview
  4. Dependency Analysis
  5. Plan Generation

What it can do on your machine

Read from SKILL.md and the folder at commit 19c258a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create A Plan loads about 1.7k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 594 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dojoengine/dojo at commit 19c258a, republished under its Apache-2.0 licence (© dojoengine). 594 words, ~1,746 tokens.

Download SKILL.mdSave it as .claude/skills/create-a-plan/SKILL.md (or your agent's skills folder).
name
create-a-plan
description
Conduct a focused technical planning interview to produce an implementable, parallelizable plan or spec with clear dependencies, risks, and open questions.

Create a Plan Skill

This skill runs a structured technical interview to turn a rough idea or an existing spec into a detailed, implementable plan. The output is organized for parallel execution: foundations first, then independent workstreams, then merge and integration.

Invocation

The user will provide one of:

  • A path to a spec or plan file (for example: SPEC.md, PLAN.md, RFC.md)
  • A rough description of what they want to build
  • A feature request or problem statement

Output is always written to PLAN.md in the repo root.

Process

Phase 0: Preflight
  1. If a file path is provided, read it first and note goals, non-goals, constraints, and gaps.
  2. Confirm you will produce PLAN.md as the output in the repo root. If PLAN.md already exists, update it rather than creating a new file.
Phase 1: Discovery

Summarize what is known, then identify missing details. Focus on:

  • Goals and non-goals
  • Constraints (time, budget, platform, dependencies)
  • Success metrics and acceptance criteria
Phase 2: Deep Interview

Use the AskUserQuestion (Claude) and/or request_user_input (Codex) tools in rounds. Ask 1-3 questions per round. Each round should go deeper and avoid repeating what is already known.

CRITICAL RULES:

  1. Never ask obvious questions. If the codebase or spec already answers it, do not ask it again.
  2. Ask about edge cases and failure modes.
  3. Probe for hidden complexity (state transitions, migrations, concurrency).
  4. Challenge assumptions when they create risk or ambiguity.
  5. Identify parallelization boundaries and serial dependencies.
  6. If the user is unsure, propose a default and ask for confirmation.

Question categories to cover as relevant:

  • Technical architecture and data flow
  • Data model and state management
  • API contracts and versioning
  • Caching and invalidation
  • Background jobs, retries, and idempotency
  • Error handling and recovery
  • Observability and debugging
  • Performance, scale, and SLAs
  • Security, privacy, and compliance
  • Integrations and external dependencies
  • UX flows, accessibility, and responsiveness
  • Rollout, migration, and rollback
  • Testing strategy and validation
Phase 3: Dependency Analysis

Identify:

  1. Serial dependencies that must complete first
  2. Parallel workstreams that can run independently
  3. Merge points where work reconvenes
Show full SKILL.md (254 more words)Show less
Phase 4: Plan Generation

Write the final plan to PLAN.md. Ensure the plan includes concrete verification steps the agent can run end to end. If the user only wants a plan in chat, provide it inline and mention that it would be written to PLAN.md.

Output Format

The generated plan MUST follow this structure:

markdown
# [Feature Name] Implementation Plan

## Overview
[2-3 sentence summary of what this implements and why]

## Goals
- [Explicit goal 1]
- [Explicit goal 2]

## Non-Goals
- [What this explicitly does NOT do]

## Assumptions and Constraints
- [Known constraints or assumptions]

## Requirements

### Functional
- [Requirement]

### Non-Functional
- [Performance, reliability, security, compliance]

## Technical Design

### Data Model
[Schema changes, new entities, relationships]

### API Design
[New endpoints, request/response shapes, versioning]

### Architecture
[System diagram in text or mermaid, component interactions]

### UX Flow (if applicable)
[Key screens, loading states, error recovery]

---

## Implementation Plan

### Serial Dependencies (Must Complete First)

These tasks create foundations that other work depends on. Complete in order.

#### Phase 0: [Foundation Name]
**Prerequisite for:** All subsequent phases

| Task | Description | Output |
|------|-------------|--------|
| 0.1 | [Task description] | [Concrete deliverable] |
| 0.2 | [Task description] | [Concrete deliverable] |

---

### Parallel Workstreams

These workstreams can be executed independently after Phase 0.

#### Workstream A: [Name]
**Dependencies:** Phase 0
**Can parallelize with:** Workstreams B, C

| Task | Description | Output |
|------|-------------|--------|
| A.1 | [Task description] | [Concrete deliverable] |
| A.2 | [Task description] | [Concrete deliverable] |

#### Workstream B: [Name]
**Dependencies:** Phase 0
**Can parallelize with:** Workstreams A, C

| Task | Description | Output |
|------|-------------|--------|
| B.1 | [Task description] | [Concrete deliverable] |

---

### Merge Phase

After parallel workstreams complete, these tasks integrate the work.

#### Phase N: Integration
**Dependencies:** Workstreams A, B, C

| Task | Description | Output |
|------|-------------|--------|
| N.1 | [Integration task] | [Concrete deliverable] |

---

## Testing and Validation

- [Unit, integration, end-to-end coverage]
- [Manual test plan if needed]

## Rollout and Migration

- [Feature flags, staged rollout, migration steps]
- [Rollback plan]

## Verification Checklist

- [Exact commands or manual steps the agent can run to verify correctness]
- [Expected outputs or success criteria]

## Risk Assessment

| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk description] | Low/Med/High | Low/Med/High | [Strategy] |

## Open Questions

- [ ] [Question that still needs resolution]

## Decision Log

| Decision | Rationale | Alternatives Considered |
|----------|-----------|------------------------|
| [Decision made] | [Why] | [What else was considered] |

Interview Flow Example

Round 1: High-Level Architecture

  • "The spec mentions a sync engine. Is this push-based (webhooks), pull-based (polling), or event-driven (queue)?"
  • "What is the expected data volume and throughput?"

Round 2: Edge Cases

  • "If a batch fails mid-run, do we retry the whole batch or resume from a checkpoint?"
  • "What happens when source data is deleted but still referenced downstream?"

Round 3: Parallelization

  • "Can we process different categories independently, or are there cross-category dependencies?"
  • "Is there a natural partition key that allows sharding?"

Round 4: Operational

  • "What is the acceptable latency for sync or processing?"
  • "How will operators debug failures and what visibility do they need?"

Key Behaviors

  1. Persist until the plan is implementable and verifiable by the agent, but avoid user fatigue by batching questions.
  2. Challenge vague answers when they affect design decisions.
  3. Identify hidden work and operational overhead.
  4. Think about the merge and integration steps early.
  5. Summarize understanding and confirm before writing the final plan.

Completing the Interview

After sufficient rounds of questions:

  1. Summarize your understanding back to the user
  2. Confirm the parallelization strategy
  3. Write the complete plan to the target file
  4. Ask if any sections need refinement

© dojoengine, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/create-a-plan of dojoengine/dojo.

Open the folder on GitHubat commit 19c258a

Compare with similar skills

Create A Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create A Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create A Plan this skilldojoengine/dojo478—~1.7kAutomated safety check: PassApache-2.0
ReleaseBloom-Engine/engine134—~1.4kAutomated safety check: NotesMIT
Add ThemeIvanWng97/pixtuoid489—~449Automated safety check: PassMIT
Build Accelerationmohitmishra786/low-level-dev-skills253—~1.4kAutomated safety check: PassMIT
Gdextensionjame581/GodotPrompter795—~2.7kAutomated safety check: PassMIT
Godot Genre Survivalthedivergentai/GD-Agentic-Skills809—~3.4kAutomated safety check: PassLGPL-3.0

Similar skills

  • Release

    Bloom-Engine/engine

    Cut a new Bloom Engine release — bump package.json if requested, commit, tag, push, create GitHub Release, and watch the gated release pipeline

    134 GitHub stars~1.4k tokensUpdated 27 days ago
    Game DevelopmentAuto-check: notes

  • Add Theme

    IvanWng97/pixtuoid

    Add a new color theme to pixtuoid (a full Theme palette, rendered into the office).

    489 GitHub stars~449 tokensUpdated today
    Game DevelopmentAuto-check passed

  • Build Acceleration

    mohitmishra786/low-level-dev-skills

    Build acceleration skill for C/C++ projects. An agent skill from mohitmishra786/low-level-dev-skills.

    253 GitHub stars~1.4k tokensUpdated 3 mo ago
    Game DevelopmentAuto-check passed

  • Gdextension

    jame581/GodotPrompter

    A skill your agent uses when building native extensions for Godot — godot-cpp (C++) or gdext (Rust), binding classes, building, and GDScript/C interop

    795 GitHub stars~2.7k tokensUpdated 2 days ago
    Game DevelopmentAuto-check passed

  • Godot Genre Survival

    thedivergentai/GD-Agentic-Skills

    Expert blueprint for survival games (Minecraft, Don't Starve, The Forest, Rust) covering needs systems, resource gathering, crafting recipes, base building, and progression balancing.

    809 GitHub stars~3.4k tokensUpdated 29 days ago
    Game DevelopmentAuto-check passed

  • Unity Development Loop

    akiojin/unity-cli

    Run Unity runtime development loops with gameplay-focused implementation and validation.

    107 GitHub stars~1.6k tokensUpdated 3 days ago
    Game DevelopmentAuto-check passed

More from dojoengine/dojo

  • Create PR

    dojoengine/dojo

    Create or update a PR from current branch to main, watch CI, and address feedback

    478 GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check passed

  • Dojo Contributing

    dojoengine/dojo

    Contributor workflow for dojoengine/dojo. An agent skill from dojoengine/dojo.

    478 GitHub stars~356 tokensUpdated 5 mo ago
    Auto-check passed

Works with

Categories

Questions about Create A Plan

What does Create A Plan do?

Conduct a focused technical planning interview to produce an implementable, parallelizable plan or spec with clear dependencies, risks, and open questions. Create A Plan is an agent skill from dojoengine/dojo. Conduct a focused technical planning interview to produce an implementable, parallelizable plan or spec with clear dependencies, risks, and open questions.

When should I use Create A Plan?

Create A Plan fits situations like: game Development work in your project.

How do I install Create A Plan in Claude Code?

Run `npx skills add dojoengine/dojo --skill create-a-plan -a claude-code`. Or copy the skill folder (.agents/skills/create-a-plan in dojoengine/dojo) into .claude/skills/create-a-plan in your project. Claude Code loads it when a task matches its description.

How do I install Create A Plan in Codex?

Run `npx skills add dojoengine/dojo --skill create-a-plan -a codex`. Or copy the skill folder (.agents/skills/create-a-plan in dojoengine/dojo) into .agents/skills/create-a-plan in your project. Codex loads it when a task matches its description.

Can I use Create A Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dojoengine/dojo --skill create-a-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-a-plan, .gemini/skills/create-a-plan, .github/skills/create-a-plan and .opencode/skills/create-a-plan in your project.

What does Create A Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Create A Plan is instructions for the agent only.

Does Create A Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Create A Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create A Plan use?

Create A Plan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create A Plan use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create A Plan?

Skills that share tags, products or a category with Create A Plan: Release (Bloom-Engine/engine, 134 stars), Add Theme (IvanWng97/pixtuoid, 489 stars), Build Acceleration (mohitmishra786/low-level-dev-skills, 253 stars) and Gdextension (jame581/GodotPrompter, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create A Plan?

dojoengine (a GitHub organization) maintains it in dojoengine/dojo, which has 478 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on May 6, 2026.

Source: dojoengine/dojo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.