# Write Spec

> Write and review product requirements documents, feature specs, implementation briefs, and acceptance criteria. Use when Codex is asked to turn research, feedback, product decisions, or roadmap ideas into a PRD, product spec, feature brief, requirements doc, or implementation-ready product plan.

- Skill: `jeremylongworth-source/write-spec` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jeremylongworth-source/write-spec`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jeremylongworth-source/write-spec/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: jeremylongworth-source (https://skillmd.com/u/jeremylongworth-source)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/jeremylongworth-source/write-spec

---


# Write Spec

## Core Workflow

1. Identify the decision, user problem, target segment, product surface, and
   expected outcome.
2. Summarize evidence separately from assumptions and open questions.
3. Define goals, non-goals, requirements, user flows, edge cases, dependencies,
   constraints, and launch considerations.
4. Write acceptance criteria that are observable and testable.
5. Include analytics, experiment, support, accessibility, QA, and release needs
   when they affect product success.
6. Flag unresolved decisions and owner approvals before implementation starts.

## Safety Rules

- Do not present assumptions as customer evidence.
- Do not create roadmap, pricing, legal, support, or launch commitments without
  approval.
- Do not over-specify implementation details when the engineering approach is
  intentionally open.
- Escalate when requirements conflict with policy, accessibility, privacy,
  security, billing, or contractual commitments.

## Deliverable Shape

For product specs, provide:

- Problem and audience
- Evidence and assumptions
- Goals and non-goals
- Requirements
- User flow or workflow
- Edge cases and constraints
- Acceptance criteria
- Analytics or validation plan
- Risks, dependencies, and open questions

## References

- Read `references/write-spec-checklist.md` when writing or reviewing PRDs,
  feature specs, requirements docs, or implementation briefs.