om-app-spec-writing

Write and review business-level App Specs with domain models, workflows, and phased rollouts.

1.7k|382|Updated Sep 10, 2025
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill om-app-spec-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-app-spec-writing
Source: https://github.com/open-mercato/open-mercato/tree/main/.ai/skills/om-app-spec-writing
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-app-spec-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often jump from a vague business idea straight into code or feature specs, producing misaligned implementations, happy-path-only stories, and duplicated platform work. This Skill enforces a structured App Spec — domain model, identity model, ROI-backed workflows, gap analysis, and phased rollout — before any feature spec or code exists.

Core Features & Use Cases

  • Phased spec authoring: Guides a staff-PM persona through business context, ubiquitous-language glossary, domain model, identity model, workflows with measurable ROI, user stories with failure paths, and platform gap analysis scored in atomic commits.
  • Adversarial quality gates: Dispatches fresh-context DDD challenger subagents and architect checkpoints after each section to catch terminology drift, missing invariants, overengineering, and cross-story conflicts.
  • Review mode: Audits an existing App Spec against every section checklist and returns severity-ranked findings.
  • Use Case: A product lead says "define business requirements for a partner portal" and receives a complete App Spec with glossary, identity decision tree, 3-7 ROI-backed workflows, gap matrix, and a phased rollout ready for decomposition into feature specs.

Quick Start

Ask the agent to create an app spec for your product idea, providing the app name and a short description of the business need.

Frequently Asked Questions about om-app-spec-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an app spec before coding?

Invoke the skill with the app name and a free-form description of the business need. It walks you through business context, domain model, identity model, workflows with ROI, user stories, gap analysis, and a phased rollout, producing a single App Spec document.

What is the difference between an app spec and a feature spec?

An App Spec is the business architecture document defining who pays, the domain, workflows, and phasing. Feature specs are decomposed from a finished App Spec by the om-spec-writing skill, one independently deployable capability per spec.

Can I review an existing app spec instead of writing one?

Yes, pass the path to an existing App Spec with the --review flag. The skill runs every section checklist, dispatches the DDD challenger per major section, and returns findings ranked Critical, High, Medium, and Low.

How does the skill prevent writing code too early?

A hard gate forbids writing code, creating feature specs, or invoking implementation skills until the App Spec is complete and confirmed by the user. Challenger gates and architect checkpoints must also pass before handoff.

What are the limitations of the app spec workflow?

The skill is product-agnostic and relies on the repository's agent docs for platform capability names, identity primitives, and extension points. Without those docs or a repo-local extension, gap analysis falls back to generic design-doc conventions.