Amazon Writing

One skill for Amazon narrative document types — shared spec format for humans reviewing in meetings and agents executing in spec-driven development.

Companion wedge: four-answers — answer-only enforcement on Q&A.
Companion operating layer: team-of-one — Amazon mechanisms for a solo builder.

Deep guides: docs/ · Rules reference: reference.md · Spec-driven context: docs/spec-driven.md

Why this matters now (spec-driven development)

In spec-driven development, the document is the contract:

• Humans read it in narrative meetings (silent read → FUND / KILL / REVISE)
• Agents read it as the source of truth before writing code, tests, or implementation plans
• Both need the same properties: precise language, testable claims, explicit risks, no weasel words