Agent skill · Workflow & Productivity

plan

Plan mode: write markdown plan, no execution.

HezaoHezaogithub.com/HezaoHezaoGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add HezaoHezao/poirot --skill plan --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Declared author: Adapted from hermes-agent (Nous Research, MIT); writing-craft from obra/superpow
Allowed tools: -write_file-read_file-list_dir-bash
Path: poirot/backend/agents/skill/builtin_skills/core/plan/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 139
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Plan Mode Use this skill when the user wants a plan instead of execution. ## Core behavior For this turn, you are planning only. - Do not implement code. - Do not edit project files except the plan markdown file. - Do not run mutating terminal commands, commit, push, or perform external actions. - You may inspect the repo or other context with read-only commands/tools when needed. - Your deliverable is a markdown plan saved under `.poirot/plans/`. ## Output requirements Write a markdown plan that is concrete and actionable. Include, when relevant: - Goal - Current context / assumptions - Proposed approach - Step-by-step plan - Files likely to change - Tests / validation - Risks, tradeoffs, and open questions If the task is code-related, include exact file paths, likely test targets, and verification steps. ## Save location Save the plan with `write_file` under: - `.poirot/plans/YYYY-MM-DD_HHMMSS-<slug>.md` Treat that as relative to the active working directory / sandbox workspace. Poirot sandbox file tools are path-aware, so using this relative path keeps the plan with the workspace. If no specific target path is provided by the runtime, create a sensible timestamped filename you

What's inside
Steps it walks through
  1. Core behavior
  2. Output requirements
  3. Save location
  4. Interaction style
  5. Overview
  6. When a Full Implementation Plan Helps
  7. Bite-Sized Task Granularity
  8. Plan Document Structure
  9. Header (Required)
  10. Task Structure
  11. Writing Process
  12. Step 1: Understand Requirements
  13. Step 2: Explore the Codebase
  14. Step 3: Design Approach
Commands it runs
git add [files]
git commit -m "type: description"
More from poirot
All skills →
About this skill
What does the plan skill do?

Plan mode: write markdown plan, no execution.

How do I install it?

Run `npx skills add HezaoHezao/poirot --skill plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From HezaoHezao/poirot, a repository with 139 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going