atmos-specs-prdlisted

# Atmos Specs · PRD Turn a settled direction (from BRAINSTORM or a direct request) into a PRD that anyone on the team can read without having been in the original conversation. ## What this skill owns — and what it does not - **Owns**: `PRD.md` in exactly one spec directory. - **Does not own**: BRAINSTORM.md, TECH.md, TEST.md. Don't edit them here. Reference BRAINSTORM for context; leave TECH/TEST to their own skills. Why: PRD is the contract between product intent and engineering execution. Mixing architecture in blurs that contract; mixing brainstorm uncertainty in makes the PRD unusable as a source of truth. ## Read these before you write 1. `specs/AGENTS.md` — conventions. 2. The spec's own `BRAINSTORM.md` if it has useful content — that's your primary input. 3. A reference PRD of similar scope: `specs/APP/APP-005_github-integration/PRD.md` (feature-scoped) or `specs/APP/APP-001_atmos-core/PRD.md` (product-scoped). 4. The repo root `AGENTS.md` if you need a reminder of what Atmos is (workspaces, tmux, ACP, WebSocket-first, local-first). ## Workflow ### 1. Resolve the spec path `spec_id` is required. Accept `APP-005` or the full `APP-005_github-integration`. Resolve to `specs/APP/APP-005_<title>/PRD.md`. If the directory doesn't exist, stop and tell the user — creating new specs is the brainstorm skill's job. ### 2. Extract inputs Pull as much as possible from the existing files before asking questions: - Read `BRAINSTORM.md`. Promote material from its "Ready t