Writing Product Specs and Documentation With AI

Write a Product Requirements Document for the following feature:

Feature: Mobile invoice approval for AP Managers

Background: AP Managers currently must use a desktop browser to approve
invoices. 40% of approval delays occur because managers are away from
their desks. Users have requested mobile approval capability in 6 of
the last 8 quarterly surveys.

Business goal: Reduce average invoice approval time from 4 hours to
under 1 hour for the 60% of invoices that require a single approval.

Scope:
- In scope: iOS and Android native app, approve/reject/comment on invoices,
  push notifications for pending approvals, access to invoice PDF
- Out of scope: invoice creation, complex multi-party approvals,
  offline mode (Phase 2)

Technical context: REST API exists. Mobile will consume existing endpoints.
User auth via existing Supabase Auth. No new backend required.

Include sections: Overview, Problem Statement, Goals and Non-Goals,
User Stories (high-level), Success Metrics, Open Questions.

Audience: Development team + product stakeholders.
Length: 2 pages. No fluff.

Write a one-page feature brief for the mobile invoice approval feature.

Audience: CFO and Finance Director (non-technical, care about business outcomes)

Content:
- What this feature does (plain language, no technical terms)
- Why we're building it now (business case with data)
- What users will experience (narrative walkthrough)
- Success metrics (how we'll know if it worked)
- Timeline and scope (one sentence each)

Tone: clear, confident, business-focused. No jargon. No bullet overload.

Write release notes for version 2.3 of the AP automation system.

Changes in this release:
- Mobile invoice approval (iOS and Android)
- Bulk rejection capability (select multiple invoices, reject with one comment)
- Performance: invoice list load time reduced from 3.2s to 0.8s
- Bug fix: attachment previews were failing for PDFs over 10MB
- Bug fix: email notifications were delayed 15-30 minutes (now real-time)

Two versions:
1. USER-FACING release notes (for the AP team): what changed,
   how to use the new features, what was fixed. Plain language.
   Focus on "what does this mean for you."
2. INTERNAL release notes (for the product/dev team): technical
   detail on the changes, deployment notes, any known limitations.

Draft a product roadmap communication for the next 6 months
of the AP automation product.

Now (current quarter): Core AP automation, invoice matching, approval workflow
Next (following quarter): Mobile approval, vendor self-service portal Phase 1
Later (6 months out): Analytics dashboard, ERP integration enhancements,
advanced fraud detection

For each horizon:
- What features are we delivering?
- What business problem does it solve?
- What does success look like?
- What is NOT committed (honest about uncertainty)

Two formats:
1. Executive one-pager (CFO audience) — business outcomes, timelines, dependencies
2. Team roadmap (development team) — more detail, scope, sequencing rationale

Tone: confident about commitments, honest about uncertainty in the "later" horizon.

Write developer documentation for our Invoice Approval API.

API details:
- Endpoint: POST /api/v2/invoices/{id}/approve
- Authentication: Bearer token (API key)
- Request body: { approved_by: string, comment?: string, delegation?: string }
- Success response: 200, { status: "approved", timestamp: ISO8601 }
- Error responses: 400 (validation), 403 (insufficient permissions),
  404 (invoice not found), 409 (already processed)

Document includes:
- Overview: what this endpoint does and when to use it
- Authentication: how to include the API key
- Request format: parameters with type, required/optional, description
- Response format: success and each error with what causes it
- Code example: curl + one language (TypeScript or Python, your choice)
- Common mistakes: top 3 errors developers make with this endpoint

Audience: external developers integrating with our system.