What problem does it solve?
Teams working in the Open Mercato repository risk writing duplicate or misplaced specs when preparing issues, and they lack a consistent path from a spec to its implementation. This Skill extends the shared om-prepare-issue workflow with repo-specific rules so every prepared issue lands in the right spec tree and carries a clear pickup path.
Core Features & Use Cases
- Enterprise spec scope: The optional --enterprise argument writes the spec under .ai/specs/enterprise/ instead of the default .ai/specs/ and adds the enterprise category label to the spec PR.
- Duplicate-spec detection: Before writing, it checks both .ai/specs/ and .ai/specs/enterprise/ for existing specs covering the same area, and scans .ai/lessons.md for matching lesson records by module, area, or topic tags.
- Spec methodology enforcement: Applies the repo-local om-spec-writing skill in full, including the compliance-review gate and the OM spec template.
- Use Case: A developer wants to spec a new CRM feature. The Skill checks both spec trees for overlap, writes the spec using the OM template, and records that /om-implement-spec will pick it up once the spec PR merges into develop.
Quick Start
Ask the assistant to prepare an issue for a new feature in the Open Mercato repo, optionally passing --enterprise to place the spec in the commercial scope.