finding

What problem does it solve?

This Skill captures proactive discoveries from analysis, reviews, or inspections and converts them into neutral, factual finding reports and structured trackers so issues are recorded, classified, and handed off to downstream workflows.

Core Features & Use Cases

• Structured Reporting: Produce a Markdown finding report written to docs/findings/{YYYY-MM-DD_HHMM}_{name}.md using the provided template and required sections.
• Classification & Severity: Classify each finding by type (Defect, Vulnerability, Debt, Gap, Drift) and severity (Critical, High, Medium, Low) with rationale.
• Tracker Management: Create or update Findings Tracker files (*_FINDINGS_TRACKER.md), assign stable F-numbers, and generate recommended next-step tasks for downstream skills.
• Use Case: During a code review or security scan, log an authorization gap as a Finding and bootstrap a tracker so investigators can take the next pipeline step.

Quick Start

Use the finding skill by issuing a concise, factual description, for example: /finding Missing companyId filter in invoices WHERE clause --authorization gap.