What is software-lifecycle?

A documentation workflow for software projects that moves from proposals to decisions, implementation specifications, and incident postmortems, with guides for procedures.

Use it to organize proposals, record architecture decisions, write specifications, document incidents, and maintain onboarding or operational guides.

It gives engineering documents a clear purpose and progression, so accepted ideas can become buildable plans and failures can inform future work.

software-lifecycle — Skill for Claude Code by inkeep

Install

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.

Any agent

npx skills add inkeep/open-knowledge-skills --skill software-lifecycle

Clone the repo

git clone --depth 1 https://github.com/inkeep/open-knowledge-skills

Made for: Claude Code.

Or install software-lifecycle, the plugin that ships this one along with the rest of its 6 skills.

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/inkeep/open-knowledge-skills/software-lifecycle/github.svg)](https://agentmods.dev/skills/inkeep/open-knowledge-skills/software-lifecycle)

Your own site

<a href="https://agentmods.dev/skills/inkeep/open-knowledge-skills/software-lifecycle"><img src="https://agentmods.dev/badge/skills/inkeep/open-knowledge-skills/software-lifecycle/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/inkeep/open-knowledge-skills/software-lifecycle"><img src="https://agentmods.dev/badge/skills/inkeep/open-knowledge-skills/software-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,091 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.00132	$0.01091
Opus 5.5	$0.00053	$0.00436
Sonnet 5.5	$0.00026	$0.00218
Haiku 4.5	$0.00013	$0.00109

Measured 26d ago against content hash e49d561c6d47, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

software-lifecycle 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 26d 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.

skills/starter-packs/software-lifecycle/software-lifecycle/SKILL.md · 56 lines

How it starts

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

Software Lifecycle pack — how to work here

This project holds the doc lifecycle for an engineering team or OSS project. The flow is proposals → decisions → specs → postmortems, with guides as the how-to bucket. This skill holds the workflow so templates and folder descriptions stay clean.

This skill is pack guidance. The platform /open-knowledge skill (read/write/preview/linking/grounding rules) still governs every markdown operation — this layers the lifecycle conventions on top.

The flow

proposals/    in-flight RFC-shape design proposals
   ↓ accepted
decisions/    frozen ADRs (the record of what was decided)
   ↓ derived
specs/        implementation specs for accepted proposals
   ↓ when things break
postmortems/  blameless incident write-ups
guides/       how-to / onboarding / runbooks (referenced throughout)

Per-folder rules + agent behaviors

proposals/ — One file per proposal (0001-feature-name.md). Status flows draft → fcp → accepted/rejected. An accepted proposal graduates to a record in decisions/. Shape: Motivation / Design / Drawbacks / Alternatives / Unresolved questions. Agent: when a proposal sits at status: draft more than 14 days, surface it for the author to advance, park, or close.

decisions/ — Architecture Decision Records (MADR / Nygard shape). Frozen once accepted. One file per decision (NNNN-title.md); status proposed/accepted/deprecated/superseded. A new decision that supersedes an older one links back via Supersedes:. Agent: on a new decision, scan existing records touching the same subsystem and surface Supersedes: candidates before commit.

specs/ — Implementation specs derived from accepted proposals. Prefer the github/spec-kit shape: one folder per spec (specs/NNN-name/) with spec.md + plan.md + tasks.md (the pack ships all three templates). References the parent proposal. Agent: when a spec moves to status: shipped, suggest a postmortem template if the owner reports an incident in the spec's subsystem.

Read the full file on GitHub · 56 lines

Files

What ships with it

1 file 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.

plugin.json 346 B

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.

26d ago Changed e49d561c6d47
2mo ago First seen · 56 lines · 132 tokens per session scan A b8f9d5925024

Subscribe to this mod's changes

software-lifecycle is a skill published in the GitHub repository inkeep/open-knowledge-skills (17 stars, last pushed 13d ago), licensed MIT. It adds 132 tokens to every session and 1,091 once invoked, about $0.0005 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-31.

Planning Writing and docs agent-skills ai-agents mcp open-knowledge skills

software-lifecycle next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
software-lifecycleinkeep/open-knowledge-skills	Skill	17	13d ago	MIT	A	132	Claude Code
claude-md-improveranthropics/claude-plugins-official	Skill	47k	today	Apache-2.0	A	82	Claude Code
agent-platform-model-registrygoogle/skills	Skill	24k	today	Apache-2.0	A	60	Claude Code, Codex
google-cloud-solution-agentic-analytics-spark-knowledge-cataloggoogle/skills	Skill	24k	today	Apache-2.0	A	132	Claude Code, Codex
glance-canonical-layoutsandroid/skills	Skill	10k	today	Apache-2.0	A	56	Claude Code
viteantfu/skills	Skill	6.1k	5d ago	MIT	A	49	Claude Code, Codex
twitter-readerhimself65/finance-skills	Skill	3.5k	6d ago	MIT	A	110	Claude Code