What is SDLC-decompose?

A transition guide that breaks a software design into separate components and creates a directory for each one before coding begins.

Use it to identify components, create their directories, and record them in the project’s coding instructions.

It turns broad design documents into an organized coding structure and checks that the project is ready to leave the design phase.

How pangon/ai-sdlc-framework configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/pangon/ai-sdlc-framework/main/.claude/skills/SDLC-decompose/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/pangon/ai-sdlc-framework

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pangon/ai-sdlc-framework/sdlc-decompose/github.svg)](https://agentmods.dev/skills/pangon/ai-sdlc-framework/sdlc-decompose)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,164 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00011	$0.00866
Sonnet 5.5	$0.00005	$0.00433
Haiku 4.5	$0.00003	$0.00216

Measured 2mo ago against content hash 775c01059468, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/skills/SDLC-decompose/SKILL.md · 165 lines

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-elicit to continue refining specification or /SDLC-design to start the design phase, and do not proceed.
Design — decomposition would cross the Design → Code phase gate. Recommend running /SDLC-validate first: 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 in CLAUDE.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-design to 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-design before 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 to Code when the component directories are created (see Current State Tracking) — not at validation time.

Read the full file on GitHub · 165 lines

Changes

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.

2mo ago First seen · 165 lines · 27 tokens per session scan A 775c01059468

Subscribe to this mod's changes

SDLC-decompose is a skill published in the GitHub repository pangon/ai-sdlc-framework (130 stars, last pushed 2mo 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.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.

Planning

SDLC-decompose next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
SDLC-decomposepangon/ai-sdlc-framework	Skill	130	2mo ago	Apache-2.0	A	27	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

ai-sdlc-framework: Skill for Claude Code