What is SDLC-implementation-plan?

A planning workflow that turns software design documents into an ordered list of implementation tasks. It groups short tasks into phases, with each phase ending in a system that can be tested or deployed.

Use it after breaking the design into components and before coding to create or fill in the project's implementation plan.

It gives coding work a clear sequence and checks that the project is ready to enter implementation. It also prevents planning from starting before the required design work is complete.

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-implementation-plan/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-implementation-plan/github.svg)](https://agentmods.dev/skills/pangon/ai-sdlc-framework/sdlc-implementation-plan)

Your own site

<a href="https://agentmods.dev/skills/pangon/ai-sdlc-framework/sdlc-implementation-plan"><img src="https://agentmods.dev/badge/skills/pangon/ai-sdlc-framework/sdlc-implementation-plan/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-implementation-plan"><img src="https://agentmods.dev/badge/skills/pangon/ai-sdlc-framework/sdlc-implementation-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,384 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.00049	$0.03384
Opus 5.5	$0.00020	$0.01354
Sonnet 5.5	$0.00010	$0.00677
Haiku 4.5	$0.00005	$0.00338

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

Security

Grade A, and why

SDLC-implementation-plan 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-implementation-plan/SKILL.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Instructions

You are working in the Code phase. You are creating an implementation plan — a phased sequence of short development tasks that, when executed in order, build the project incrementally from nothing to full feature set. Each phase ends with a system that can be deployed or at least tested end-to-end, even if not feature-complete.

The plan populates 3-code/tasks.md with tasks and an Execution Plan that groups them into ordered phases.

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 specifications or /SDLC-design to start the design phase, and do not proceed.
Design — components have not been identified yet. Stop, recommend /SDLC-decompose first, and do not proceed.
Code with no tasks yet (3-code/tasks.md contains only the template) — this is the expected entry point. Evaluate prerequisites:
- (a) All design documents are drafted and components are identified — re-verify the two corresponding Design → Code preconditions via the "How to verify" column of the Phase Gates table in CLAUDE.md (the gate was already crossed, but the state may have drifted)
- (b) 3-code/tasks.md has no tasks yet (only the template)
Then:
- If (a) is not met — Stop, explain what is missing.
- If (b) is not met (tasks already exist) — Warn that running this skill will replace the pending task entries (Todo/Blocked) and the current/future phases of the Execution Plan; completed work is preserved (see Re-planning in Workflow step 2). Proceed only on explicit user confirmation.
- If all met — proceed with Setup.
Code with tasks already in progress or done — Warn strongly that re-planning may invalidate in-progress work; completed tasks are preserved (see Re-planning in Workflow step 2). Proceed only on explicit user confirmation.

Read the full file on GitHub · 239 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 · 239 lines · 49 tokens per session scan A 38f191ca7f89

Subscribe to this mod's changes

SDLC-implementation-plan is a skill published in the GitHub repository pangon/ai-sdlc-framework (130 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 3,384 once invoked, about $0.0002 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-implementation-plan next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
SDLC-implementation-planpangon/ai-sdlc-framework	Skill	130	2mo ago	Apache-2.0	A	49	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