research-to-guidelisted

Transform already validated research into a clear, evidence-faithful user guide without losing claims, limitations, sources, application, or prototypes. Owns reader contract, composition, narrative style, examples, prototype, and coverage audit. Use to rewrite, convert, expand, structure, or turn a research report, technical analysis, market study, domain review, literature review, findings file, or baseline document into a guide, playbook, handbook, tutorial, decision guide, or separate user-facing MD. Responsibility boundary: does not conduct the primary research and does not choose PDF typography/layout; use `researcher` before it and `guide-pdf` after it. Triggers: 'turn this research into a guide', 'make a user-friendly MD', 'переработай исследование в гайд', 'добавь применение и прототип', 'не потеряй важное'.
createusernam/setup_project · ★ 0 · Data & Documents · score 62

Install: claude install-skill createusernam/setup_project

# Research to Guide IRON LAW: NEVER IMPROVE READABILITY BY SILENTLY DROPPING A CLAIM, BOUNDARY, COUNTERARGUMENT, OR EVIDENCE STATUS. Use this skill after research is complete or when the user provides a research artifact. It transforms evidence into a reader journey; it does not redo research unless a claim is missing, unstable, or explicitly challenged. ## Goal contract `GOAL_ROOT`: Turn validated evidence into a guide the target reader can act on without changing claim meaning or evidence status. - **Success:** the separate guide is operational, readable, source-traceable, and passes preservation coverage. - **Not success:** a shorter or smoother report that silently drops boundaries, counterevidence, hypotheses, or unknowns. ## Usage ```text /research-to-guide --source <research.md> [--baseline <original.md>] [--output <guide.md>] [--genre mentor|decision|field-textbook] [--prototype <name-or-path>] ``` - `source`: validated research or synthesis; required. - `baseline`: earlier artifact to audit for content lost during research revision. - `output`: always a separate Markdown file; infer `<source-stem>-guide.md` if omitted. - `genre`: infer from the user's outcome if omitted. - `prototype`: a concrete scenario that carries the explanation; derive one only when the evidence supports it. ## Workflow Copy and track this checklist: ```text Research to Guide Progress - [ ] 1. Establish the