Capture and persist research findings, discoveries, and decision rationale to findings.md.
Scanned 5/29/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill findings-capture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Findings Capture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-findings-capture)More formats (shields.io, HTML) on the badges page.
# 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...