What problem does it solve? Writing feature specifications that are complete, architecturally sound, and ready for implementation is slow and error-prone; this Skill enforces a staff-engineer-grade process with a hard Open Questions gate so specs never ship with unresolved critical unknowns. ## Core Features & Use Cases - Skeleton-first drafting: Start with a minimal TLDR plus 2-3 sections, surface critical unknowns as a numbered Open Questions block, and iterate only after answers arrive. - Structured spec output: Produces dated spec files with Problem Statement, Architecture, Data Model, API Contracts, Edge Cases, Phasing, and a step-level Implementation Plan that feeds directly into automated PR creation. - Severity-ranked architectural review: Reviews existing specs against repository agent instructions, canonical primitives, backward-compatibility contracts, and reversibility, reporting Critical/High/Medium/Low findings with evidence and corrections. - Autonomous mode: An --autonomous flag resolves gate questions with the most reversible defaults and marks risky ones as needing human confirmation, enabling unattended pipeline runs. - Use Case: A developer starting a new billing feature invokes the skill, answers three gate questions about scope and data model, and receives a phased spec whose implementation plan is handed phase-by-phase to an automated PR-creation workflow. ## Quick Start Ask the agent to write a spec for your new feature using the om-spec-writing skill and answer the Open Questions it presents.
