project-knowledge-steward

Route durable project knowledge to canonical docs, ADRs, Skills, and plans while removing duplication.

1|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/getyak/talent-signal --skill project-knowledge-steward-getyak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-knowledge-steward
Source: https://github.com/getyak/talent-signal/tree/main/.agents/skills/project-knowledge-steward
Command: npx skills add https://github.com/getyak/talent-signal --skill project-knowledge-steward-getyak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running agent-assisted projects accumulate scattered documentation, duplicated explanations, and stale implementation detail that degrade future agent effectiveness. This Skill classifies each new learning and routes it to the single authoritative surface—AGENTS.md, a canonical doc, an ADR, a Skill, a plan, research, tests, or code—so project knowledge stays lean and retrievable. ## Core Features & Use Cases - Knowledge Classification: Categorizes each insight by type (invariant, decision rationale, repeatable method, active state, external evidence, deterministic behavior) and assigns the narrowest correct destination. - Deduplication and Pruning: Searches for existing statements and contradictions, replaces duplicate explanations with links, and removes stale implementation detail from foundational docs. - Wiki Workflow Support: Manages the _index/ inbox-to-pages pipeline, respects wiki-generated markers, and runs pnpm wiki:test and pnpm docs:check after changes. - Use Case: After a user corrects the agent for the third time about a deployment constraint, use this Skill to fix the instance, identify the failure class, and record the durable prevention in AGENTS.md or an ADR instead of scattering notes across docs. ## Quick Start Use the project-knowledge-steward skill to decide where this retrospective finding belongs and update the canonical documentation accordingly.

Frequently Asked Questions about project-knowledge-steward

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide where new project documentation should live?▼

Classify the insight first: always-on invariants go to AGENTS.md, stable judgments to one canonical doc, decision rationale to an ADR, repeatable methods to a Skill, and active state to a plan. Choose the narrowest surface that can retrieve or enforce the knowledge.

How to keep agent context files from becoming bloated?▼

Remove endpoint inventories, function signatures, and configuration snapshots from foundational docs, keeping only purpose, decision, boundary, and consequence. Replace duplicate explanations with links and store detail in research or operational artifacts retrieved on demand.

When should I create an ADR instead of updating existing docs?▼

Create an ADR when capturing the rationale for one consequential choice that future work must understand. Stable product or architecture judgments belong in a single canonical document, while an ADR preserves why a specific decision was made.

Can I edit wiki-generated pages directly?▼

No, pages with a wiki-generated marker must never be hand-edited. Edit the source in the _index/ directories, then run pnpm wiki:build to compile, followed by pnpm wiki:test and pnpm docs:check to verify.

When should a repeated correction become a permanent rule?▼

Only after a clear failure class emerges from repeated evidence, not one ambiguous event. Prefer an ADR, test, or temporary note first, and encode rigid rules only when safety, privacy, authorization, or data integrity justifies them.