Profile My skills Saved Collections Edit profile Submit a skill

Project Knowledge Capture

Capture durable project knowledge after implementation: goals, context, key entrypoints, CodeGraph findings, decisions, verification results, review conclusions, and follow-up notes into docs/knowledge — so the next developer (or the next session) can answer 'why was this done' and 'what to be careful about' in minutes, not days. Use when development completes and project knowledge should be preserved without secrets or process noise. Do NOT use for: chat summaries, raw session transcripts, secrets, customer data, or production data.

liyown e3c4834 4 files · 5.8 KB Updated
Coding & Dev Tools

File contents

Project Knowledge Capture

Capture stable project knowledge after a development task. This is not a chat transcript and not a changelog.

Required Loading

Always load prompts/capture.md.

Contract

  • Default target directory: docs/knowledge/.
  • Create or update docs/knowledge/index.md.
  • Create docs/knowledge/YYYY-MM-DD-<goal-slug>.md for the task note.
  • Record durable knowledge only: context, entrypoints, decisions, constraints, tests, review conclusions.
  • Preserve CodeGraph provenance. If context was gathered by rg/file inspection (no CodeGraph), keep the exact line CodeGraph unavailable; context was gathered by rg/file inspection. in the CodeGraph Findings section, with the specific rg queries and files consulted on the next line.
  • Do not write secrets, tokens, customer data, production data, sensitive logs, or speculative claims.

liyown/superpower-enterprise/tree/main/skills/project-knowledge-capture commit e3c483493e

Browse category

Frequently asked questions

npx skillmds@latest add liyown/project-knowledge-capture