Findings Capture
Capture and persist research findings, discoveries, and decision rationale to findings.md.
Best use case
Findings Capture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Capture and persist research findings, discoveries, and decision rationale to findings.md.
Teams using Findings Capture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/findings-capture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Findings Capture Compares
| Feature / Agent | Findings Capture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Capture and persist research findings, discoveries, and decision rationale to findings.md.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Findings Capture Capture and persist research findings, discoveries, and decision rationale to findings.md. ## Agent Findings Curator - `pwf-findings-curator` ## Workflow 1. Initialize findings.md with structured section headers 2. Capture findings during execution with timestamps 3. Apply 2-Action Rule: persist after every 2 operations 4. Record decisions with supporting rationale 5. Deduplicate and organize on final flush 6. Analyze coverage for verification ## Inputs - `projectPath` - Root path for planning files - `phaseName` - Current phase name - `findings` - Array of finding objects - `decisions` - Array of decision objects ## Outputs - Updated findings.md with organized, timestamped entries - Coverage analysis for verification ## Process Files - `planning-orchestrator.js` - Findings initialization and appending - `planning-execution.js` - 2-Action Rule batches and final flush - `planning-verification.js` - Coverage analysis
Related Skills
packet-capture
Expert skill for packet capture and analysis using libpcap/Wireshark. Execute tcpdump/tshark commands, write BPF filter expressions, analyze pcap files, decode protocol layers, calculate statistics, and generate Wireshark dissectors.
motion-capture-analyzer
Motion capture data processing and analysis skill for gait analysis and biomechanical studies
screen-capture-api
Cross-platform screen and window capture for screenshots and recording
performance-baseline-capturer
Capture performance baselines before migration for regression comparison and SLA verification
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.