Borrowing it
Nothing to install: this file belongs to pangon/ai-sdlc-framework. 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/pangon/ai-sdlc-framework/main/.claude/skills/SDLC-decompose/SKILL.mdgit clone --depth 1 https://github.com/pangon/ai-sdlc-frameworkWrote 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/pangon/ai-sdlc-framework/sdlc-decompose)<a href="https://agentmods.dev/skills/pangon/ai-sdlc-framework/sdlc-decompose"><img src="https://agentmods.dev/badge/skills/pangon/ai-sdlc-framework/sdlc-decompose.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.1 | $0.00027 | $0.02164 |
| Opus 5 | $0.00014 | $0.01082 |
| Sonnet 5 | $0.00005 | $0.00433 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
SDLC-decompose 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 6d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
You are working at the Design → Code transition, analyzing design artifacts to identify distinct software components, creating per-component directories in the Code phase, and documenting them in the Code phase instructions.
Phase Validation
Before doing anything else, read the **Phase**: field of the ### Current State subsection in CLAUDE.md. Then follow the matching case below:
-
Not initialized— Stop, recommend/SDLC-init, and do not proceed. -
Specification— Stop, recommend/SDLC-elicitto continue refining specification or/SDLC-designto start the design phase, and do not proceed. -
Design— decomposition would cross the Design → Code phase gate. Recommend running/SDLC-validatefirst: gate evaluation trusts the assessment lines in Current State, and validation verifies their freshness against the actual git history. Then evaluate the Design → Code preconditions from the Phase Gates table inCLAUDE.md(using its "How to verify" column), except "Components identified" — that precondition is what this skill establishes — and respond based on the results:- If the documents in the Design Documents Index are not all drafted — design is incomplete. Stop, list which documents are still
Stub, recommend/SDLC-designto continue drafting, and do not proceed. - If the documents are drafted but the completeness-assessment precondition is not met (no assessment, stale, or open Critical findings) — strongly recommend running a Completeness Assessment via
/SDLC-designbefore decomposition. Proceed only if the user explicitly accepts the gaps. - If all evaluated preconditions are met — inform the user of any remaining Important/Minor findings (non-blocking) and ask the user to confirm the advancement to the Code phase (phase gate advancement is an "always ask" action). Proceed with Setup only after confirmation.
In every proceed case, the
**Phase**:field is set toCodewhen the component directories are created (see Current State Tracking) — not at validation time. - If the documents in the Design Documents Index are not all drafted — design is incomplete. Stop, list which documents are still
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.
- 6d ago First seen · 165 lines · 27 tokens per session scan A 775c01059468
SDLC-decompose is a skill published in the GitHub repository pangon/ai-sdlc-framework (126 stars, last pushed 13d ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,164 once invoked, about $0.0001 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-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…
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…
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…