SkillAgentSearch skills...

software-lifecycle

How to work in a Software Lifecycle project (the `software-lifecycle` starter pack): proposals → decisions → specs → postmortems, plus guides. Read when the project has these folders, or when asked how this project is organized.

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Automation

Supported Platforms

Zed

Our assessment of software-lifecycle

software-lifecycle scores 86/100 on our quality scale, 1784th of 2,790 Automation skills we index.

Its SKILL.md is 4.6 KB long, split into 5 sections with 1 code example: a solid amount of guidance for an agent.

With 4,309 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so software-lifecycle is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under GPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

software-lifecycle compared with similar skills

All 4 of these similar skills score higher than software-lifecycle; compare them before choosing.

SkillScoreStarsUpdatedFormat
software-lifecycle (this skill)by inkeep864.3k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install software-lifecycle?
Run npx skills add inkeep/open-knowledge --skill software-lifecycle. The install tabs above show the steps for each supported agent.
Which AI agents does software-lifecycle work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is software-lifecycle safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is GPL-3.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is software-lifecycle still maintained?
The repository was last updated about 2 months ago, so software-lifecycle is actively maintained.

name: software-lifecycle description: "How to work in a Software Lifecycle project (the software-lifecycle starter pack): proposals → decisions → specs → postmortems, plus guides. Read when the project has these folders, or when asked how this project is organized. Carries the doc lifecycle, status flows, and per-folder agent behaviors so that guidance does not live inside template bodies or folder descriptions. The five workflows — frame a proposal, write a spec, record a decision, write a postmortem, review a design — each ship as their own sibling skill in this pack. Complements the platform open-knowledge skill; does not replace it." compatibility: "Any agent host with the OpenKnowledge MCP server configured. Installed project-local by ok seed --pack software-lifecycle." metadata: pack: "software-lifecycle" author: "Inkeep" repository: "https://github.com/inkeep/open-knowledge-skills"

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.

postmortems/ — Blameless incident write-ups, one file per incident (YYYY-MM-DD-name.md): Summary / Timeline / Root cause / What went well / Action items (Google SRE shape). Agent: surface a Related: block linking prior postmortems that share subsystems.

guides/ — How-to guides, onboarding docs, and service-bound runbooks (Diátaxis how-to). Ships guide, onboarding-guide, and runbook templates. Carries last_verified so stale guides surface in periodic reviews. Agent: when a postmortem is published, scan its action items for guide-shaped follow-ups and stub a guide pre-filled with the symptom and timeline excerpt.

The five workflows

Authoring in this project is procedural, not conventional. Each workflow ships as its own skill so it loads only when the work calls for it — reach for the one that matches the task rather than writing into a folder from scratch.

| Workflow | Sibling skill | When | | --- | --- | --- | | Frame a proposal | /frame-a-proposal | A change needs designing and arguing before anyone builds it. | | Write a spec | /write-a-spec | An accepted proposal needs scoping into an implementable spec. | | Record a decision | /record-a-decision | A decision was actually made and needs its context and consequences preserved. | | Write a postmortem | /write-a-postmortem | An incident happened and the team needs a blameless write-up. | | Review a design | /review-a-design | An existing proposal, spec, or decision needs pressure-testing for soundness. |

Templates

Create docs with write({ document: { path, template: "<name>" } }). Templates carry only structure (headings + frontmatter scaffold); what each section is for is described above, not repeated in the document body.

Related Skills

View on GitHub
GitHub Stars4.3k
CategoryAutomation
Updated1mo ago
Forks285

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions