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.
npx skills add dremonkey/agents-and-skills --skill plan-requirement-docgit clone --depth 1 https://github.com/dremonkey/agents-and-skillsWrote 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/dremonkey/agents-and-skills/plan-requirement-doc)<a href="https://agentmods.dev/skills/dremonkey/agents-and-skills/plan-requirement-doc"><img src="https://agentmods.dev/badge/skills/dremonkey/agents-and-skills/plan-requirement-doc/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/dremonkey/agents-and-skills/plan-requirement-doc"><img src="https://agentmods.dev/badge/skills/dremonkey/agents-and-skills/plan-requirement-doc.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.00048 | $0.01785 |
| Opus 5 | $0.00024 | $0.00892 |
| Sonnet 5 | $0.00010 | $0.00357 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
plan-requirement-doc 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CEO Product Review Mode
Purpose
Use this skill to ensure a product or feature plan is strategically correct before detailed implementation planning.
This is a product-definition review, not an engineering deep-dive.
Artifact Contract
Before creating artifacts, assess the size and strategic weight of the initiative:
Large initiatives (new subsystem, new user-facing capability, multi-EPIC effort)
- Vision doc at
tasks/<EPIC_NAME>/VISION.md(ICP, problem, value prop, positioning, launch narrative, non-goals). - PRD doc(s) at
tasks/<EPIC_NAME>/PRD.<TOPIC>.md(scope, requirements, user flows, acceptance criteria, success metrics). - Update top-level
VISION.md— add or revise a short entry capturing the initiative's intent. Keep it high-level: what capability is being added and why, not implementation details. This file is the living record of product direction.
Small-to-medium features (new component in existing system, single-EPIC scope, optimization)
- PRD at
tasks/<EPIC_NAME>/PRD.md(scope, requirements, acceptance criteria, success metrics). - No per-epic vision doc — the feature is part of an existing system's vision, not its own.
Rule of thumb: if the feature is described in terms of an existing system ("add X to Y", "optimize Z pipeline"), it's small-to-medium. If it introduces a new user-facing capability or a new architectural boundary, it's large.
These artifacts are inputs to plan-tech-spec and plan-eng-tasks.
Core Principle
A plan is only ready when all of these are clear and coherent:
- ICP (who exactly this is for)
- User problem statement (what pain, in what context, why now)
- Value proposition (what outcome improves, and why this is better than alternatives)
- Positioning (how this should be framed in the market and in-product)
- Success metrics (how we know it worked)
- Launch narrative (how we explain and roll this out)
If any of these are weak, call it out directly and drive resolution.
What ships with it
1 file 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.
- 9d ago First seen · 207 lines · 48 tokens per session scan A f962838f2ba5
plan-requirement-doc is a skill published in the GitHub repository dremonkey/agents-and-skills (2 stars, last pushed 26d ago), licensed MIT. It adds 48 tokens to every session and 1,785 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-08-31.
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…