version: 0.1.0

spec-driven-development

Overview

写 spec 不是写 PRD —— 是"动手前把目标、边界、交付物、验收标准想清楚"的纪律。omo 的 Prometheus 是 planner 出 plan,但没有强制 PRD;plan ≠ spec。Spec 是合同,plan 是排期。

omo Integration

Spec vs Prometheus Plan: Prometheus writes the plan as a markdown task list (- [ ] N. <title> for implementation rows, - [ ] F<n>. <title> for final-verifier rows) for atlas execution. brainstorming (or Prometheus Mode) writes the Design as Phase 0 of the same file. This skill writes the PRD/Spec as Phase 1 of the same file — the contract that comes BEFORE the Prometheus task list. Order:

Phase 0: Design (brainstorming — or Prometheus Mode via ulw-plan skill)
Phase 1: Spec (this skill — refines Phase 0 into a verifiable PRD with acceptance criteria + commands)
Momus plan review (omo built-in; momus agent validates plan against clarity/verification/context criteria)
Phase 2: Research + Phase 3: Slice (incremental-implementation)
/start-work to dispatch to Atlas

Spec vs Prometheus task list: Prometheus task rows encode what to do (with file paths and acceptance criteria per row). Our Phase 1 Spec encodes what done looks like (acceptance criteria, test strategy, scope boundaries). The Spec is the human contract; the task list is the worker contract. Both live in the same .omo/plans/<slug>.md.