What problem does it solve? Barwise requires a written, reviewed spec before any development begins, and ad-hoc specs drift from the house format, bury decisions, or ship ungrounded claims. This Skill turns a REPO_REVIEW finding, feature, or refactor into a reviewable docs/specs/*.spec.md that follows the project conventions. ## Core Features & Use Cases - Structured spec workflow: Grounds the design against the code, interviews away ambiguities, argues from the project's design principles, and drafts from the annotated template.spec.md. - Editing and quality gates: Runs ordered edit passes (BLUF, brevity, voice, accuracy), scans for LLM writing tics, and enforces a design and formatting pre-push gate including dprint checks. - Sensemaking discipline: Anchors designs in verified facts, holds competing frames, runs premortems, and marks ungrounded forward sections as provisional. - Use Case: Given a REPO_REVIEW finding about a misplaced module, produce a spec with principle framing, an inventory table, workstreams split into independently shippable PRs, and open decisions for the reviewer. ## Quick Start Use the spec-writer skill to draft a design spec for the REPO_REVIEW finding about moving the manifest reader out of core.
