What problem does it solve? Teams often start coding before agreeing on what the product actually does, leading to mismatched expectations, scope drift, and undocumented design decisions. This Skill makes the README the canonical, user-facing design contract and settles every open design question before implementation begins. ## Core Features & Use Cases - README-first drafting: Writes or locates the canonical README describing the system as if it already exists, covering only what a user sees, runs, and reads. - Structured design interview: Grills the user one question at a time on unsettled decisions, always offering a recommended answer that a plain "yes" can endorse, and explores the codebase instead of asking when answers are discoverable. - Settle and report loop: Folds answers back into the README, edits clarity issues directly, asks before changing scope, and ends each pass with a report of settled decisions, open questions, and next actions. - Use Case: Before building a new CLI tool, run a pass to draft its README, resolve questions about flags, output formats, and error behavior, then hand the settled README to implementers as the contract. ## Quick Start Ask the agent to run a readme-driven-development pass on the feature you are about to build, starting by drafting or reviewing its README.
