How do I install the Docs skill?

Run npx skillmds@latest add lantisprime/docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

lantisprime (@lantisprime) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docs by lantisprime — Agent Skill

Name: Docs
Author: lantisprime

Docs

Use this skill at the end of any phase that changed SDLC artifacts to update the SDLC documentation tree — the artifact index, requirements traceability matrix, architecture manifest, changelog, and any user-facing docs affected by the change. Also trigger when the user says "update docs", "refresh the index", "regenerate the traceability matrix", or after a deployment completes.

lantisprime 63ee0bf 2.6 KB Updated Sep 17, 2026

File contents

Docs (Phase 8, cross-cutting)

Keep the SDLC artifact tree navigable and the traceability matrix current.

When to run

After any phase signs a gate and the gate recorded artifact changes
After a deployment completes
On explicit request

Step 1 — Update the artifact index

Refresh .claude/sdlc/docs/index.md:

List every artifact by phase with its path and last-modified date
Flag any orphans (requirements with no test case, test cases with no implementation, etc.)

Step 2 — Traceability matrix

Refresh .claude/sdlc/docs/traceability.md:

REQ ID	Tech Spec	Test Case(s)	Code (files/fns)	Test Run	Deploy
REQ-001	specs/order.md	TC-001,002	order.py::submit	2026-...	prod

Any empty cell is a visible gap. The human decides whether to fill or waive.

Step 3 — Changelog

Append to CHANGELOG.md in the consuming repo root (not in .claude/sdlc/), following the project's convention (Keep a Changelog / Conventional Commits style).

Step 4 — Architecture manifest

Refresh .claude/sdlc/architecture/manifest.json:

File list with version and last-modified
Cross-references (which spec refers to which architecture doc)

Step 5 — User-facing docs

If the change affects user-facing APIs, CLI flags, config keys, or UI flows, update the corresponding user docs. Don't leave this for later.

What this skill must NOT do

Do not fabricate traceability. If a REQ has no test, say so in the matrix.
Do not quietly "clean up" other docs while updating — follow surgical-edit discipline even here.

References

docs/SDLC.md Docs

Next step hint

After updating the artifact index, pipe the next_suggestions conditions to skills/_shared/next-hint.sh and print any output:

printf '%s\n' \
  'support_gate_signed|task complete — run /start or /plan to begin the next work item' \
  'always|docs updated — continue with the current phase or run /start for the next work item' \
  | bash skills/_shared/next-hint.sh

Print any output verbatim. If the script outputs nothing, add nothing.

---name: docsdescription: Use this skill at the end of any phase that changed SDLC artifacts to update the SDLC documentation tree — the artifact index, requirements traceability matrix, architecture manifest, changelog, and any user-facing docs affected by the change. Also trigger when the user says "update docs", "refresh the index", "regenerate the traceability matrix", or after a deployment completes.---# Docs (Phase 8, cross-cutting)Keep the SDLC artifact tree navigable and the traceability matrix current.## When to run- After any phase signs a gate and the gate recorded artifact changes- After a deployment completes- On explicit request## Step 1 — Update the artifact indexRefresh `.claude/sdlc/docs/index.md`:- List every artifact by phase with its path and last-modified date- Flag any orphans (requirements with no test case, test cases with no implementation, etc.)## Step 2 — Traceability matrixRefresh `.claude/sdlc/docs/traceability.md`:| REQ ID | Tech Spec | Test Case(s) | Code (files/fns) | Test Run | Deploy ||---------|------------------|--------------|-------------------|----------|--------|| REQ-001 | specs/order.md | TC-001,002 | order.py::submit | 2026-... | prod |Any empty cell is a visible gap. The human decides whether to fill or waive.## Step 3 — ChangelogAppend to `CHANGELOG.md` in the consuming repo root (not in `.claude/sdlc/`), following the project's convention (Keep a Changelog / Conventional Commits style).## Step 4 — Architecture manifestRefresh `.claude/sdlc/architecture/manifest.json`:- File list with version and last-modified- Cross-references (which spec refers to which architecture doc)## Step 5 — User-facing docsIf the change affects user-facing APIs, CLI flags, config keys, or UI flows, update the corresponding user docs. Don't leave this for later.## What this skill must NOT do- Do not fabricate traceability. If a REQ has no test, say so in the matrix.- Do not quietly "clean up" other docs while updating — follow surgical-edit discipline even here.## References- `docs/SDLC.md` Docs## Next step hintAfter updating the artifact index, pipe the `next_suggestions` conditions to `skills/_shared/next-hint.sh` and print any output:```bashprintf '%s\n' \ 'support_gate_signed|task complete — run /start or /plan to begin the next work item' \ 'always|docs updated — continue with the current phase or run /start for the next work item' \ | bash skills/_shared/next-hint.sh```Print any output verbatim. If the script outputs nothing, add nothing.

Frequently asked questions