{"id":22055,"plugin_id":"plugins_6aaff56b7f048191894b661584c8e86d","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:17:07.906Z","digest":"8a6fc163db7282d590bf9ac857f2f549ad9bd418b13b8e94fd74354f2b3a2d33","against":null,"payload":{"description":"Use whenever creating, editing, migrating, reorganizing, superseding, archiving, or otherwise changing durable knowledge in the receiving project's knowledge base.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":224}],"name":"knowledge-steward","skill_md_contents":"---\nname: knowledge-steward\ndescription: Use whenever creating, editing, migrating, reorganizing, superseding, archiving, or otherwise changing durable knowledge in the receiving project's knowledge base.\n---\n\n# Knowledge Steward Skill\n\n## Goal\nKeep the receiving project's knowledge current, non-contradictory, traceable, portable across AI agents, and cheap to load. Persist durable project truth in canonical project artifacts instead of relying on chat history or assistant memory.\n\nApply the [receiving-project contract](../../references/project-context.md) when resolving paths, authority, language, and companion skills.\n\n## Trigger\nActivate this skill when a task will change durable KB knowledge, governance, lifecycle, indexes, context, decisions, backlog, or work-state artifacts. Do not activate merely to answer a transient question that causes no durable KB change.\n\n## Core rules\n1. Source of Truth over chat history.\n2. Discussion is not a decision.\n3. Confirmed durable decisions are persisted.\n4. One canonical home per fact; link instead of copying.\n5. Current-state notes contain current truth, not accumulated history.\n6. Preserve historical rationale without preserving contradictions in active context.\n7. Structured/numeric data stays in its designated live source; KB stores meaning, intent, methodology, assumptions, constraints, and accepted decisions.\n8. Prefer updating an existing canonical owner over creating a competing note.\n9. Keep lifecycle state separate from evidence/validation state.\n10. Read the minimum sufficient context; expand only when uncertainty or validation requires it.\n\n## Required workflow\n1. Read the receiving project's available agent guide and current-state artifact if not already loaded; use the equivalents resolved by the project contract.\n2. Identify the task domain and read its available context/index. Missing source-KB filenames do not require creating a new taxonomy.\n3. Determine the canonical owner using the project's Source of Truth or relevant domain index. Use the bundled [authority reference](../../references/source-of-truth.md) for reusable distinctions when no project equivalent exists.\n4. Read only the canonical notes needed for the change.\n5. Classify incoming information as discussion, proposal, decision, temporary decision, open question, deprecated, or superseded.\n6. For a substantial or ambiguous write, consolidate material facts, decisions, trade-offs, temporary assumptions, unresolved blockers, and exact artifacts to be changed before writing. Obtain owner confirmation when required by scope or uncertainty.\n7. Update the smallest canonical artifact set once using the accepted final state.\n8. Add/update a durable decision record only when rationale/history has future value; routine edits do not require one.\n9. When replacing an older decision or document, mark it superseded/deprecated and point to the replacement; remove it from active/default indexes.\n10. Update relevant `_Context.md`, `PROJECT_STATE.md`, active Work state, backlog, and indexes only when their current-state meaning changes.\n11. Read back every changed artifact.\n12. Run deterministic validation/lint when available.\n13. Report what changed and any remaining uncertainty or revisit trigger.\n\n## Context discipline\nDefault loading order is Hot → Warm → Cold.\n\n**Hot:** `AGENTS.md`, `PROJECT_STATE.md`, relevant domain `_Context.md`.\n\n**Warm:** triggered skills, active canonical GDD/technical docs, active decisions, active work state.\n\n**Cold:** legacy GDD, superseded decisions, historical audits, completed work/session artifacts, raw research, `99_Archive/`.\n\nNever scan Cold knowledge by default. Access it only for migration, history/rationale recovery, conflict investigation, evidence verification, or explicit audit.\n\n## Lifecycle and cleanup\nCanonical documents may use `draft`, `review`, `active`, `temporary`, `deprecated`, `superseded`, `archived`. Validation/evidence state is separate. A `review_after` date triggers maintenance review; it does not automatically invalidate a document.\n\nPrefer retain/supersede/archive when historical value exists. Destructive deletion is appropriate only for clear duplicates, empty/stub notes, accidental copies, or intermediate artifacts whose unique evidence/rationale has already been compiled into a canonical owner. Ambiguous destructive deletion requires owner approval.\n\n## Working-state rule\nLong or multi-session work must maintain a compact working-state artifact with: goal, completed work, confirmed decisions, current findings, changed artifacts, open issues/blockers, next step. When work completes, move it out of the active path.\n\n## Language\nFollow the receiving project's writing policy; default to English for canonical knowledge and the user's language for conversation. Preserve exact IDs, code/config identifiers, paths, and localized player-facing strings when relevant.\n\n## Project governance\nThis packaged skill supplies the operational method. The receiving project's agent guide and active governance records own local policy and migration state. If a legacy Knowledge Steward document is still active there, reconcile it against that authority rather than assuming it was retired by installing this plugin.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}