ai-sdlc-framework: Skill for Claude Code

.claude/skills/SDLC-status/SKILL.md

SDLC-status is a skill for Claude Code from pangon/ai-sdlc-framework. It costs 50 tokens per session (1,899 once invoked), scanned A, original, Apache-2.0.

A project-wide dashboard that summarizes the state of software development lifecycle work, from requirements and design through code and deployment. SDLC means the stages used to plan, build, verify, and release software.

In plain words
What is it for?
Use it to review phase statuses, count project artifacts, check whether release gates are ready, inspect verification coverage, and identify stale assessments.
Why use it?
It gathers scattered project records into one view of progress, readiness, traceability, and assessment freshness.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is pangon/ai-sdlc-framework's own configuration. It tells Claude Code how to work on ai-sdlc-framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-sdlc-framework configures →

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

agentmods badge for SDLC-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/pangon/ai-sdlc-framework/sdlc-status.svg)](https://agentmods.dev/skills/pangon/ai-sdlc-framework/sdlc-status)
Your own site
<a href="https://agentmods.dev/skills/pangon/ai-sdlc-framework/sdlc-status"><img src="https://agentmods.dev/badge/skills/pangon/ai-sdlc-framework/sdlc-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,899 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01899
Opus 5 $0.00025 $0.00949
Sonnet 5 $0.00010 $0.00380
Haiku 4.5 $0.00005 $0.00190

Measured 7d ago against content hash 0331f680e80d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

SDLC-status 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 7d 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-status/SKILL.md · 182 lines

How it starts

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

Instructions

You are generating a comprehensive status report for the entire SDLC project.

Setup

  1. Read root instructions: CLAUDE.md — extract Project Overview and Current State.
  2. Read all four phase instruction files:
    • 1-spec/CLAUDE.spec.md
    • 2-design/CLAUDE.design.md
    • 3-code/CLAUDE.code.md
    • 4-deploy/CLAUDE.deploy.md
  3. Read 1-spec/stakeholders.md.
  4. Read 3-code/tasks.md (if it exists and has content), and the verification indexes that exist — 3-code/verification.md and 3-code/<component>/verification.md.
  5. Scan all artifact indexes in the phase files — follow File column links only when needed to resolve ambiguous statuses.
  6. List files in decisions/ to count decisions (exclude PROCEDURES.md, templates, and .history.md files; read .history.md only when the corresponding active record shows Deprecated or Superseded status).
  7. List component directories in 3-code/ (directories containing a CLAUDE.md file).
  8. List files in 4-deploy/infrastructure/, 4-deploy/scripts/, 4-deploy/runbooks/ to count deployment artifacts (exclude templates and placeholder README.md files).

Phase Validation

Before generating the report, read the **Phase**: field of the ### Current State subsection in CLAUDE.md:

  • If it is Not initialized (or the Project Overview still contains placeholder text) → report the project as Not Initialized and recommend /SDLC-init.
  • Otherwise → proceed with full report.

Report Structure

Present the report as a single markdown document with these sections.


Project Overview
  • Project: name/description (from CLAUDE.md Project Overview)
  • Date: current date
  • Current State: reproduce the Current State section from CLAUDE.md verbatim — this is the authoritative project-level summary maintained by all skills

Phase 1: Specification

Stakeholders: N defined (list names and influence levels in a compact line)

Artifacts:

Artifact Total Draft Approved Implemented Deprecated
Goals
User Stories
Requirements

Read the full file on GitHub · 182 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.

  1. 7d ago First seen · 182 lines · 50 tokens per session scan A 0331f680e80d

Subscribe to this mod's changes

SDLC-status is a skill published in the GitHub repository pangon/ai-sdlc-framework (126 stars, last pushed 14d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,899 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens