Prompt file imported from steikould/center_of_excellence_personas (.github/prompts/coop/co-04-rotation-capstone.prompt.md). Copyright stays with the author.

CO-04 — Rotation Capstone

Name: co-04-rotation-capstone
Author: steikould

Goal: Reflect on your entire rotation. Summarize what you learned about each domain, document the gaps you identified, and leave recommendations for the next co-op. This is your signature deliverable.

What You're Learning

How to synthesize diverse experiences into a coherent narrative
Reflective practice: turning experience into transferable insight
Constructive recommendation-writing: identifying problems AND proposing solutions
The art of the handoff: leaving something better than you found it

Why This Matters

Your rotation capstone serves three audiences:

You — This is your portfolio piece. It demonstrates that you didn't just sit in a chair for a few months; you learned, contributed, and grew. Take it to interviews. Reference it in applications. Be proud of it.
The next co-op — Imagine if YOU had received a document on your first day that said: "Here's what the last co-op learned, what they wished they'd known, and what to focus on." That's what you're creating.
The CoE leadership — Your fresh-eyes perspective on gaps, friction, and opportunities is intelligence that experienced team members may not have. Leaders need this.

This isn't a formality. It's the most impactful thing you'll produce during your rotation.

The Challenge

Part 1 — Reflect on Each Domain

Go through your journey file and shadowing summaries. For each persona domain you encountered, write a reflection. Ask Copilot to help you structure it:

@coop

Help me write a domain reflection for my rotation capstone. I want to summarize what I learned about each area of the AI Center of Excellence. For each domain, help me organize my thoughts:

**Domain**: [e.g., Enterprise Architecture, Data Science, Process Engineering, etc.]

**What I learned**: (2-3 key takeaways about this domain)
- What does this team/role actually do?
- What challenges do they face?
- What tools and systems do they use?

**What surprised me**: (1-2 things I didn't expect)

**How it connects to other domains**: (which other personas does this work with, and how?)

**A question I still have**: (something I'd explore if I had more time)

Help me write reflections for each domain I encountered. Remind me to be specific — "I learned about data science" is vague. "I learned that model validation in a GxP environment requires formal protocols similar to equipment validation, which means data scientists need to work closely with Quality" is specific and shows understanding.

Part 2 — Document Gaps and Observations

This is where your fresh perspective is most valuable. Ask Copilot:

@coop

Help me compile the gaps and observations from my rotation into a structured analysis. I want to organize them into categories:

**Knowledge base gaps** — What's missing from the knowledge base?
- Empty directories or sparse sections I noticed
- Types of knowledge that get discussed but aren't documented
- Schemas that might be needed but don't exist yet

**Process gaps** — What processes could work better?
- Onboarding friction points I experienced
- Handoffs between personas that seem unclear
- Tools or resources that were hard to find

**Communication gaps** — Where does information get lost?
- Terms or concepts that are used differently by different people
- Decisions that happened but weren't recorded
- Tribal knowledge that lives in people's heads but not in documents

**Opportunities** — What could the CoE do that it isn't doing yet?
- Connections between personas that could be stronger
- Artifacts that would benefit multiple roles
- Skills or topics that deserve their own module

For each gap/observation:
1. What I observed (specific and factual)
2. Why it matters (impact on the team or next co-op)
3. My suggestion (what could be done about it)

Help me be constructive, not critical. The goal is to make things better, not to point fingers.

Part 3 — Write Recommendations for the Next Co-op

This is your gift to your successor. Ask Copilot:

@coop

Help me write a "Guide for the Next Co-op" section of my capstone. I want to be the mentor I wish I'd had on day one. Include:

**Before you start:**
- What to read first (top 5 files in this repo, in order)
- What tools to set up (VS Code, Copilot, Git basics)
- Who to meet in your first week (and what to ask them)

**During your rotation:**
- Which modules to prioritize (and which ones to save for later if time is short)
- How to get the most out of shadowing (my tips from CO-02)
- How to choose your first knowledge base contribution (my tips from CO-03)
- Common mistakes I made (and how to avoid them)

**Advice I wish someone had told me:**
- About the industry (animal pharma context that took me a while to grasp)
- About the technology (tools or concepts that were harder than expected)
- About the culture (how the CoE works, how to ask for help, what's valued)
- About making contributions (how to turn observations into documented knowledge)

**What to focus on:**
Based on the gaps I identified, here are areas where the next co-op could make the biggest impact:
[List 3-5 specific focus areas with enough context to act on them]

Make this warm and practical. The next co-op should read this and feel prepared, not overwhelmed.

Part 4 — Assemble the Capstone

Now bring it all together into a single, polished document. Ask Copilot:

@coop

Help me assemble my rotation capstone into a complete document. It should include:

**Header:**
- My name/identifier (or "Co-op, [rotation period]")
- Rotation dates
- The AI Center of Excellence, [Company]
- Date of this document

**Executive Summary** (3-5 sentences):
What I did, what I learned, and what I recommend. Someone should be able to read this paragraph and understand the value of my rotation.

**Section 1: My Journey** (1 page max)
- Modules completed (shared and role-specific)
- Knowledge base contributions made
- Key skills developed

**Section 2: Domain Reflections** (from Part 1)
- One subsection per domain I explored
- Focused on insights, not just descriptions

**Section 3: Contributions** (from CO-03 and throughout)
- What I contributed to the knowledge base
- Impact of each contribution (who benefits and how)

**Section 4: Gap Analysis** (from Part 2)
- Organized by category
- Each gap includes observation, impact, and suggestion

**Section 5: Recommendations for the Next Co-op** (from Part 3)
- Practical, actionable, and encouraging

**Section 6: Personal Reflection**
- What I learned about AI in animal pharma
- What I learned about working in a cross-functional team
- How this experience will influence my career

**Appendix:**
- My glossary (link to `personas/coop/workspace/artifacts/glossary.md`)
- My "Who Does What" directory (link to `personas/coop/workspace/artifacts/who-does-what.md`)
- My shadowing summaries (link to `personas/coop/workspace/artifacts/shadowing-summary.md`)

Help me write transitions between sections so it reads as a cohesive document, not just a collection of parts. The tone should be professional but genuine — this is my voice, my experience, my recommendations.

Save Step

Save the complete capstone to personas/coop/workspace/artifacts/capstone/rotation-capstone.md
Make sure all referenced appendix files are saved in your workspace
Update your journey file: mark CO-04 complete and fill in the Final Reflection section
Consider sharing your glossary and "Who Does What" directory more broadly — these could become shared resources

You did it. You came in as someone new to the industry, the team, and the technology. You leave with a portfolio of real contributions, a deep understanding of how AI works in animal pharma, and a document that will genuinely help the next person who sits in your chair. That's something to be proud of.

Stretch Goal

Present your capstone. Even if it's informal, practice the skill of summarizing your work for an audience:

@coop

Help me prepare a 10-minute presentation of my rotation capstone. I want to present to the CoE team. Structure it as:

- **Slide 1**: Title and rotation overview (30 seconds)
- **Slide 2**: What the CoE does and my role in it (1 minute — assume some audience members don't know the CoE well)
- **Slide 3-4**: Top 3 things I learned (2 minutes — pick the most interesting insights, not everything)
- **Slide 5-6**: My contributions and their impact (2 minutes — show, don't just tell)
- **Slide 7-8**: Gap analysis highlights (2 minutes — pick the 3 most actionable gaps)
- **Slide 9**: Recommendations for the next co-op (1 minute)
- **Slide 10**: What this experience means for my career (30 seconds — end on a personal, genuine note)
- **Q&A**: 2 minutes

For each slide, give me:
- The key message (one sentence)
- Talking points (2-3 bullets)
- One thing to avoid (a common presentation mistake for this type of content)

Help me keep it conversational, not stiff. I want the audience to hear my authentic voice.

Save presentation notes to personas/coop/workspace/artifacts/capstone/presentation-notes.md.

Congratulations on completing your co-op rotation modules! Return to your journey file and complete the Final Reflection. Then head to Module 08 (Capstone) in the shared modules to do the final synthesis. You've earned it.

# CO-04 — Rotation Capstone > **Goal**: Reflect on your entire rotation. Summarize what you learned about each domain, document the gaps you identified, and leave recommendations for the next co-op. This is your signature deliverable. --- ## What You're Learning - How to synthesize diverse experiences into a coherent narrative - Reflective practice: turning experience into transferable insight - Constructive recommendation-writing: identifying problems AND proposing solutions - The art of the handoff: leaving something better than you found it ## Why This Matters Your rotation capstone serves three audiences: 1. **You** — This is your portfolio piece. It demonstrates that you didn't just sit in a chair for a few months; you learned, contributed, and grew. Take it to interviews. Reference it in applications. Be proud of it. 2. **The next co-op** — Imagine if YOU had received a document on your first day that said: "Here's what the last co-op learned, what they wished they'd known, and what to focus on." That's what you're creating. 3. **The CoE leadership** — Your fresh-eyes perspective on gaps, friction, and opportunities is intelligence that experienced team members may not have. Leaders need this. This isn't a formality. It's the most impactful thing you'll produce during your rotation. ## The Challenge ### Part 1 — Reflect on Each Domain Go through your journey file and shadowing summaries. For each persona domain you encountered, write a reflection. Ask Copilot to help you structure it: ``` @coop Help me write a domain reflection for my rotation capstone. I want to summarize what I learned about each area of the AI Center of Excellence. For each domain, help me organize my thoughts: **Domain**: [e.g., Enterprise Architecture, Data Science, Process Engineering, etc.] **What I learned**: (2-3 key takeaways about this domain) - What does this team/role actually do? - What challenges do they face? - What tools and systems do they use? **What surprised me**: (1-2 things I didn't expect) **How it connects to other domains**: (which other personas does this work with, and how?) **A question I still have**: (something I'd explore if I had more time) Help me write reflections for each domain I encountered. Remind me to be specific — "I learned about data science" is vague. "I learned that model validation in a GxP environment requires formal protocols similar to equipment validation, which means data scientists need to work closely with Quality" is specific and shows understanding. ``` ### Part 2 — Document Gaps and Observations This is where your fresh perspective is most valuable. Ask Copilot: ``` @coop Help me compile the gaps and observations from my rotation into a structured analysis. I want to organize them into categories: **Knowledge base gaps** — What's missing from the knowledge base? - Empty directories or sparse sections I noticed - Types of knowledge that get discussed but aren't documented - Schemas that might be needed but don't exist yet **Process gaps** — What processes could work better? - Onboarding friction points I experienced - Handoffs between personas that seem unclear - Tools or resources that were hard to find **Communication gaps** — Where does information get lost? - Terms or concepts that are used differently by different people - Decisions that happened but weren't recorded - Tribal knowledge that lives in people's heads but not in documents **Opportunities** — What could the CoE do that it isn't doing yet? - Connections between personas that could be stronger - Artifacts that would benefit multiple roles - Skills or topics that deserve their own module For each gap/observation: 1. What I observed (specific and factual) 2. Why it matters (impact on the team or next co-op) 3. My suggestion (what could be done about it) Help me be constructive, not critical. The goal is to make things better, not to point fingers. ``` ### Part 3 — Write Recommendations for the Next Co-op This is your gift to your successor. Ask Copilot: ``` @coop Help me write a "Guide for the Next Co-op" section of my capstone. I want to be the mentor I wish I'd had on day one. Include: **Before you start:** - What to read first (top 5 files in this repo, in order) - What tools to set up (VS Code, Copilot, Git basics) - Who to meet in your first week (and what to ask them) **During your rotation:** - Which modules to prioritize (and which ones to save for later if time is short) - How to get the most out of shadowing (my tips from CO-02) - How to choose your first knowledge base contribution (my tips from CO-03) - Common mistakes I made (and how to avoid them) **Advice I wish someone had told me:** - About the industry (animal pharma context that took me a while to grasp) - About the technology (tools or concepts that were harder than expected) - About the culture (how the CoE works, how to ask for help, what's valued) - About making contributions (how to turn observations into documented knowledge) **What to focus on:** Based on the gaps I identified, here are areas where the next co-op could make the biggest impact: [List 3-5 specific focus areas with enough context to act on them] Make this warm and practical. The next co-op should read this and feel prepared, not overwhelmed. ``` ### Part 4 — Assemble the Capstone Now bring it all together into a single, polished document. Ask Copilot: ``` @coop Help me assemble my rotation capstone into a complete document. It should include: **Header:** - My name/identifier (or "Co-op, [rotation period]") - Rotation dates - The AI Center of Excellence, [Company] - Date of this document **Executive Summary** (3-5 sentences): What I did, what I learned, and what I recommend. Someone should be able to read this paragraph and understand the value of my rotation. **Section 1: My Journey** (1 page max) - Modules completed (shared and role-specific) - Knowledge base contributions made - Key skills developed **Section 2: Domain Reflections** (from Part 1) - One subsection per domain I explored - Focused on insights, not just descriptions **Section 3: Contributions** (from CO-03 and throughout) - What I contributed to the knowledge base - Impact of each contribution (who benefits and how) **Section 4: Gap Analysis** (from Part 2) - Organized by category - Each gap includes observation, impact, and suggestion **Section 5: Recommendations for the Next Co-op** (from Part 3) - Practical, actionable, and encouraging **Section 6: Personal Reflection** - What I learned about AI in animal pharma - What I learned about working in a cross-functional team - How this experience will influence my career **Appendix:** - My glossary (link to `personas/coop/workspace/artifacts/glossary.md`) - My "Who Does What" directory (link to `personas/coop/workspace/artifacts/who-does-what.md`) - My shadowing summaries (link to `personas/coop/workspace/artifacts/shadowing-summary.md`) Help me write transitions between sections so it reads as a cohesive document, not just a collection of parts. The tone should be professional but genuine — this is my voice, my experience, my recommendations. ``` ## Save Step - Save the complete capstone to `personas/coop/workspace/artifacts/capstone/rotation-capstone.md` - Make sure all referenced appendix files are saved in your workspace - Update your journey file: mark CO-04 complete and fill in the Final Reflection section - Consider sharing your glossary and "Who Does What" directory more broadly — these could become shared resources You did it. You came in as someone new to the industry, the team, and the technology. You leave with a portfolio of real contributions, a deep understanding of how AI works in animal pharma, and a document that will genuinely help the next person who sits in your chair. That's something to be proud of. ## Stretch Goal Present your capstone. Even if it's informal, practice the skill of summarizing your work for an audience: ``` @coop Help me prepare a 10-minute presentation of my rotation capstone. I want to present to the CoE team. Structure it as: - **Slide 1**: Title and rotation overview (30 seconds) - **Slide 2**: What the CoE does and my role in it (1 minute — assume some audience members don't know the CoE well) - **Slide 3-4**: Top 3 things I learned (2 minutes — pick the most interesting insights, not everything) - **Slide 5-6**: My contributions and their impact (2 minutes — show, don't just tell) - **Slide 7-8**: Gap analysis highlights (2 minutes — pick the 3 most actionable gaps) - **Slide 9**: Recommendations for the next co-op (1 minute) - **Slide 10**: What this experience means for my career (30 seconds — end on a personal, genuine note) - **Q&A**: 2 minutes For each slide, give me: - The key message (one sentence) - Talking points (2-3 bullets) - One thing to avoid (a common presentation mistake for this type of content) Help me keep it conversational, not stiff. I want the audience to hear my authentic voice. ``` Save presentation notes to `personas/coop/workspace/artifacts/capstone/presentation-notes.md`. --- **Congratulations on completing your co-op rotation modules!** Return to your journey file and complete the Final Reflection. Then head to Module 08 (Capstone) in the shared modules to do the final synthesis. You've earned it.

{ "prompt": "# CO-04 — Rotation Capstone\n\n> **Goal**: Reflect on your entire rotation. Summarize what you learned about each domain, document the gaps you identified, and leave recommendations for the next co-op. This is your signature deliverable.\n\n---\n\n## What You're Learning\n- How to synthesize diverse experiences into a coherent narrative\n- Reflective practice: turning experience into transferable insight\n- Constructive recommendation-writing: identifying problems AND proposing solutions\n- The art of the handoff: leaving something better than you found it\n\n## Why This Matters\n\nYour rotation capstone serves three audiences:\n\n1. **You** — This is your portfolio piece. It demonstrates that you didn't just sit in a chair for a few months; you learned, contributed, and grew. Take it to interviews. Reference it in applications. Be proud of it.\n\n2. **The next co-op** — Imagine if YOU had received a document on your first day that said: \"Here's what the last co-op learned, what they wished they'd known, and what to focus on.\" That's what you're creating.\n\n3. **The CoE leadership** — Your fresh-eyes perspective on gaps, friction, and opportunities is intelligence that experienced team members may not have. Leaders need this.\n\nThis isn't a formality. It's the most impactful thing you'll produce during your rotation.\n\n## The Challenge\n\n### Part 1 — Reflect on Each Domain\n\nGo through your journey file and shadowing summaries. For each persona domain you encountered, write a reflection. Ask Copilot to help you structure it:\n\n```\n@coop\n\nHelp me write a domain reflection for my rotation capstone. I want to summarize what I learned about each area of the AI Center of Excellence. For each domain, help me organize my thoughts:\n\n**Domain**: [e.g., Enterprise Architecture, Data Science, Process Engineering, etc.]\n\n**What I learned**: (2-3 key takeaways about this domain)\n- What does this team/role actually do?\n- What challenges do they face?\n- What tools and systems do they use?\n\n**What surprised me**: (1-2 things I didn't expect)\n\n**How it connects to other domains**: (which other personas does this work with, and how?)\n\n**A question I still have**: (something I'd explore if I had more time)\n\nHelp me write reflections for each domain I encountered. Remind me to be specific — \"I learned about data science\" is vague. \"I learned that model validation in a GxP environment requires formal protocols similar to equipment validation, which means data scientists need to work closely with Quality\" is specific and shows understanding.\n```\n\n### Part 2 — Document Gaps and Observations\n\nThis is where your fresh perspective is most valuable. Ask Copilot:\n\n```\n@coop\n\nHelp me compile the gaps and observations from my rotation into a structured analysis. I want to organize them into categories:\n\n**Knowledge base gaps** — What's missing from the knowledge base?\n- Empty directories or sparse sections I noticed\n- Types of knowledge that get discussed but aren't documented\n- Schemas that might be needed but don't exist yet\n\n**Process gaps** — What processes could work better?\n- Onboarding friction points I experienced\n- Handoffs between personas that seem unclear\n- Tools or resources that were hard to find\n\n**Communication gaps** — Where does information get lost?\n- Terms or concepts that are used differently by different people\n- Decisions that happened but weren't recorded\n- Tribal knowledge that lives in people's heads but not in documents\n\n**Opportunities** — What could the CoE do that it isn't doing yet?\n- Connections between personas that could be stronger\n- Artifacts that would benefit multiple roles\n- Skills or topics that deserve their own module\n\nFor each gap/observation:\n1. What I observed (specific and factual)\n2. Why it matters (impact on the team or next co-op)\n3. My suggestion (what could be done about it)\n\nHelp me be constructive, not critical. The goal is to make things better, not to point fingers.\n```\n\n### Part 3 — Write Recommendations for the Next Co-op\n\nThis is your gift to your successor. Ask Copilot:\n\n```\n@coop\n\nHelp me write a \"Guide for the Next Co-op\" section of my capstone. I want to be the mentor I wish I'd had on day one. Include:\n\n**Before you start:**\n- What to read first (top 5 files in this repo, in order)\n- What tools to set up (VS Code, Copilot, Git basics)\n- Who to meet in your first week (and what to ask them)\n\n**During your rotation:**\n- Which modules to prioritize (and which ones to save for later if time is short)\n- How to get the most out of shadowing (my tips from CO-02)\n- How to choose your first knowledge base contribution (my tips from CO-03)\n- Common mistakes I made (and how to avoid them)\n\n**Advice I wish someone had told me:**\n- About the industry (animal pharma context that took me a while to grasp)\n- About the technology (tools or concepts that were harder than expected)\n- About the culture (how the CoE works, how to ask for help, what's valued)\n- About making contributions (how to turn observations into documented knowledge)\n\n**What to focus on:**\nBased on the gaps I identified, here are areas where the next co-op could make the biggest impact:\n[List 3-5 specific focus areas with enough context to act on them]\n\nMake this warm and practical. The next co-op should read this and feel prepared, not overwhelmed.\n```\n\n### Part 4 — Assemble the Capstone\n\nNow bring it all together into a single, polished document. Ask Copilot:\n\n```\n@coop\n\nHelp me assemble my rotation capstone into a complete document. It should include:\n\n**Header:**\n- My name/identifier (or \"Co-op, [rotation period]\")\n- Rotation dates\n- The AI Center of Excellence, [Company]\n- Date of this document\n\n**Executive Summary** (3-5 sentences):\nWhat I did, what I learned, and what I recommend. Someone should be able to read this paragraph and understand the value of my rotation.\n\n**Section 1: My Journey** (1 page max)\n- Modules completed (shared and role-specific)\n- Knowledge base contributions made\n- Key skills developed\n\n**Section 2: Domain Reflections** (from Part 1)\n- One subsection per domain I explored\n- Focused on insights, not just descriptions\n\n**Section 3: Contributions** (from CO-03 and throughout)\n- What I contributed to the knowledge base\n- Impact of each contribution (who benefits and how)\n\n**Section 4: Gap Analysis** (from Part 2)\n- Organized by category\n- Each gap includes observation, impact, and suggestion\n\n**Section 5: Recommendations for the Next Co-op** (from Part 3)\n- Practical, actionable, and encouraging\n\n**Section 6: Personal Reflection**\n- What I learned about AI in animal pharma\n- What I learned about working in a cross-functional team\n- How this experience will influence my career\n\n**Appendix:**\n- My glossary (link to `personas/coop/workspace/artifacts/glossary.md`)\n- My \"Who Does What\" directory (link to `personas/coop/workspace/artifacts/who-does-what.md`)\n- My shadowing summaries (link to `personas/coop/workspace/artifacts/shadowing-summary.md`)\n\nHelp me write transitions between sections so it reads as a cohesive document, not just a collection of parts. The tone should be professional but genuine — this is my voice, my experience, my recommendations.\n```\n\n## Save Step\n\n- Save the complete capstone to `personas/coop/workspace/artifacts/capstone/rotation-capstone.md`\n- Make sure all referenced appendix files are saved in your workspace\n- Update your journey file: mark CO-04 complete and fill in the Final Reflection section\n- Consider sharing your glossary and \"Who Does What\" directory more broadly — these could become shared resources\n\nYou did it. You came in as someone new to the industry, the team, and the technology. You leave with a portfolio of real contributions, a deep understanding of how AI works in animal pharma, and a document that will genuinely help the next person who sits in your chair. That's something to be proud of.\n\n## Stretch Goal\n\nPresent your capstone. Even if it's informal, practice the skill of summarizing your work for an audience:\n\n```\n@coop\n\nHelp me prepare a 10-minute presentation of my rotation capstone. I want to present to the CoE team. Structure it as:\n\n- **Slide 1**: Title and rotation overview (30 seconds)\n- **Slide 2**: What the CoE does and my role in it (1 minute — assume some audience members don't know the CoE well)\n- **Slide 3-4**: Top 3 things I learned (2 minutes — pick the most interesting insights, not everything)\n- **Slide 5-6**: My contributions and their impact (2 minutes — show, don't just tell)\n- **Slide 7-8**: Gap analysis highlights (2 minutes — pick the 3 most actionable gaps)\n- **Slide 9**: Recommendations for the next co-op (1 minute)\n- **Slide 10**: What this experience means for my career (30 seconds — end on a personal, genuine note)\n- **Q&A**: 2 minutes\n\nFor each slide, give me:\n- The key message (one sentence)\n- Talking points (2-3 bullets)\n- One thing to avoid (a common presentation mistake for this type of content)\n\nHelp me keep it conversational, not stiff. I want the audience to hear my authentic voice.\n```\n\nSave presentation notes to `personas/coop/workspace/artifacts/capstone/presentation-notes.md`.\n\n---\n\n**Congratulations on completing your co-op rotation modules!** Return to your journey file and complete the Final Reflection. Then head to Module 08 (Capstone) in the shared modules to do the final synthesis. You've earned it.", "variables": [], "notes": "Your rotation capstone serves three audiences:", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/steikould/center_of_excellence_personas", "path": ".github/prompts/coop/co-04-rotation-capstone.prompt.md", "ref": "1872309cfc57f4a821a765ef386508d6be8de68a", "url": "https://github.com/steikould/center_of_excellence_personas/blob/1872309cfc57f4a821a765ef386508d6be8de68a/.github/prompts/coop/co-04-rotation-capstone.prompt.md", "key": "steikould/center_of_excellence_personas/.github/prompts/coop/co-04-rotation-capstone.prompt.md" } } }

co-04-rotation-capstone

About