What problem does it solve? Prose feedback on design documents loses the mapping between answers and the decisions they address, and hand-edited markdown answer slots silently drop multi-line notes. This Skill generates a per-decision review form so every verdict and note comes back structurally attached to the decision it belongs to. ## Core Features & Use Cases - Decision-card form generation: Builds a self-contained HTML form from references/form-template.html with one card per decision, each carrying a claim, detail, rationale, verdict control (approve/change/reject/defer), and a notes box. - Structured markdown output: The form emits a result file matching references/result-template.md, with stable decision IDs as join keys, blockquoted multi-line notes, and an explicit ## Not answered section so silence is never mistaken for consent. - Local file or Artifact variants: Runs as a file:// page with a watched result file on disk, or as a published artifact where the reviewer pastes feedback back into chat. - Use Case: You paste a 20-decision design doc for review. Instead of a wall of prose, the reviewer clicks verdicts card by card, and you ingest a markdown file where every ruling is bound to its decision ID. ## Quick Start Generate an owner-gate review form for the decisions in my design document and watch for the reviewer's feedback file.
