What to provide
Team roles, approved tools, common tasks, data rules, skill level, and available time.
What you will get
A four-week plan with training, practice tasks, owners, guardrails, and measurable outcomes.
Example: A five-person operations team has Microsoft Copilot but no agreed safe use cases or review standards.
Copy the full prompt
Customize the bracketed fields.
Use approved business information and have a person review the result before acting.
Create a practical 30-day AI adoption plan for our team.
Team and roles: [roles]
Approved AI tools: [tools and licenses]
Common work: [recurring tasks]
Current skill level: [beginner, mixed, or experienced]
Data and security rules: [what may and may not be shared]
Time available: [hours per week]
Ask up to five clarifying questions. Build a four-week plan that starts with low-risk drafting and analysis using fictional or approved non-sensitive information. For each week, define the lesson, practice task, owner, human review step, expected evidence, and a simple success measure. Include a short acceptable-use checklist, examples of information the team must not enter, and a process for reporting incorrect or unsafe output. Do not assume tool features, connect accounts, change company policy, or automate external actions. Mark policy, licensing, and security questions that require company approval.
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.Version 1.0 · Updated 2026-10-10 · Free starter template. Evaluate the output in your approved environment.