c-01-findings-capture

Route verified findings to durable markdown surfaces with capture summaries.

27|4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/Foxfire1st/agents-remember --skill c-01-findings-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: c-01-findings-capture
Source: https://github.com/Foxfire1st/agents-remember/tree/main/.cursor/skills/c-01-findings-capture
Command: npx skills add https://github.com/Foxfire1st/agents-remember --skill c-01-findings-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture verified findings and route them to the appropriate durable surface to preserve context and ensure durable visibility.

Core Features & Use Cases

  • Durable routing of findings to owning surfaces (requirement_change_candidates.md, architecture_open_questions.md, the active phase artifact, or onboarding) to keep rules and decisions traceable.
  • Verification before propagation to onboarding, ensuring alignment with code and onboarding constraints.
  • Clear capture summaries that record evidence and destination for auditability and future reference.

Quick Start

In an active task workflow or standalone clarification, initiate a findings capture and route the confirmed finding to the correct durable destination with a concise evidence summary.

Frequently Asked Questions about c-01-findings-capture

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

FAQPage Schema
How do I capture findings during a workflow and route them to durable context?

To capture findings, initiate the capture process during an active task workflow or standalone clarification. The skill verifies the finding against code and onboarding constraints, then routes it to the appropriate durable surface to preserve context and ensure durable visibility.

What is the best way to document requirement change candidates during a task?

Documenting requirement change candidates is handled by routing verified findings to requirement_change_candidates.md. This ensures rules and decisions remain traceable and preserves context within the active task workflow.

How does architecture open question routing work for software documentation?

Architecture open question routing directs verified findings to architecture_open_questions.md. This preserves context and ensures durable visibility for unresolved architectural decisions during active development phases.

Can I log findings to the active phase artifact instead of a separate file?

Yes, findings can be routed directly to the active phase artifact. The skill determines the appropriate durable destination and returns a structured capture summary recording what was written and where.