Loading...
Loading...
Found 5 Skills
Diagnose and guide revisions in non-fiction books. Use for non-fiction book revision, when arguments feel weak, evidence is outdated, readers report confusion, thesis is unclear, or book structure has problems. Keywords: non-fiction, revision, thesis, argument, evidence, structure.
This skill should be used when recognizing recurring themes, identifying patterns in work or data, or when "pattern", "recurring", or "repeated" are mentioned. For implementation, see codify skill.
Constructive critique through 5 HackerNews commenter personas with evidence-based claim validation. Use when user wants devil's advocacy, stress testing, or critical review of ideas, docs, architecture, or code. Use for "roast", "critique this", "poke holes", "devil's advocate", "stress test", or "what's wrong with". Do NOT use for code review (use systematic-code-review), implementation changes, or performance profiling without a specific critique request.
Check the evidence, biases, alternative explanations, and reporting boundaries required for research conclusions before implementation or submission. Use when the user asks for “review my research design”, “act as a strict reviewer”, “challenge this conclusion”, or requests the rw-research-referee workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Execute complete FPF cycle from hypothesis generation to decision