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 agentmods add skills/zeeshanhanif/agentic-sdlc-kit/implementation-planningnpx skills add zeeshanhanif/agentic-sdlc-kit --skill implementation-planninggit clone --depth 1 https://github.com/zeeshanhanif/agentic-sdlc-kitWrote 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/zeeshanhanif/agentic-sdlc-kit/implementation-planning)<a href="https://agentmods.dev/skills/zeeshanhanif/agentic-sdlc-kit/implementation-planning"><img src="https://agentmods.dev/badge/skills/zeeshanhanif/agentic-sdlc-kit/implementation-planning.svg" alt="Measured on agentmods" 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 | $0.00203 | $0.02477 |
| Opus 5 | $0.00102 | $0.01239 |
| Sonnet 5 | $0.00041 | $0.00495 |
| Haiku 4.5 | $0.00020 | $0.00248 |
Grade A, and why
implementation-planning 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Planning
This skill is the bridge between design and construction. It takes the requirements and design-phase documents and produces a plan a team (or an agent) can execute: what to build, broken into thin vertical slices, in what order, starting where.
Two principles govern it:
- Slice vertically, never horizontally. A unit of work is a thin slice that cuts through every layer — UI, API, domain, data — and delivers something demonstrable. "Build all the tables" or "build all the screens" are horizontal slices: they deliver no value and integrate late. Every feature here spans backend and UI together.
- Make the architecture executable before making it complete. The first thing built is the walking skeleton — the minimal end-to-end path that proves the system runs and deploys — not the easiest feature. Sequence the rest by dependency and risk, de-risking the most uncertain decisions early.
It plans the whole application's breadth but only details what's next. Producing implementation-ready detail for the entire backlog upfront is the waterfall trap; this skill gives full breadth and depth-on-demand.
Inputs
Four upstream documents, each read from its default path unless the user provides another. Each degrades independently — a missing document reduces fidelity, it doesn't block (though the plan is materially weaker without the architecture and ux-foundations, which carry the building blocks and screens that make slices vertical).
- SRS —
docs/srs.md. The source of what a feature is: functional requirements with IDs and priorities (MoSCoW feeds sequencing and the coverage check), plus constraints (team, timeline). Skip tombstoned requirements (statusRemoved/Deprecated) — they must not spawn slices. - Use cases —
docs/use-cases.md. Slices often realize use cases; their flows are prime slice candidates. - Architecture —
docs/architecture.md. Building blocks and their dependencies, risky ADRs, runtime scenarios, deployment view, cross-cutting concepts. - UX foundations —
docs/ux-foundations.md. Surfaces, per-surface screen inventories with SCR IDs, key user flows. (Skip tombstoned screens.)
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.
- 4d ago First seen · 212 lines · 203 tokens per session scan A 5a4abb9c72e6
implementation-planning is a skill published in the GitHub repository zeeshanhanif/agentic-sdlc-kit (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 203 tokens to every session and 2,477 once invoked, about $0.0010 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…