project-knowledge-capture

Convert verified decisions, lessons, and patterns into reusable project knowledge artifacts.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill project-knowledge-capture-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-knowledge-capture
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/project-knowledge-capture
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill project-knowledge-capture-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hard-won project insights—decisions, lessons, patterns, and anti-patterns—often disappear when a task ends, forcing teams to relearn the same lessons. This Skill transforms verified evidence into durable, reusable knowledge artifacts that outlive individual tasks. ## Core Features & Use Cases - Evidence-Grounded Capture: Only verified facts from handoffs, validated outcomes, and recurring issues become knowledge entries; unconfirmed hypotheses are explicitly excluded. - Structured Knowledge Forms: Normalizes entries into decisions, lessons, patterns, anti-patterns, and architecture notes with context, triggers, constraints, and provenance. - Deduplication and Conflict Handling: Merges duplicate entries by root concept while preserving evidence trails, and blocks publication when conflicting evidence cannot be reconciled. - Use Case: After repeated rollback incidents, convert the verified root cause into an anti-pattern entry with prevention guidance, published as reports/knowledge.json and reports/knowledge-capture.md for downstream memory workflows. ## Quick Start Use the project-knowledge-capture skill to turn the verified lessons from our latest project handoff into reusable knowledge entries.

Frequently Asked Questions about project-knowledge-capture

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

FAQPage Schema
How do I capture project lessons learned so they are reusable?

Gather verified signals from handoffs and validated outcomes, filter out unconfirmed hypotheses, then normalize each insight into a decision, lesson, pattern, anti-pattern, or architecture note with context and evidence provenance. Publish the results as knowledge.json and knowledge-capture.md reports.

What is the difference between project-knowledge-capture and project-handoff?

Project-handoff records current status and next actions for continuity, while project-knowledge-capture distills verified, reusable insights that should outlive the current task. Use handoff for state transfer and knowledge-capture for durable lessons and patterns.

Can I capture a lesson without verified evidence?

No. The skill fails closed when evidence provenance is missing and never promotes speculative advice as verified knowledge. Each entry must map to at least one verified evidence source.

What happens when two captured knowledge entries contradict each other?

Contradictory entries must be resolved or explicitly marked with uncertainty. If conflicting evidence cannot be reconciled, the skill emits a blocked status rather than publishing unreliable knowledge.

When should I not use project-knowledge-capture?

Do not use it for communicating current task status or next actions—that belongs to project-handoff. It is also unsuitable for unverified hypotheses or for publishing knowledge externally without explicit approval.