Readme

Generates READMEs that follow specific opinionated patterns: lead with the problem not the tech stack, acknowledge prior art, show working examples before theory, and collapse depth instead of cutting it. Runs an interview to extract your project's pain point and fix, then writes structured docs with trust blocks near install commands and deep content hidden in collapsible sections. It validates output through a council system and enforces anti-patterns like no guru tone and stating your differentiator exactly once. Good when you need adoption-focused documentation and know your existing README buries the lede or sounds like a framework pitch instead of solving a concrete problem.