Borrowing it
Nothing to install: this file belongs to hachej/boring-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hachej/boring-ui/main/.agents/skill-references/plan/jeffrey-emanuel-planning-workflow/SKILL.mdgit clone --depth 1 https://github.com/hachej/boring-uiWrote 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.
[](https://agentmods.dev/skills/hachej/boring-ui/jeffrey-emanuel-planning-workflow)<a href="https://agentmods.dev/skills/hachej/boring-ui/jeffrey-emanuel-planning-workflow"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/jeffrey-emanuel-planning-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hachej/boring-ui/jeffrey-emanuel-planning-workflow"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/jeffrey-emanuel-planning-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00043 | $0.01970 |
| Opus 5 | $0.00022 | $0.00985 |
| Sonnet 5 | $0.00009 | $0.00394 |
| Haiku 4.5 | $0.00004 | $0.00197 |
Grade C, and why
planning-workflow scanned grade C with 1 finding 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 10d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
name: planning-workflow description: >- Comprehensive markdown planning methodology for software projects. Use when starting a new project, creating implementation plans, or refining architecture How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Workflow — The Foundation of Agentic Development
Core Philosophy: "Planning tokens are a lot fewer and cheaper than implementation tokens."
The models are far smarter when reasoning about a detailed plan that fits within their context window. This is the key insight behind spending 80%+ of time on planning.
Outcome — When This Skill Has Delivered
You have a usable plan when all of the following hold:
- The plan is self-contained: a fresh agent who has never seen the project can read it and start implementing without asking the human for clarification.
- It is dependency-aware: every non-trivial task names what blocks it and what it unblocks, so the work decomposes cleanly into a beads graph.
- It is justified: every architectural choice and every non-obvious feature has at least one sentence on why, not just what — future agents need the rationale to make consistent local decisions.
- It has survived at least 4 review rounds by a strong reasoning model (GPT Pro Extended Reasoning is the proven choice) and reached steady-state — i.e., the most recent round produces marginal rather than structural revisions.
- It has been converted to beads with the dependency graph intact, so implementation agents can pick up ready work via
br ready --jsonwithout re-reading the plan.
You have NOT delivered if any of these is true: the plan is < ~1,500 lines for a non-trivial project (under-specified); the plan is > ~10,000 lines with no decomposition (impossible to act on); the human is still being asked "what should this do?" mid-implementation (planning was abandoned, not completed); beads exist but have no dependency edges (the plan's structure was lost in conversion).
When NOT to Use This Skill
Reach for something else if:
- The change is small and local (one bug fix, one file, < ~200 LOC) → plan in chat or as a one-line TaskCreate; the planning overhead exceeds the implementation cost.
- You are doing pure research (investigating an unknown codebase, prototyping an idea) → use
codebase-archaeologyoridea-wizardfirst; planning is for execution, not discovery. - The architecture is dictated (you are porting an existing system, following a spec, or implementing a well-defined RFC) → use
porting-to-rustortesting-conformance-harnesses; the plan is the spec itself. - You're under a hard deadline that doesn't permit 80%-on-planning (live incident, hotfix, security patch) → ship the fix, then retrofit the plan if the area needs further work.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 155 lines · 43 tokens per session scan C bfd6992205e0
planning-workflow is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,970 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…