Documents for a practical first release

Prompt: Draft a one-page PRD from this plan. Separate evidence from assumptions and ask about missing constraints.

• Problem and audience: who needs this and what evidence supports it?
• MVP and non-goals: what is the smallest useful release?
• Acceptance criteria: observable pass/fail conditions for each user journey.
• Measure and rollout: activation event, baseline, owner, pilot group, and rollback condition.

Prompt: Draft an architecture decision record for this design, comparing the simplest viable option with one alternative. Do not claim compliance or a cost estimate without supporting assumptions.

• Context: expected traffic, data sensitivity, budget, and operational constraints.
• Decision: components, data ownership, access boundaries, and API contracts.
• Tradeoffs: rejected alternative, consequences, and conditions for revisiting the decision.
• Recovery: backups, retries, observability, retention, and a tested rollback path.

Prompt: Draft a task contract for this workflow. Keep actions read-only until I approve an exact external change.

• Inputs: allowed sources, required access, sample input, and data retention.
• Output: required evidence, destination, and what counts as completion.
• Boundaries: permitted actions, approval points, maximum runs, and spend limits.
• Evaluation: happy path, missing access, unavailable source, malicious source text, duplicate attempt, and unknown write outcome.
• Recovery: stop conditions, escalation owner, and receipt checks before retrying.

Prompt: Turn this plan and task contract into a launch checklist with an owner and evidence link for each check. Leave untested items unchecked.

• Happy path and failure cases exercised with realistic, clearly labeled test data.
• Permissions, tenant isolation, and destructive-action approvals reviewed.
• Mobile and keyboard journeys checked; setup and cost requirements visible.
• Evidence, monitoring, support route, and rollback documented before release.