Findings Capture
npx machina-cli add skill a5c-ai/babysitter/findings-capture --openclawFiles (1)
SKILL.md
954 B
Findings Capture
Capture and persist research findings, discoveries, and decision rationale to findings.md.
Agent
Findings Curator - pwf-findings-curator
Workflow
- Initialize findings.md with structured section headers
- Capture findings during execution with timestamps
- Apply 2-Action Rule: persist after every 2 operations
- Record decisions with supporting rationale
- Deduplicate and organize on final flush
- Analyze coverage for verification
Inputs
projectPath- Root path for planning filesphaseName- Current phase namefindings- Array of finding objectsdecisions- Array of decision objects
Outputs
- Updated findings.md with organized, timestamped entries
- Coverage analysis for verification
Process Files
planning-orchestrator.js- Findings initialization and appendingplanning-execution.js- 2-Action Rule batches and final flushplanning-verification.js- Coverage analysis
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/planning-with-files/skills/findings-capture/SKILL.mdView on GitHub Overview
Findings Capture records research findings, discoveries, and decision rationale in findings.md for traceability. It runs under the Findings Curator agent to initialize structured sections, capture timestamped entries during execution, deduplicate on final flush, and provide coverage verification.
How This Skill Works
During planning, Findings Curator initializes findings.md with structured headers. As work progresses, it appends findings with timestamps and records decisions with rationale. It enforces a 2-Action Rule: persist after every two operations and performs a final flush plus coverage analysis.
When to Use It
- During research sprints to log discoveries and decision rationale
- Before making planning decisions to ensure traceability to findings.md
- When collaborating with multiple contributors on a project
- Before phase handoffs to verify coverage and deduplication
- During quality checks to ensure decisions have supporting rationale
Quick Start
- Step 1: Initialize findings.md with headers using Findings Curator
- Step 2: Capture a finding with timestamp and add your decision rationale
- Step 3: After every two ops, persist; run final flush and coverage analysis
Best Practices
- Initialize findings.md with structured headers before work begins
- Capture each finding with a timestamp and context
- Record decisions with explicit supporting rationale
- Deduplicate and organize entries on final flush
- Run coverage analysis to verify complete findings
Example Use Cases
- Logging a new research finding with timestamp
- Documenting a design decision with rationale
- Chronicling a risk and its mitigation plan
- Batch persisting entries after two operations (2-Action Rule)
- Performing final coverage verification before project wrap
Frequently Asked Questions
Add this skill to your agents