Case topic · extended category

Collaboration

Single-page topic Aligns with Product & UX / Engineering

Overview: shorten loops between product, design, and engineering: templated issues, acceptance criteria, and change notes so agents can fill context in-session. Integrate with trackers: map fields like dependencies and risks so the model does not invent milestones.

Relationship to the case hub: collaboration work often lands in Product & UX (copy, PRDs, acceptance) and Engineering & architecture (issue/PR labeling, release notes). This page is a cross-role explainer; anchors #cat-design and #cat-eng.

Implementation notes (single page)

PRs, issues, and templates

PRs and issues: template fields match team norms. For UI changes, require design tokens or screenshot diffs to reduce spec drift.

Decision logs across roles

Across roles, have the agent output a decision log—who confirmed what, when, and what’s still open—for async work. With external parties, note what can be said externally vs internally.

Deliverables together

Deliverables: demos, release notes, and rollback hints together so review and release windows stay aligned.

# Case notes
- Trigger: issue becomes ready-for-dev
- Output: acceptance checklist + impact
- Exit: PR merged and docs updated

Case hub · Product & UX Open design category index Cases overview