> For the complete documentation index, see [llms.txt](https://llm.theparley.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://llm.theparley.org/starting-to-use-it/lunch-and-learn-series/week-2.md).
# Week 2
## Prompt Recipes: Build Your Own Mini-Assistant
***
### MONDAY — Turntable TEAM
**Part 1: Prompt Engineering + Homework Debrief (0-30 min)**
* Share homework experiences: what worked, what failed, why
* Anatomy of effective prompts (role, context, task, format, constraints)
* Iterative refinement techniques
* Getting better outputs through specificity
* Common prompt mistakes and fixes
**Part 2: Build Your Recipe Library (30-60 min)**
* **Activity**: Create 2-3 custom prompt recipes:
* Executive brief generator
* Talking points creator
* "Explain this issue for leadership" template
* Strategic-risk summary
* Participants actively build and test each recipe using AI
* Refine prompts based on results
* Save successful recipes in a shared document
* Share best recipes with the group
**Outcome**: Practical templates ready for immediate leadership communication needs.
### TUESDAY — BOOMBOX CREW
**Part 1: Prompt Engineering + Homework Debrief (0-30 min)**
* Homework review: lessons learned from real applications
* How to structure prompts for consistent results
* Iteration strategies for accuracy
* Using examples to guide AI output
* Troubleshooting poor responses
**Part 2: Build Your Recipe Library (30-60 min)**
* **Activity**: Create 2-3 custom prompt recipes:
* Policy → plain English translator
* Structured memo generator
* Decision-tree extractor
* Minutes → decisions + deadlines
* Participants use AI to develop and test templates
* Iterate to improve quality and consistency
* Build shared recipe collection
* Present favorite recipes to group
**Outcome**: Reliable templates for documentation and process clarity.
### WEDNESDAY — LIMEWIRE LEGENDS
**Part 1: Prompt Engineering + Homework Debrief (0-30 min)**
* Share real-world attempts: successes and failures
* Building prompts that deliver consistent quality
* How to iterate when results aren't quite right
* Tone and style guidance in prompts
* Fixing common prompt problems
**Part 2: Build Your Recipe Library (30-60 min)**
* **Activity**: Create 2-3 custom prompt recipes:
* Project update generator
* Committee summary template
* Stakeholder briefing drafts
* Rewrite for tone ("clear, kind, professional")
* Participants actively create and test recipes with AI
* Refine based on actual outputs
* Compile group recipe library
* Share best practices and examples
**Outcome**: Templates that reduce repetitive communication work.
### THURSDAY — SPOTIFY SQUAD
**Part 1: Prompt Engineering + Homework Debrief (0-30 min)**
* Homework review: what you tried and what you learned
* What makes a prompt effective
* How to improve outputs through refinement
* Giving AI the right context and examples
* Diagnosing why outputs miss the mark
**Part 2: Build Your Recipe Library (30-60 min)**
* **Activity**: Create 2-3 custom prompt recipes:
* Meeting recap generator
* Instruction clarifier
* Professional email drafts
* Turn vague tasks into step-by-step plans
* Participants build and test templates using AI
* Practice and troubleshoot together
* Build shared template collection
* Demonstrate successful recipes
**Outcome**: Organizational tools for clarity and confidence.
### FRIDAY - OFFICE HOURS
Answer any questions from the different cohorts. Only one hour? Maybe two?
### KEY TAKEAWAYS?
| Turntable Team | BOOMBOX CREW | LIMEWIRE LEGENDS | SPOTIFY SQUAD |
|---|
| | | |
| | | |
| | | |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://llm.theparley.org/starting-to-use-it/lunch-and-learn-series/week-2.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.