knowledge

Captures session learnings, audits documentation indexes, and reconciles living component behavior specs.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/FerEscobarDev/Specture --skill knowledge-ferescobardev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge
Source: https://github.com/FerEscobarDev/Specture/tree/main/skills/knowledge
Command: npx skills add https://github.com/FerEscobarDev/Specture --skill knowledge-ferescobardev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project knowledge decays: session discoveries vanish when conversations end, documentation indexes drift as files move, and no single file reflects a component's current behavior after dozens of specs. This Skill keeps a project's durable knowledge healthy across four modes without polluting the repo with low-signal noise. ## Core Features & Use Cases - Capture mode: Converts ephemeral session discoveries into durable artifacts (docs-index entries, ADR drafts, rules.yml invariants, conventions patches) with a maximum of 3 drafts and granular Plan-mode approval; AI-drafted ADRs always stay Proposed. - Audit mode: Read-only periodic scan of docs-index.yml detecting orphans, stale entries, duplicates, and uncovered docs, producing a health score and reports. - Stats mode: Reads per-epic build metrics from build-metrics.jsonl and applies the Spec Planning Gate reading, with optional baseline reconstruction. - Reconcile/characterize mode: Lazily backfills one component's living-behavior file in docs/05-specs/_current/ from its completed specs, or characterizes it read-only from code for adopted projects. - Use Case: After closing an epic that revealed an undocumented invariant, run capture to draft a rules.yml entry and ADR, approve them in Plan mode, and have them committed with telemetry logged. ## Quick Start Ask the AI to run the knowledge skill in capture mode to turn this session's discoveries into durable documentation artifacts for review.

Frequently Asked Questions about knowledge

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

FAQPage Schema
How do I capture session learnings into project documentation?▼

Invoke the knowledge skill in capture mode after a non-trivial session, epic closure, or debug fix. It gathers minimal evidence, cross-references existing artifacts, and proposes up to 3 drafts (ADR, docs-index entry, rules.yml invariant) for your approval in Plan mode before writing anything.

How do I detect stale or orphaned documentation index entries?▼

Run the knowledge skill in audit mode. It performs a read-only scan of docs-index.yml checking for orphan files, entries older than 180 or 365 days, duplicates, and uncovered docs, then writes a health score report to docs/.specture-meta/last-audit.md.

Can the knowledge skill write to Claude's personal memory?▼

No. The skill explicitly never writes to personal memory directories. Personal preference candidates detected during capture are only listed for the user, who may save them manually if desired.

What is the reconcile mode for living behavior files?▼

Reconcile builds one component's living-behavior file in docs/05-specs/_current/ from its completed specs, applying a last-spec-wins rule for supersessions. The characterize variant extracts behavior read-only from code when a component has no specs, common in adopted projects.

Does the knowledge skill auto-apply documentation changes?▼

No. All write operations require Plan-mode approval, and the user can approve or reject drafts individually. AI-drafted ADRs always remain in Proposed status, and only humans can promote docs-index entries to user_confirmed.

What are the limitations of the capture mode?▼

Capture is limited to 3 drafts per invocation (1 in teach mode) and a roughly 30K token evidence budget. It never modifies production code or tests, never generates Accepted ADRs, and treats low-signal sessions as a soft skip rather than an error.