Design a Jira and Notion handoff — Full Prompt Suite

A guided prompt system to define how product context, delivery work, and evidence move between tools.

8 downloadable Markdown files

Discovery, master, implementation, review and handoff prompts

Business-context worksheet and internal-use license

Immediate ZIP download after confirmed payment

Support: account and delivery help through AEVUS Support

Refund terms: reviewed under the Terms of Service

Built for: source of truth · field mapping · status transitions · audit evidence

Secure checkout by Stripe. AEVUS does not receive your complete card number.

What to provide

Teams, Jira projects, Notion spaces, Git repositories, work stages, and ownership rules.

What you will get

A source-of-truth map, field mapping, lifecycle, permissions, and implementation checklist.

Copy the full prompt

Customize the bracketed fields.

Use approved business information and have a person review the result before acting.

Design a reviewable workflow connecting Jira, Notion, and Git for [team or product].
People and roles: [roles]
Jira projects and issue types: [details]
Notion spaces or databases: [details]
Git repositories and release branches: [details]
Current work stages: [stages]
Approval and access rules: [rules]

Ask which system owns product decisions, technical state, delivery status, and runtime evidence. Then propose a source-of-truth map, stable identifiers, field mappings, status transitions, link conventions, ownership, permissions, duplicate prevention, failure handling, and an audit trail. Include one example feature moving from decision through implementation and verified release. Recommend the minimum connector scopes and a read-only pilot first. Do not sign in, create tokens, connect services, change permissions, or write records. Clearly separate proposed automation from actions a person must approve.

Response requirements:
- Begin with a short summary of the goal, confirmed facts, assumptions, and missing information.
- Ask focused clarification questions before completing the work when a missing answer would materially change the result.
- Use clear headings, tables, checklists, or numbered steps where they make the output easier to use.
- Keep source facts separate from recommendations. Quote or cite supplied evidence when the task depends on source material.
- Mark unsupported details, decisions, owners, dates, costs, credentials, and commitments as [TO CONFIRM].
- Identify the three most important risks, failure conditions, or quality checks.
- End with a practical next-action checklist that names the responsible role and the evidence needed to confirm completion.
- Include a final self-review: check the answer against this prompt, list any unmet requirement, and correct it before responding.
- Do not claim that you accessed a system, verified an external fact, completed an action, or tested the result unless evidence in this conversation proves it.

Get help adapting this prompt ↗

Version 1.0 · Updated 2026-10-10 · Free starter template. Evaluate the output in your approved environment.