Borrowing it
Nothing to install: this file belongs to OutlitAI/outlit-sdk. 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/OutlitAI/outlit-sdk/main/.agents/skills/writing-plans/SKILL.mdgit clone --depth 1 https://github.com/OutlitAI/outlit-sdkWrote 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/outlitai/outlit-sdk/writing-plans)<a href="https://agentmods.dev/skills/outlitai/outlit-sdk/writing-plans"><img src="https://agentmods.dev/badge/skills/outlitai/outlit-sdk/writing-plans/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/outlitai/outlit-sdk/writing-plans"><img src="https://agentmods.dev/badge/skills/outlitai/outlit-sdk/writing-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.01217 |
| Opus 5 | $0.00018 | $0.00609 |
| Sonnet 5 | $0.00007 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
writing-plans 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 4d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Plans
Complexity Gate
Write an implementation plan when any of these apply:
- The user explicitly asks for a plan.
- An approved design or specification is ready for implementation planning.
- The work changes architecture, cross-component contracts, public APIs, permissions, security, billing, or durable data.
- The work includes migrations, compatibility transitions, rollout sequencing, recovery requirements, or difficult rollback.
- Delivery has multiple meaningful stages, owners, repositories, deployments, or long-running checkpoints.
- Correctness depends on resolving sequencing, interface, or verification choices before implementation.
Use a short internal plan when the outcome is clear and the work has no meaningful sequencing or unresolved contract decisions. A change to behavior or several files does not by itself require a separate plan document. Inspect discoverable details before deciding; preserve the user's requested planning depth.
If high-impact product or architecture decisions remain unresolved, use brainstorming before writing the plan.
Planning Workflow
- Read the approved requirements, relevant repository instructions, implementation surfaces, contracts, tests, and deployment conventions.
- Confirm the goal, scope, non-goals, constraints, and unresolved assumptions. Do not silently turn an implementation plan into a new design.
- Map the files and contracts that create meaningful implementation boundaries.
- Organize work into independently understandable, verifiable outcomes. Fold mechanical setup and documentation into the outcome they support.
- Add cross-cutting verification, rollout, observability, rollback, and completion criteria where relevant.
- Self-review the plan against the source requirements, repository state, and operational risks.
Save the plan to docs/superpowers/plans/YYYY-MM-DD-<topic>.md unless the user or repository specifies another location.
Plan Contract
Start with:
# <Topic> Implementation Plan
**Goal:** <one concrete outcome>
**Source:** <approved spec, issue, or requirements>
**Approach:** <short implementation strategy>
**Scope:** <included work and explicit non-goals>
**Key risks:** <material risks and mitigations>
**Completion:** <observable conditions that mean the work is done>
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.
- 4d ago Changed · +2 lines 7b817d172987
- 10d ago First seen · 122 lines · 37 tokens per session scan A 4ec9862200ff
writing-plans is a skill published in the GitHub repository OutlitAI/outlit-sdk (6 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 1,217 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
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, then fills the gaps with list (filters, sort, a time…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
agreement-setup
Set up a bKash tokenized agreement for repeat charges and check its status.
planfix-api
A Planfix CRM integration for managing tasks and contacts. A CRM is a system for organizing customer and business relationships.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).