capture

Documents solved problems into the correct Diataxis quadrant for future retrieval.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill capture-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capture
Source: https://github.com/manusco/wolfgang/tree/main/.cursor/skills/capture
Command: npx skills add https://github.com/manusco/wolfgang --skill capture-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solved problems often get rediscovered because the solution was never written down. This Skill routes the /capture command to the Resonance librarian procedure, which records a solved problem in the correct Diataxis documentation quadrant so the knowledge persists. ## Core Features & Use Cases - Command Routing: Maps the /capture command directly to the librarian skill's capture procedure. - Diataxis Classification: Ensures each documented solution lands in the correct Diataxis quadrant (tutorial, how-to, reference, or explanation). - Use Case: After debugging a tricky deployment failure, run /capture to document the root cause and fix so the team never re-diagnoses the same issue. ## Quick Start Ask the assistant to run the capture procedure to document the problem you just solved into the correct Diataxis quadrant.

Frequently Asked Questions about capture

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

FAQPage Schema
How do I document a solved problem with the capture command?▼

Invoke /capture after resolving an issue. The command routes to the librarian skill, which guides you through recording the problem and solution in the correct Diataxis quadrant according to its Definition of Done.

What is the Diataxis framework for documentation?▼

Diataxis divides documentation into four quadrants: tutorials, how-to guides, reference, and explanation. The capture procedure classifies each solved problem into the appropriate quadrant so knowledge stays organized and findable.

Does the capture skill contain the documentation logic itself?▼

No. This skill only routes the /capture command to the librarian skill located at .agents/skills/ops/librarian/SKILL.md. That librarian skill contains the actual capture procedure and its Definition of Done.

When should I use capture instead of writing docs manually?▼

Use capture right after solving a non-trivial problem, while the context is fresh. It enforces consistent placement and structure, whereas manual documentation often skips classification or gets written inconsistently.