plan-execution-skill

plan-execution-skill is a skill for OpenCode from darellchua2/opencode-config-template. It costs 36 tokens per session (3,515 once invoked), scanned A, original, Apache-2.0.

A workflow that reads a PLAN.md file and carries out its phases in order, tracking progress as work is completed. PLAN.md is a text file that lists development tasks and their acceptance criteria.

In plain words
What is it for?
Use it to find the relevant plan, run its tasks sequentially, update progress after each phase, and commit the recorded progress.
Why use it?
It helps execute a multi-step implementation consistently without losing track of completed work or the next phase.

Skill for OpenCode

Written for OpenCode: installed under .opencode/. Also seen: mentions subagents; positional $N argument; mentions OpenCode.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/darellchua2/opencode-config-template/plan-execution-skill
Any agent
npx skills add darellchua2/opencode-config-template --skill plan-execution-skill
Clone the repo
git clone --depth 1 https://github.com/darellchua2/opencode-config-template

Made for: OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plan-execution-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/plan-execution-skill.svg)](https://agentmods.dev/skills/darellchua2/opencode-config-template/plan-execution-skill)
Your own site
<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/plan-execution-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/plan-execution-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,515 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.03515
Opus 5 $0.00018 $0.01758
Sonnet 5 $0.00007 $0.00703
Haiku 4.5 $0.00004 $0.00351

Measured 2d ago against content hash 8fea3764240f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

plan-execution-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

opencode_app/.opencode/skills/plan-execution-skill/SKILL.md · 475 lines

How it starts

The opening of the file, as written. The whole thing — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.

What I do

I provide automatic PLAN.md execution with integrated progress tracking:

  1. Detect Current PLAN: Extract branch name and find matching PLAN file
  2. Parse Plan Structure: Read phases, tasks, and acceptance criteria
  3. Execute Phases: Work through plan tasks in order
  4. Auto-Update Progress: Invoke plan-updater after each phase completes
  5. Track Completion: Mark tasks complete and commit progress automatically

When to use me

Use this skill when:

  • You say "implement the plan" or "execute the plan"
  • Working on a branch with a PLAN.md file
  • Want automatic progress tracking during development
  • Need systematic phase-by-phase execution

Trigger phrases:

  • "implement the plan"
  • "execute the plan"
  • "work on the plan"
  • "continue with the plan"
  • "resume plan execution"

Subagents That Should Use This Skill

Subagent When to Invoke
Any subagent When user says "implement the plan"

Core Workflow

Step 0: Verbatim playbook discipline (anti-drift)

Before executing, transcribe the matched PLAN's steps into the session todolist VERBATIM, ahead of any task-specific todos:

  • Copy plan steps word-for-word — no paraphrasing, reordering, or merging during transcription.
  • A step you decide to skip STAYS in the todolist, annotated skip: <reason>. Silently deleting it is drift.
  • Task-specific todos are appended AFTER the transcribed plan steps, never interleaved.
  • At each phase boundary, diff the todolist against the PLAN file: every deviation must be a visible skip: entry or a completed step.

Step 1: Detect Current PLAN

Identify the PLAN file for the current branch:

BRANCH_NAME=$(git branch --show-current)

# GitHub pattern: GIT-123
if [[ "$BRANCH_NAME" =~ ^GIT-([0-9]+)$ ]]; then
  ISSUE_NUM="${BASH_REMATCH[1]}"
  PLAN_FILE="PLANS/PLAN-GIT-${ISSUE_NUM}.md"
  PLAN_TYPE="github"
fi

# JIRA pattern: PROJECT-123
if [[ "$BRANCH_NAME" =~ ^([A-Z]+-[0-9]+)$ ]]; then
  PLAN_ID="${BASH_REMATCH[1]}"
  PLAN_FILE="PLANS/PLAN-${PLAN_ID}.md"
  PLAN_TYPE="jira"
fi

if [ ! -f "$PLAN_FILE" ]; then
  echo "No PLAN file found for branch: $BRANCH_NAME"
  echo "Expected: $PLAN_FILE"
  exit 1
fi

echo "Found PLAN: $PLAN_FILE"

Read the full file on GitHub · 475 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 475 lines · 36 tokens per session scan A 8fea3764240f

Subscribe to this mod's changes

plan-execution-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 36 tokens to every session and 3,515 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

git-ship

自动化 Git 工作流一键发布助手,执行完整的「ship」流程: 基于最新 main 切新分支 → commit → 推送 → 创建 PR → squash merge → 回 main。 调用 ship 本身就是对完整流程的授权;自动推断分支名、commit message 和 PR 内容, 并主动解决 Git 冲突、测试、lint、类型检查、构建和 CI 失败,持续修复和重试, 直到改动成功合并。不要因可自行修复的失败暂停,只在认证、权限、仓库保护等 无法由当前环境解决的外部阻塞出现时请求用户介入。 仅在用户明确表达「ship」意图时触发,例如: 直接说「ship」「/ship」「git ship」 明确要求完整走完 git…

oil-oil/git-ship · 273 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens