What problem does it solve? Agents and developers lose time guessing where authoritative project knowledge lives, duplicating facts across root files, task pages, and scattered notes. This Skill defines a single source-of-truth layout so durable knowledge is written once and discovered reliably. ## Core Features & Use Cases - Source-of-truth split: Assigns canonical ownership for glossaries, system maps, area summaries, dependency graphs, feature contracts, runbooks, and component contexts under docs/resources/. - Conventions and templates: Ships ADR, runbook, local-bindings, area-sources, and inbox-batch templates plus references for runbook, ADR, and generated-artifact naming rules. - Knowledge lifecycle lanes: Separates raw inbox staging, curated digests, rerunnable timestamped reports, and durable attachments so unstable material never pollutes canonical docs. - Use Case: After a teammate call, drop the transcript into docs/resources/_inbox/, distill it into a digest, promote stable facts into the area summary, and record provenance in sources.md. ## Quick Start Ask the agent to decide where a new architecture decision or operational procedure belongs and have it create the ADR or runbook using this skill's conventions.
