| name | c-01-findings-capture |
| description | Capture confirmed findings, route them to the right durable task-local path, and propagate factual current-state clarifications into onboarding immediately when allowed. |
c-01-findings-capture Findings Capture
Use this skill when durable knowledge emerges during developer discussion, task execution, review, or direct clarification and should not remain stranded in chat.
Companion file:
findings-capture-workflow.md
Operating Modes
- Inside a task workflow (an
l-01-agent-lifecycles orchestrator build phase or a w-02-light-task-workflow task, including a master + light sub-task series).
- Standalone during direct clarification.
Durable Destinations
Route the finding to the owning durable surface:
requirement_change_candidates.md when the finding changes scope, requirements, or developer intent.architecture_open_questions.md when the finding exposes a structural decision, dependency boundary, or design uncertainty.- The active phase artifact when the finding is planning-, implementation-, or review-local and belongs to the current task flow.
- Onboarding through
c-05-create-or-update-onboarding-files when the finding is a verified factual current-state clarification that should survive outside the task.
Rules
- Verify relevant code and onboarding before durable capture when possible.
- Do not copy developer clarifications into onboarding verbatim. Check them
against code reality first; when code contradicts or only partially supports
the clarification, surface the mismatch and resolve it before durable capture.
- Ask targeted follow-up questions if the finding is still ambiguous.
- Do not rewrite approved
requirements.md or architecture.md directly from one finding without developer approval.
- Do not send speculative, future-state, unresolved, or task-only notes into onboarding.
- If a finding affects both task-local artifacts and onboarding, update the task-local owner first, then propagate to onboarding only if the factual guardrail is satisfied.
- Use broader discovery only when direct code and onboarding checks are not enough.
- Never leave a confirmed finding only in chat when an appropriate durable destination exists.
