software-lifecycle

Name: software-lifecycle
Author: inkeep

3.1kstars191forks

How to install software-lifecycle?

inkeep/open-knowledge/software-lifecycle

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

Installs into the current project.

Summary

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. Carries the doc lifecycle, status flows, and per-folder agent behaviors so that guidance does no

Files · 1

View on GitHub

SKILL.md

1	# Software Lifecycle pack — how to work here
2
3	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.
4
5	> This is pack guidance. The platform `open-knowledge` skill still governs every markdown operation.
6
7	## The flow
8
9	```
10	proposals/ in-flight RFC-shape design proposals
11	↓ accepted
12	decisions/ frozen ADRs (the record of what was decided)
13	↓ derived
14	specs/ implementation specs for accepted proposals
15	↓ when things break
16	postmortems/ blameless incident write-ups
17	guides/ how-to / onboarding / runbooks (referenced throughout)
18	```
19
20	## Per-folder rules + agent behaviors
21
22	`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.
23
24	`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.
25
26	`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.
27
28	`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.
29
30	`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.
31
32	## Templates
33
34	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.

People who liked this also viewed

6 picks

Type

software-lifecycle

3.1kstars191forks

View on GitHub

How to install software-lifecycle?

inkeep/open-knowledge/software-lifecycle

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Software Lifecycle pack — how to work here
2
3	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.
4
5	> This is pack guidance. The platform `open-knowledge` skill still governs every markdown operation.
6
7	## The flow
8
9	```
10	proposals/ in-flight RFC-shape design proposals
11	↓ accepted
12	decisions/ frozen ADRs (the record of what was decided)
13	↓ derived
14	specs/ implementation specs for accepted proposals
15	↓ when things break
16	postmortems/ blameless incident write-ups
17	guides/ how-to / onboarding / runbooks (referenced throughout)
18	```
19
20	## Per-folder rules + agent behaviors
21
22	`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.
23
24	`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.
25
26	`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.
27
28	`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.
29
30	`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.
31
32	## Templates
33
34	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.

People who liked this also viewed

6 picks

Type