OpenParable
Skip to content
← Back to skills

Plan Design

Productivity
plan-design

Plan Design is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Design an implementation approach for a single ticket.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/planning/plan-design/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/plan-design, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Plan Design

The Planner drives this workflow. Produce a detailed, actionable implementation plan for a single work item. The plan must be specific enough that the implementer does not need to guess at file paths, content structures, or sequencing.


Phase 1: Understand the Ticket

Gather context before designing.

Steps

  1. Read the issue body and comments
  2. Identify acceptance criteria and constraints
  3. Read related files, prior ADRs, and architecture docs
  4. Note the current state of the codebase relevant to this change

Output

Produce a ticket summary covering: what the ticket asks for, acceptance criteria, relevant current state.

Approval Required: No


Phase 2: Design the Approach

Produce a complete, file-level implementation plan.

Steps

  1. Identify all files to create, modify, or delete
  2. For each file change, specify:
    • Exact file path
    • What to change (with enough context to locate the edit)
    • What the change should look like (new content or transformation)
  3. Define the implementation sequence (what order to make changes)
  4. Identify verification steps (how to confirm correctness)

Plan Quality Criteria

  • No guessing required: Every change specifies file path, location, and content
  • Sequenced: Changes are ordered so each step builds on the last
  • Verifiable: Each step has a way to confirm it worked
  • Scoped: Only changes needed for this ticket — nothing extra

Output

Produce an implementation plan covering: step-by-step file changes (file | action | details), verification steps, assumptions.

⛔ CHECKPOINT

STOP. Do not proceed until human approves the plan, verification steps, and assumptions.

Approval Required: Yes


Error Handling

ErrorRecovery
Ticket scope unclearAsk clarifying questions, refine acceptance criteria
Multiple valid approachesPresent top 2 options with trade-offs, recommend one
Dependencies on other ticketsNote the dependency, plan the work that can proceed independently
Missing contextUse /skill:plan-research to investigate before designing