Loading...
Loading...
Found 3 Skills
Initialize and manage the evidence collection directory for professional security audits with documented proof of findings.
Use when writing or reviewing anything that will be read as true — a decision record, a README, an acceptance report, a runbook, a changelog entry, an audit finding, or any claim that something was verified. Applies the ten canons of evidence-backed documentation — what makes a claim documentation rather than an assertion — and routes to the doctrine that enforces each one. Also use when a project needs a documentation gate, a decision register, a propagation matrix, or a retrospective that outlives its author. Triggers - 'documentation gate', 'decision record', 'ADR', 'acceptance report', 'runbook', 'is this verified', 'доказательная документация', 'записать решение', 'отчёт о приёмке', 'раннбук', 'чем это подтверждено', 'доки в синхроне'. Not for: drafts, chat answers, commit messages or code comments — say 'без доков' to opt out.
Set up and maintain an auditable JSON status file for a single research project, recording research phases, materials, judgments, unknowns, handovers, and change logs. Use when the user asks for "establish research archives", "save the material status of this research project", "hand over literature, judgments, and next steps to another research Skill", "check research status files", or requests the rw-research-passport workflow.