What problem does it solve? Writing and updating product planning specs (spec md) often leads to inconsistent structure, lost originals, and ambiguous feedback handling. This Skill standardizes spec authoring with a fixed template and protects existing documents by versioning copies instead of overwriting them. ## Core Features & Use Cases - New spec creation: Collects a draft outline plus required metadata (title, version, save location) and writes the spec in the 명세서_템플릿.md format with changelog table and Open Issues section. - Safe revision workflow: Reads an existing md, maps free-form feedback (natural language, screenshots) to sections, flags conflicts or ambiguities for confirmation, then writes a version+1 copy while preserving the original. - Section contract enforcement: Defines section boundaries (### N · 기능요소명 with marker comments) that downstream HTML, Figma, and QA outputs consume for four-way consistency. - Use Case: A product manager receives meeting notes requesting changes to an alarm rule spec. The Skill maps each request to a section, asks about ambiguous items, and produces spec v7.md with a changelog entry and ⭐ markers at changed points. ## Quick Start Ask the assistant to revise the attached spec md with these feedback notes and save it as the next version, or request a new spec draft from your outline.
