OpenParable
Skip to content
← Back to skills

Simple Plan

Productivity
simple-plan

Simple Plan is an Agent Skill for productivity published in the dcouple/Pane repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Quick gut-check before implementing when the user directly asks you to do something. Investigates, proposes a lightweight plan, and implements only after approval. Use this instead of `plan` when the change is straightforward.

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/dcouple/Pane/blob/HEAD/.codex/skills/simple-plan/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/simple-plan, 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.

Simple Plan

When the user directly asks for a change, investigate first and propose a short plan before writing code.

Plan Contents

Current State

  • root cause or current behavior
  • concrete file references

Proposed Changes

  • what needs to change
  • file references where relevant
  • task list in implementation order

Advice

  • architectural or implementation guidance when useful

Process

  1. Investigate the codebase first
  2. Present the plan to the user
  3. Only implement after approval
  4. After approval, keep one primary implementation authority by default
  5. Keep the user's why, constraints, and non-goals explicit during implementation
  6. After implementation, run implementation-reviewer
  7. Prefer a fresh skeptical second review pass before declaring completion
  8. If you have a separate Claude workflow available, it can be the parallel second-opinion lane, but Codex remains primary on this path

Notes

  • Keep the plan concise but concrete
  • Include file references whenever possible
  • If the task is broad or risky, recommend switching to plan
  • Do not implement anything until the user approves