Initial commit
This commit is contained in:
46
commands/create-companion-nb.md
Normal file
46
commands/create-companion-nb.md
Normal file
@@ -0,0 +1,46 @@
|
||||
---
|
||||
description: Create a companion Jupyter notebook for a textbook chapter
|
||||
---
|
||||
|
||||
# Create Companion Notebook
|
||||
|
||||
Generate a Jupyter notebook that accompanies a textbook chapter, allowing students to explore concepts interactively.
|
||||
|
||||
## Process
|
||||
|
||||
1. **Invoke the course-architect agent** to create the notebook
|
||||
2. The agent will:
|
||||
- Ask which course this notebook is for
|
||||
- Load the appropriate course profile
|
||||
- Ask what chapter or topic this accompanies
|
||||
- Generate a notebook that:
|
||||
- Follows the chapter's structure
|
||||
- Includes executable code examples
|
||||
- Uses course-appropriate libraries
|
||||
- Provides interactive explorations
|
||||
- Includes exercises for students to complete
|
||||
|
||||
## What the Agent Does
|
||||
|
||||
The course-architect will:
|
||||
- Create code cells with working examples from the chapter
|
||||
- Add markdown cells explaining concepts
|
||||
- Include visualizations to build intuition
|
||||
- Design exercises that build on examples
|
||||
- Use the technical stack specified in the course profile
|
||||
- Match the complexity to student level
|
||||
|
||||
The agent has access to skills for:
|
||||
- **pedagogy**: Interactive learning principles
|
||||
- **content-templates**: Notebook structure patterns
|
||||
- **courses/{course-name}**: Course-specific tools and libraries
|
||||
|
||||
## Output
|
||||
|
||||
A complete Jupyter notebook (.ipynb format) including:
|
||||
- Markdown cells with explanations
|
||||
- Code cells with working examples
|
||||
- Visualizations and interactive elements
|
||||
- Student exercises (with solutions in comments or separate cells)
|
||||
- Clear instructions and learning objectives
|
||||
- Proper imports and setup
|
||||
233
commands/create-lab-nb.md
Normal file
233
commands/create-lab-nb.md
Normal file
@@ -0,0 +1,233 @@
|
||||
---
|
||||
description: Create a lab assignment Jupyter notebook
|
||||
---
|
||||
|
||||
# Create Lab Notebook
|
||||
|
||||
Generate a Jupyter notebook for a hands-on lab assignment where students apply concepts to solve problems.
|
||||
|
||||
## Interactive Workflow
|
||||
|
||||
This command uses a numbered-option interactive workflow to gather requirements and create the lab notebook.
|
||||
|
||||
### Step 1: Course Selection
|
||||
|
||||
Ask the user which course this lab is for:
|
||||
|
||||
```
|
||||
Which course is this lab for?
|
||||
|
||||
[1] BANA 4080 (Intro to Data Mining - Undergraduate)
|
||||
[2] BANA 6043 (Statistical Computing - Graduate)
|
||||
[3] BANA 7075 (ML in Business - Graduate)
|
||||
|
||||
Please select an option by number:
|
||||
```
|
||||
|
||||
**Course Mappings:**
|
||||
- BANA 4080 → `bana-4080` profile (inherits from `intro-to-data-mining`) - Undergraduate
|
||||
- BANA 6043 → `bana-6043` profile (inherits from `statistical-computing`) - Graduate
|
||||
- BANA 7075 → `bana-7075` profile (inherits from `ml-in-business`) - Graduate
|
||||
|
||||
Load the appropriate course profile and, for BANA 4080, also load the `lab-template-guide` skill.
|
||||
|
||||
### Step 2: Chapter Input
|
||||
|
||||
Ask which chapters the lab should reinforce:
|
||||
|
||||
```
|
||||
Which chapters should this lab reinforce?
|
||||
(Provide chapter numbers or names, e.g., "Chapters 7-9" or "Control Flow, Functions")
|
||||
```
|
||||
|
||||
Read the specified chapters if available to analyze content.
|
||||
|
||||
### Step 3: Topic Confirmation
|
||||
|
||||
Based on the chapters, analyze and present planned topics:
|
||||
|
||||
```
|
||||
Based on [chapters specified], I plan to cover these topics:
|
||||
- [Topic 1 identified from chapter analysis]
|
||||
- [Topic 2 identified from chapter analysis]
|
||||
- [Topic 3 identified from chapter analysis]
|
||||
[- Additional topics as appropriate]
|
||||
|
||||
[1] Accept these topics
|
||||
[2] Add or modify topics
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
|
||||
If option [2], ask:
|
||||
```
|
||||
Please specify additional topics to include or modifications:
|
||||
```
|
||||
|
||||
### Step 4: Dataset Strategy
|
||||
|
||||
Present the dataset plan and ask for confirmation:
|
||||
|
||||
```
|
||||
Dataset plan:
|
||||
- Part A (guided reinforcement): [Primary dataset from chapter readings]
|
||||
- Part B (independent challenges): [Dataset from end-of-chapter exercises]
|
||||
|
||||
[1] Accept these datasets
|
||||
[2] Specify alternative datasets
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
|
||||
If option [2], ask:
|
||||
```
|
||||
Please specify which datasets to use:
|
||||
- Part A dataset:
|
||||
- Part B dataset:
|
||||
```
|
||||
|
||||
### Step 5: Week Number
|
||||
|
||||
Ask what week this lab is for:
|
||||
|
||||
```
|
||||
What week number is this lab for?
|
||||
(Used for filename: XX_wkX_lab.ipynb)
|
||||
```
|
||||
|
||||
### Step 6: Save Location
|
||||
|
||||
Detect if a `lab/` or `labs/` directory exists in the current working directory or nearby. Present options:
|
||||
|
||||
```
|
||||
Where should I save the lab notebook?
|
||||
|
||||
[Suggested path: /path/to/lab/]
|
||||
|
||||
Please provide the directory path (or press Enter to use suggested path):
|
||||
```
|
||||
|
||||
### Step 7: Generate Lab
|
||||
|
||||
**For BANA 4080 labs:**
|
||||
1. Read the template file at `/Users/b294776/Desktop/UC/uc-bana-4080/planning/templates/lab_notebook_template.ipynb`
|
||||
2. Follow the structure exactly as defined in the template
|
||||
3. Replace all `[PLACEHOLDERS]` with appropriate content based on:
|
||||
- Chapters/readings specified
|
||||
- Topics confirmed
|
||||
- Datasets selected
|
||||
- Week number
|
||||
- Course profile and lab-template-guide
|
||||
4. Ensure the 75-minute structure:
|
||||
- Part A: ~30 minutes of guided reinforcement
|
||||
- Class Q&A: ~5-10 minutes
|
||||
- Part B: ~35-40 minutes of independent challenges (6 challenges)
|
||||
- Wrap-up: ~3-5 minutes
|
||||
5. Include:
|
||||
- Clear learning objectives (3-4 items)
|
||||
- Business context for all concepts
|
||||
- Step-by-step instructions for Part A
|
||||
- Progressive challenges for Part B (no starter code, no AI)
|
||||
- Reflection questions
|
||||
- Troubleshooting section
|
||||
6. Save as `XX_wkX_lab.ipynb` in specified directory
|
||||
|
||||
**For BANA 6043 and 7075 labs:**
|
||||
1. Use the general lab template structure from `content-templates/templates.md`
|
||||
2. Adapt to graduate level and course-specific context
|
||||
3. Follow course profile standards
|
||||
4. Save in specified directory
|
||||
|
||||
### Step 8: Completion Message
|
||||
|
||||
Display success message with reminder about TA guide:
|
||||
|
||||
```
|
||||
✅ Lab notebook created successfully!
|
||||
|
||||
Location: [full path to created file]
|
||||
|
||||
Next steps:
|
||||
1. Review the lab notebook and make any necessary edits
|
||||
2. When ready, use `/course-builder:create-ta-guide` to create the TA guidance notebook
|
||||
|
||||
The TA guidance notebook will include:
|
||||
- Complete solutions for all challenges
|
||||
- Teaching guidance for Part A sections
|
||||
- Common student difficulties and hints
|
||||
- Timing and facilitation strategies
|
||||
```
|
||||
|
||||
## What the Agent Does
|
||||
|
||||
The course-architect agent will:
|
||||
|
||||
**Planning Phase:**
|
||||
- Load appropriate course profile based on selection
|
||||
- For BANA 4080: Load lab-template-guide skill
|
||||
- Analyze specified chapters to extract key concepts
|
||||
- Identify topics requiring hands-on practice
|
||||
- Determine appropriate datasets from chapter content
|
||||
- Confirm all details with user using numbered options
|
||||
|
||||
**Content Creation Phase:**
|
||||
- For BANA 4080: Read and use the actual template file
|
||||
- Generate lab following the exact structure required
|
||||
- Fill all placeholders with specific, contextual content
|
||||
- Create Part A with guided examples and "Your Turn" exercises
|
||||
- Create Part B with 6 progressive business-focused challenges
|
||||
- Include appropriate scaffolding for student level
|
||||
- Add business context to every concept and exercise
|
||||
- Ensure timing estimates are realistic
|
||||
|
||||
**Quality Assurance:**
|
||||
- Verify all placeholders are replaced
|
||||
- Ensure learning objectives align with activities
|
||||
- Confirm business context is present throughout
|
||||
- Validate structure matches template requirements
|
||||
- Check that timing adds up to 75 minutes (for BANA 4080)
|
||||
|
||||
## Course-Specific Requirements
|
||||
|
||||
### BANA 4080 (Undergraduate)
|
||||
- **Template:** Must use the provided template file exactly
|
||||
- **Structure:** Part A (30 min) + Q&A (5-10 min) + Part B (35-40 min) + Wrap-up (3-5 min)
|
||||
- **Part A:** Guided reinforcement with TA leading students
|
||||
- **Part B:** 6 independent group challenges with NO starter code, NO AI tools
|
||||
- **Tone:** Encouraging, accessible, builds confidence
|
||||
- **Examples:** Relatable business scenarios for beginners
|
||||
- **TA Guide Required:** Yes, created separately with `/course-builder:create-ta-guide`
|
||||
|
||||
### BANA 6043 & 7075 (Graduate)
|
||||
- **Structure:** Flexible based on course needs
|
||||
- **Tone:** More formal, assumes stronger technical background
|
||||
- **Examples:** Advanced business applications, research scenarios
|
||||
- **Complexity:** Higher mathematical rigor and conceptual depth
|
||||
- **TA Guide:** Optional, based on instructor preference
|
||||
|
||||
## Skills Available to Agent
|
||||
|
||||
The agent has access to:
|
||||
- **pedagogy**: General teaching principles for data science
|
||||
- **content-templates**: Lab notebook structure patterns
|
||||
- **courses/bana-4080**: BANA 4080 course profile and lab-template-guide
|
||||
- **courses/bana-6043**: BANA 6043 course profile
|
||||
- **courses/bana-7075**: BANA 7075 course profile
|
||||
- **courses/intro-to-data-mining**: Base profile for BANA 4080
|
||||
- **courses/statistical-computing**: Base profile for BANA 6043
|
||||
- **courses/ml-in-business**: Base profile for BANA 7075
|
||||
|
||||
## Output
|
||||
|
||||
A complete Jupyter notebook (.ipynb format) including:
|
||||
- Professional header with learning objectives
|
||||
- Setup and data loading
|
||||
- Guided learning sections (Part A for BANA 4080)
|
||||
- Independent practice/challenges (Part B for BANA 4080)
|
||||
- Business context throughout
|
||||
- Reflection and wrap-up
|
||||
- Troubleshooting section
|
||||
- Appropriate complexity for student level
|
||||
- Realistic time estimates
|
||||
|
||||
**Note:** The TA guidance notebook is created separately using the `/course-builder:create-ta-guide` command after the instructor reviews and approves the student lab notebook.
|
||||
287
commands/create-module-overview.md
Normal file
287
commands/create-module-overview.md
Normal file
@@ -0,0 +1,287 @@
|
||||
---
|
||||
description: Create a Canvas module overview document
|
||||
---
|
||||
|
||||
# Create Module Overview
|
||||
|
||||
Generate a Canvas module overview document that summarizes the week's learning objectives, content, and activities.
|
||||
|
||||
## Interactive Workflow
|
||||
|
||||
This command uses a numbered-option interactive workflow to gather requirements and create the module overview.
|
||||
|
||||
### Step 1: Course Selection
|
||||
|
||||
Ask the user which course this module overview is for:
|
||||
|
||||
```
|
||||
Which course is this module overview for?
|
||||
|
||||
[1] BANA 4080 (Intro to Data Mining - Undergraduate)
|
||||
[2] BANA 6043 (Statistical Computing - Graduate)
|
||||
[3] BANA 7075 (ML in Business - Graduate)
|
||||
|
||||
Please select an option by number:
|
||||
```
|
||||
|
||||
Load the appropriate course profile.
|
||||
|
||||
### Step 2: Module Number
|
||||
|
||||
Ask what module/week this overview is for:
|
||||
|
||||
```
|
||||
What module/week number is this overview for?
|
||||
(e.g., 4, 6, 10)
|
||||
```
|
||||
|
||||
### Step 3: Content References
|
||||
|
||||
Ask which content materials to include:
|
||||
|
||||
```
|
||||
Which chapters should be referenced for this module?
|
||||
(Provide chapter numbers or names, e.g., "Chapters 7-9" or "Control Flow, Functions")
|
||||
```
|
||||
|
||||
Then ask:
|
||||
|
||||
```
|
||||
Path to Tuesday lecture slides (or description of lecture topics):
|
||||
(Press Enter to skip if not available)
|
||||
```
|
||||
|
||||
Then ask:
|
||||
|
||||
```
|
||||
Path to Thursday lab notebook (or description of lab activities):
|
||||
(Press Enter to skip if not available)
|
||||
```
|
||||
|
||||
### Step 4: Analyze Content
|
||||
|
||||
Read and analyze the provided materials:
|
||||
- If chapter paths are provided, read the chapters to extract learning objectives and key concepts
|
||||
- If slide path is provided, read the slides to understand lecture structure
|
||||
- If lab path is provided, read the lab to understand hands-on activities
|
||||
- Extract module title from content (e.g., "Control Flow, Iteration, and Functions")
|
||||
- Identify learning objectives (aim for 5-8 measurable objectives)
|
||||
- Extract key concepts and skills for "What You'll Learn This Week"
|
||||
- Summarize Tuesday lecture and Thursday lab activities
|
||||
|
||||
### Step 5: Supplemental Files
|
||||
|
||||
Ask about supplemental files:
|
||||
|
||||
```
|
||||
Are there any supplemental files or materials to include?
|
||||
(e.g., companion notebooks, example code, additional resources)
|
||||
|
||||
[1] No, leave as "TBD"
|
||||
[2] Yes, I'll provide details
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
|
||||
If option [2], ask:
|
||||
|
||||
```
|
||||
Please list the supplemental files and materials to include:
|
||||
(e.g., "Chapter 23 Logistic Regression Notebook: link", "Reading Quiz: Available Monday-Wednesday")
|
||||
```
|
||||
|
||||
### Step 6: Generate Overview
|
||||
|
||||
Using the template at `/Users/b294776/Desktop/UC/uc-bana-4080/planning/templates/module_overview_template.md`, generate the module overview by:
|
||||
|
||||
1. Reading the template file
|
||||
2. Replacing all `{PLACEHOLDERS}` with content extracted from analysis:
|
||||
- `{MODULE_NUMBER}` - Week/module number
|
||||
- `{MODULE_TITLE}` - Descriptive title extracted from content
|
||||
- `{MODULE_TOPIC_BLURB}` - 2-3 paragraph overview connecting technical content to business context
|
||||
- `{LEARNING_OBJECTIVE_X}` - Specific, measurable learning objectives (5-8 items)
|
||||
- `{KEY_POINT_X}` - Concise bullets highlighting skills/concepts from "What You'll Learn"
|
||||
- `{TUESDAY_LECTURE_TITLE}` - Title of Tuesday's lecture
|
||||
- `{TUESDAY_LECTURE_ACTIVITIES}` - 2-4 bullets describing lecture activities
|
||||
- `{THURSDAY_LAB_TITLE}` - Title of Thursday's lab
|
||||
- `{THURSDAY_LAB_ACTIVITIES}` - 2-4 bullets describing lab activities
|
||||
- Supplemental files section (TBD or user-provided content)
|
||||
|
||||
3. Ensure tone is:
|
||||
- Approachable and practical
|
||||
- Business-focused
|
||||
- Encouraging
|
||||
- Concrete with specific examples
|
||||
|
||||
4. Remove all HTML comments and guidance text from the final output
|
||||
|
||||
### Step 7: Present Draft
|
||||
|
||||
Display the complete generated overview to the user:
|
||||
|
||||
```
|
||||
Here's the proposed module overview:
|
||||
|
||||
───────────────────────────────────────────
|
||||
[Full generated overview text]
|
||||
───────────────────────────────────────────
|
||||
|
||||
Does this look good?
|
||||
|
||||
[1] Yes, save this overview
|
||||
[2] No, I'd like to make changes
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
|
||||
If option [2], ask:
|
||||
|
||||
```
|
||||
What changes would you like me to make?
|
||||
```
|
||||
|
||||
Then regenerate with the requested changes and present again.
|
||||
|
||||
### Step 8: Save Location
|
||||
|
||||
When user accepts the overview, ask where to save:
|
||||
|
||||
```
|
||||
Where should I save the module overview?
|
||||
|
||||
[Suggested: /Users/b294776/Desktop/UC/uc-bana-4080/planning/canvas_docs/]
|
||||
|
||||
Please provide the directory path (or press Enter to use suggested path):
|
||||
```
|
||||
|
||||
Then ask for filename:
|
||||
|
||||
```
|
||||
What should I name the file?
|
||||
[Suggested: week{X}_overview.md]
|
||||
|
||||
Please provide the filename (or press Enter to use suggested name):
|
||||
```
|
||||
|
||||
Save the file and display confirmation.
|
||||
|
||||
### Step 9: Completion Message
|
||||
|
||||
```
|
||||
✅ Module overview created successfully!
|
||||
|
||||
Location: [full path to created file]
|
||||
|
||||
The overview includes:
|
||||
- Module topic introduction with business context
|
||||
- {X} learning objectives
|
||||
- "What You'll Learn This Week" summary
|
||||
- Tuesday lecture and Thursday lab descriptions
|
||||
- Supplemental files section
|
||||
|
||||
Next steps:
|
||||
- Review the overview in your editor
|
||||
- Copy and paste into Canvas module page
|
||||
- Add any course-specific formatting or links
|
||||
```
|
||||
|
||||
## What the Agent Does
|
||||
|
||||
The course-architect agent will:
|
||||
|
||||
**Analysis Phase:**
|
||||
- Load appropriate course profile
|
||||
- Read and analyze provided chapters, slides, and lab materials
|
||||
- Extract key learning objectives from content
|
||||
- Identify core concepts and skills
|
||||
- Understand Tuesday lecture structure and activities
|
||||
- Understand Thursday lab structure and activities
|
||||
|
||||
**Content Generation:**
|
||||
- Read the module overview template
|
||||
- Generate engaging 2-3 paragraph module topic introduction
|
||||
- Create 5-8 specific, measurable learning objectives
|
||||
- Write concise, business-focused "What You'll Learn" bullets
|
||||
- Summarize Tuesday lecture activities (2-4 bullets)
|
||||
- Summarize Thursday lab activities (2-4 bullets)
|
||||
- Include supplemental files if provided
|
||||
- Maintain consistent structure across all weeks
|
||||
|
||||
**Quality Assurance:**
|
||||
- Ensure tone is approachable and business-focused
|
||||
- Verify all placeholders are replaced
|
||||
- Check that learning objectives are measurable
|
||||
- Confirm activities are described concretely
|
||||
- Remove all guidance comments
|
||||
- Present for user review before saving
|
||||
|
||||
## Course-Specific Requirements
|
||||
|
||||
### BANA 4080 (Undergraduate)
|
||||
- **Template:** Must use the provided template exactly
|
||||
- **Tone:** Approachable, encouraging, practical
|
||||
- **Business Context:** Strong emphasis on real-world business applications
|
||||
- **Examples:** Concrete, relatable scenarios (customer data, marketing, retail)
|
||||
- **Structure:** Consistent week-to-week format for Canvas
|
||||
|
||||
### BANA 6043 & 7075 (Graduate)
|
||||
- **Tone:** More formal but still engaging
|
||||
- **Business Context:** Advanced applications, research scenarios
|
||||
- **Examples:** Complex business problems, industry case studies
|
||||
- **Structure:** Adapt template to graduate-level expectations
|
||||
|
||||
## Template Structure
|
||||
|
||||
The overview follows this structure:
|
||||
|
||||
1. **Module Title**: Module X Overview: [Topic]
|
||||
2. **Module Topic**: 2-3 paragraphs connecting technical content to business context
|
||||
3. **Learning Objectives** (🎯): 5-8 measurable objectives with action verbs
|
||||
4. **What You'll Learn This Week** (✅): Concise bullet list of key concepts/skills
|
||||
5. **How You'll Practice** (🛠): Tuesday lecture + Thursday lab descriptions
|
||||
6. **Lectures & Other Supplemental Files** (📂): Readings, assessments, notebooks, links
|
||||
|
||||
## Key Principles
|
||||
|
||||
**Content Extraction:**
|
||||
- Learning objectives should align with chapter/lecture/lab content
|
||||
- "What You'll Learn" should be concrete and specific
|
||||
- Practice activities should emphasize hands-on application
|
||||
- Business relevance should be clear throughout
|
||||
|
||||
**Writing Style:**
|
||||
- Use active voice and action verbs
|
||||
- Keep examples concrete and relatable
|
||||
- Emphasize practical application over theory
|
||||
- Maintain encouraging, supportive tone
|
||||
- Connect concepts to career skills
|
||||
|
||||
**Quality Checks:**
|
||||
- All placeholders filled with specific content
|
||||
- No generic or vague statements
|
||||
- Business context present throughout
|
||||
- Consistent with course profile tone and standards
|
||||
- User reviewed and approved before saving
|
||||
|
||||
## Skills Available to Agent
|
||||
|
||||
The agent has access to:
|
||||
- **pedagogy**: General teaching principles for data science
|
||||
- **content-templates**: Template structures and patterns
|
||||
- **courses/bana-4080**: BANA 4080 course profile and standards
|
||||
- **courses/bana-6043**: BANA 6043 course profile
|
||||
- **courses/bana-7075**: BANA 7075 course profile
|
||||
|
||||
## Output
|
||||
|
||||
A complete markdown file ready for Canvas with:
|
||||
- Professional module overview with business context
|
||||
- Clear, measurable learning objectives (5-8 items)
|
||||
- Concise "What You'll Learn" summary
|
||||
- Detailed descriptions of Tuesday and Thursday activities
|
||||
- Supplemental files section (TBD or populated)
|
||||
- Consistent formatting and structure
|
||||
- User-reviewed and approved content
|
||||
- No template comments or guidance text
|
||||
|
||||
The overview should be immediately usable in Canvas with minimal additional editing.
|
||||
215
commands/create-quiz.md
Normal file
215
commands/create-quiz.md
Normal file
@@ -0,0 +1,215 @@
|
||||
---
|
||||
description: Create a reading comprehension quiz based on chapter content
|
||||
---
|
||||
|
||||
# Create Quiz
|
||||
|
||||
Generate a reading comprehension quiz to test student understanding of textbook chapter(s).
|
||||
|
||||
## Purpose
|
||||
|
||||
Creates "reading quizzes" that verify students comprehended key concepts from assigned chapter readings. These quizzes focus on understanding, not memorization, and use business scenarios to bring concepts to life.
|
||||
|
||||
## Process
|
||||
|
||||
1. **Invoke the course-architect agent** to create the quiz
|
||||
2. The agent will:
|
||||
- Ask which course this quiz is for
|
||||
- Load the appropriate course profile
|
||||
- **Ask which chapter(s) to base the quiz on** (e.g., "Chapter 5: Data Visualization")
|
||||
- **Confirm the number of questions** (default: 10 questions, but allow customization)
|
||||
- **Ask for the week number** (e.g., "Week 9") for filename generation
|
||||
- **Ask where to save the quiz** (provide default based on course, allow customization)
|
||||
- Read the specified chapter(s) to understand content and learning objectives
|
||||
- Generate quiz questions that:
|
||||
- Test comprehension of key concepts from the reading
|
||||
- Include business scenario-based questions
|
||||
- Use appropriate question types (multiple choice, true/false, multiple answer, numeric entry)
|
||||
- Match the course's pedagogical style
|
||||
- **Save the quiz** as a markdown file to the specified location
|
||||
|
||||
## Quiz Structure
|
||||
|
||||
Each quiz question must include:
|
||||
|
||||
1. **Question Number and Title** (e.g., "Question 3: Linear Regression Coefficients")
|
||||
2. **Question Type** (Multiple Choice, TRUE/FALSE, Multiple Answer, or Numeric Entry)
|
||||
3. **Scenario** (for scenario-based questions) - Business context that applies the concept
|
||||
4. **Question** - Clear, specific question text
|
||||
5. **Answer Options** - Varies by question type:
|
||||
- Multiple Choice: 4 options (A, B, C, D)
|
||||
- TRUE/FALSE: 2 options (A: TRUE, B: FALSE)
|
||||
- Multiple Answer: 4-5 options with instruction to "Select ALL correct"
|
||||
- Numeric Entry: Blank for student to fill in, with acceptable answer range/precision
|
||||
6. **Correct Answer** - Clearly identified with precision requirements for numeric entries
|
||||
7. **Tip/Hint** - Helpful guidance for wrong answers that:
|
||||
- Doesn't give away the answer
|
||||
- Points to the key concept they need to reconsider
|
||||
- Helps them think through the problem
|
||||
- References relevant parts of the reading
|
||||
- For numeric questions: points to the calculation method or formula needed
|
||||
|
||||
## Question Types Distribution
|
||||
|
||||
For a typical 10-question quiz:
|
||||
- **5-6 Multiple Choice** questions (standard comprehension + scenario-based)
|
||||
- **2-3 TRUE/FALSE** questions (test common misconceptions)
|
||||
- **1-2 Multiple Answer** questions (select ALL correct - tests nuanced understanding)
|
||||
- **0-2 Numeric Entry** questions (test calculation/application skills)
|
||||
|
||||
**Important:** Mix scenario-based questions throughout. At least 40-50% of questions should use business scenarios.
|
||||
|
||||
## What the Agent Does
|
||||
|
||||
The course-architect will:
|
||||
- Read the specified chapter(s) to extract key concepts and learning objectives
|
||||
- Create questions that test understanding, not just recall
|
||||
- Write realistic business scenarios that apply the concepts
|
||||
- Ensure questions match the course's student level and style
|
||||
- Provide helpful tips that guide thinking without revealing answers
|
||||
- Balance question types and difficulty
|
||||
- Avoid questions that are too easy (pure recall) or too trick-y
|
||||
|
||||
The agent has access to skills for:
|
||||
- **pedagogy**: Assessment design principles (test understanding, not memorization)
|
||||
- **content-templates**: Quiz format templates
|
||||
- **courses/{course-name}**: Course-specific context, student level, and learning philosophy
|
||||
|
||||
## Output Format
|
||||
|
||||
A complete quiz markdown file including:
|
||||
|
||||
```markdown
|
||||
# Week [X] Quiz: [Topic Name]
|
||||
|
||||
**Instructions:** This quiz tests your comprehension of Week [X] material including [key topics]. Choose the best answer(s) for each question.
|
||||
|
||||
---
|
||||
|
||||
## Question 1: [Concept Name] ([Question Type])
|
||||
|
||||
**Scenario:** [Business scenario if applicable]
|
||||
|
||||
[Question text]
|
||||
|
||||
A) [Option A]
|
||||
B) [Option B]
|
||||
C) [Option C]
|
||||
D) [Option D]
|
||||
|
||||
**Correct Answer:** [Letter]
|
||||
|
||||
**Tip for wrong answers:** [Helpful guidance that doesn't reveal the answer]
|
||||
|
||||
---
|
||||
|
||||
[Repeat for remaining questions]
|
||||
```
|
||||
|
||||
## Example Question Patterns
|
||||
|
||||
**Scenario-Based Multiple Choice:**
|
||||
```
|
||||
## Question 5: Model Evaluation (Multiple Choice)
|
||||
|
||||
**Scenario:** A retail analytics team builds a sales forecasting model.
|
||||
Training RMSE is $450, but Test RMSE is $1,200.
|
||||
|
||||
What does this suggest?
|
||||
A) The model is ready for deployment
|
||||
B) The model is overfitting
|
||||
C) The model is underfitting
|
||||
D) The test data is bad
|
||||
|
||||
**Correct Answer:** B
|
||||
|
||||
**Tip:** Consider what a large gap between training and test performance indicates about how well the model generalizes to new data.
|
||||
```
|
||||
|
||||
**Concept Application TRUE/FALSE:**
|
||||
```
|
||||
## Question 2: Correlation vs. Causation (TRUE/FALSE)
|
||||
|
||||
**Statement:** If advertising spend and sales have correlation 0.85,
|
||||
we can conclude advertising causes sales increases.
|
||||
|
||||
A) TRUE
|
||||
B) FALSE
|
||||
|
||||
**Correct Answer:** B
|
||||
|
||||
**Tip:** Remember that correlation measures association, not causation.
|
||||
What other factors might explain both variables moving together?
|
||||
```
|
||||
|
||||
**Numeric Entry:**
|
||||
```
|
||||
## Question 8: Calculate Correlation (Numeric Entry)
|
||||
|
||||
**Scenario:** A marketing analyst calculates the covariance between
|
||||
advertising spend and sales as 1,200. The standard deviation of
|
||||
advertising spend is 30 and the standard deviation of sales is 50.
|
||||
|
||||
What is the correlation coefficient? (Round to 2 decimal places)
|
||||
|
||||
Answer: ______
|
||||
|
||||
**Correct Answer:** 0.80
|
||||
|
||||
**Acceptable Range:** 0.79 to 0.81
|
||||
|
||||
**Tip:** Remember the formula: correlation = covariance / (SD of X × SD of Y).
|
||||
Make sure you're dividing, not multiplying the standard deviations.
|
||||
```
|
||||
|
||||
**Multiple Answer:**
|
||||
```
|
||||
## Question 10: Regression Assumptions (Multiple Answer - Select ALL correct)
|
||||
|
||||
Which of these are key assumptions of linear regression?
|
||||
|
||||
A) The relationship between predictors and outcome is linear
|
||||
B) The residuals (errors) are normally distributed
|
||||
C) All predictor variables must be normally distributed
|
||||
D) The variance of residuals is constant
|
||||
E) Residuals are independent of each other
|
||||
|
||||
**Correct Answers:** A, B, D, E
|
||||
|
||||
**Tip:** Linear regression doesn't require predictor variables to be normally
|
||||
distributed, only that the residuals follow a normal distribution.
|
||||
```
|
||||
|
||||
## Save Location
|
||||
|
||||
The agent will ask where to save the quiz and provide a course-specific default:
|
||||
|
||||
**For Intro to Data Mining (BANA 4080):**
|
||||
- Default: `/Users/b294776/Desktop/UC/uc-bana-4080/planning/quizzes/`
|
||||
- Filename format: `week[X]_quiz.md` (e.g., `week9_quiz.md`)
|
||||
|
||||
**For other courses:**
|
||||
- The agent will suggest an appropriate location based on the course profile
|
||||
- Always confirm the save location before writing the file
|
||||
|
||||
**After generation:**
|
||||
1. Show the user the complete quiz content
|
||||
2. Confirm the save location and filename
|
||||
3. Use the Write tool to save the file
|
||||
4. Confirm successful save to the user
|
||||
|
||||
## Important Notes
|
||||
|
||||
- **Chapter-driven:** Always ask which chapter(s) to base the quiz on
|
||||
- **Week number:** Ask for the week number to create proper filename
|
||||
- **Confirm quantity:** Ask to confirm 10 questions (or get desired number)
|
||||
- **Scenario-based:** Mix business scenarios throughout (40-50% of questions)
|
||||
- **Helpful tips:** Guide thinking, don't reveal answers
|
||||
- **Course-appropriate:** Match student level and course style
|
||||
- **Question type variety:** Use all four types (Multiple Choice, TRUE/FALSE, Multiple Answer, Numeric Entry)
|
||||
- **Numeric precision:** For numeric entry questions, always specify:
|
||||
- Required precision (e.g., "rounded to 1 decimal place")
|
||||
- Acceptable answer range to account for rounding differences
|
||||
- Clear calculation context from the scenario
|
||||
- **No coding questions:** Reading quizzes test conceptual understanding and calculations, not coding ability
|
||||
- **Save workflow:** Always confirm save location and filename before writing the file
|
||||
265
commands/create-slides.md
Normal file
265
commands/create-slides.md
Normal file
@@ -0,0 +1,265 @@
|
||||
---
|
||||
description: Create presentation slides for a lecture
|
||||
---
|
||||
|
||||
# Create Slides
|
||||
|
||||
Generate presentation slides for teaching a course topic using the Quarto RevealJS format.
|
||||
|
||||
## Interactive Workflow
|
||||
|
||||
This command uses a numbered-option interactive workflow to gather requirements and create lecture slides.
|
||||
|
||||
### Step 1: Course Detection
|
||||
|
||||
Automatically detect the course based on the current working directory path:
|
||||
|
||||
- Check if the path contains `uc-bana-4080` → BANA 4080
|
||||
- Check if the path contains `uc-bana-6043` → BANA 6043
|
||||
- Check if the path contains `uc-bana-7075` → BANA 7075
|
||||
|
||||
**If course detected:**
|
||||
```
|
||||
Detected course: BANA [X] from directory path
|
||||
Proceeding with [Course Name]...
|
||||
```
|
||||
|
||||
**If no course detected:**
|
||||
```
|
||||
Unable to detect course from directory path.
|
||||
|
||||
Which course are these slides for?
|
||||
|
||||
[1] BANA 4080 (Intro to Data Mining - Undergraduate)
|
||||
[2] BANA 6043 (Statistical Computing - Graduate)
|
||||
[3] BANA 7075 (ML in Business - Graduate)
|
||||
|
||||
Please select an option by number:
|
||||
```
|
||||
|
||||
Load the appropriate course profile.
|
||||
|
||||
### Step 2: Chapter Input
|
||||
|
||||
Ask which chapters the slides should cover:
|
||||
|
||||
```
|
||||
Which chapters should these slides cover?
|
||||
(Provide chapter numbers or names, e.g., "Chapters 7-9" or "Control Flow, Functions")
|
||||
```
|
||||
|
||||
Read the specified chapters if available to analyze content and extract key concepts.
|
||||
|
||||
### Step 3: Week Number
|
||||
|
||||
Ask what week these slides are for:
|
||||
|
||||
```
|
||||
What week number are these slides for?
|
||||
(Used for filename: w[X]_tuesday.qmd)
|
||||
```
|
||||
|
||||
### Step 4: Dataset Confirmation
|
||||
|
||||
Present the dataset plan:
|
||||
|
||||
```
|
||||
Dataset plan for demonstrations:
|
||||
I'll use the primary dataset from the chapter readings for live coding examples.
|
||||
|
||||
[1] Accept this dataset
|
||||
[2] Specify a different dataset
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
|
||||
If option [2], ask:
|
||||
```
|
||||
Please specify which dataset to use for demonstrations:
|
||||
```
|
||||
|
||||
### Step 5: Present Slide Outline
|
||||
|
||||
Analyze the chapters and present a proposed outline:
|
||||
|
||||
```
|
||||
Based on [chapters specified], here's the proposed slide outline:
|
||||
|
||||
Opening & Agenda (5 minutes)
|
||||
├── Week overview and learning objectives
|
||||
└── Connection to course progression
|
||||
|
||||
Review & Warm-Up (10-15 minutes)
|
||||
├── Previous week concept review
|
||||
└── Think-pair-share connection activity
|
||||
|
||||
Main Content (35-45 minutes)
|
||||
├── [Concept 1 Title]
|
||||
│ └── Interactive Activity: [Activity description]
|
||||
├── [Concept 2 Title]
|
||||
│ └── Hands-On Demo: [Demo description]
|
||||
└── [Concept 3 Title]
|
||||
└── Interactive Activity: [Activity description]
|
||||
|
||||
Wrap-Up (10-15 minutes)
|
||||
├── Key takeaways
|
||||
├── Thursday lab preview
|
||||
└── Q&A
|
||||
|
||||
[1] Accept this outline and generate slides
|
||||
[2] Request changes to outline
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
|
||||
If option [2], ask:
|
||||
```
|
||||
What changes would you like to make to the outline?
|
||||
```
|
||||
|
||||
Then regenerate the outline and present again.
|
||||
|
||||
### Step 6: Save Location
|
||||
|
||||
When user accepts the outline, ask where to save:
|
||||
|
||||
```
|
||||
Where should I save the slides?
|
||||
|
||||
[Suggested: Look for slides/ directory or current working directory]
|
||||
|
||||
Please provide the directory path (or press Enter to use suggested path):
|
||||
```
|
||||
|
||||
### Step 7: Generate Slides
|
||||
|
||||
**For BANA 4080 slides:**
|
||||
1. Read the template file at `/Users/b294776/Desktop/UC/uc-bana-4080/planning/templates/tuesday_slide_template.qmd`
|
||||
2. Follow the structure exactly as defined in the template
|
||||
3. Replace all `[PLACEHOLDERS]` with appropriate content based on:
|
||||
- Chapters/readings specified
|
||||
- Week number
|
||||
- Dataset selected
|
||||
- Course profile requirements
|
||||
4. Create interactive think-pair-share activities (3-4 minimum)
|
||||
5. Include hands-on demonstrations with business context
|
||||
6. Add appropriate timers with unique IDs
|
||||
7. Generate visualizations using Mermaid diagrams or Python code where applicable
|
||||
8. Save as `w[X]_tuesday.qmd` in specified directory
|
||||
|
||||
**For BANA 6043 and 7075 slides:**
|
||||
1. Use general slide template structure from `content-templates/templates.md`
|
||||
2. Adapt to graduate level and course-specific context
|
||||
3. Follow course profile standards
|
||||
4. Save in specified directory
|
||||
|
||||
### Step 8: Post-Generation Notes
|
||||
|
||||
After saving the slides, provide notes about elements requiring attention:
|
||||
|
||||
```
|
||||
✅ Slides created successfully!
|
||||
|
||||
Location: [full path to created file]
|
||||
|
||||
📋 Action Items:
|
||||
The following elements may need your attention:
|
||||
|
||||
Images Needed:
|
||||
- [List any image placeholders with slide numbers]
|
||||
- Suggested sources: Create with Mermaid, generate with Python, or source from [suggestions]
|
||||
|
||||
Visualizations Created:
|
||||
- [List Mermaid diagrams or Python-generated visualizations included]
|
||||
|
||||
Custom Content:
|
||||
- [Any sections that may need customization based on specific context]
|
||||
|
||||
Next steps:
|
||||
1. Review the slides in your editor
|
||||
2. Add or create any required images
|
||||
3. Test render the .qmd file to HTML
|
||||
4. Review interactive elements and timers
|
||||
```
|
||||
|
||||
## What the Agent Does
|
||||
|
||||
The course-architect agent will:
|
||||
|
||||
**Analysis Phase:**
|
||||
- Load appropriate course profile based on selection
|
||||
- Read and analyze specified chapters to extract key concepts
|
||||
- Identify 3-4 core concepts for gentle introduction
|
||||
- Map business applications and real-world relevance
|
||||
- Plan hands-on demonstration opportunities
|
||||
|
||||
**Outline Design Phase:**
|
||||
- Design 3-4 think-pair-share activities with business scenarios
|
||||
- Create 1-2 hands-on demonstrations for immediate success
|
||||
- Develop progressive concept flow from familiar to sophisticated
|
||||
- Plan Thursday lab connections and motivation
|
||||
- Present outline for user approval
|
||||
|
||||
**Content Generation Phase:**
|
||||
- For BANA 4080: Read and use the actual template file
|
||||
- Generate slides following the exact structure required
|
||||
- Fill all placeholders with specific, contextual content
|
||||
- Create business scenarios that students find relatable
|
||||
- Develop code demonstrations (using chapter datasets)
|
||||
- Design timer activities with unique IDs
|
||||
- **Prefer Mermaid diagrams or Python-generated visualizations** over external images
|
||||
- Add speaker notes for instructor guidance
|
||||
|
||||
**Quality Assurance:**
|
||||
- Verify all placeholders are replaced
|
||||
- Ensure 3-4 interactive activities included
|
||||
- Confirm business context is present throughout
|
||||
- Validate structure matches template requirements
|
||||
- Check that timing adds up to 60-75 minutes
|
||||
- Note any image placeholders that need attention
|
||||
|
||||
## Course-Specific Requirements
|
||||
|
||||
### BANA 4080 (Undergraduate)
|
||||
- **Template:** Must use the provided template file exactly
|
||||
- **Duration:** 60-75 minutes total
|
||||
- **Structure:** Opening (5 min) + Review (10-15 min) + Main Content (35-45 min) + Wrap-Up (10-15 min)
|
||||
- **Interactive Activities:** Minimum 3-4 think-pair-share activities with timers
|
||||
- **Hands-On Demos:** 1-2 live coding demonstrations using chapter datasets
|
||||
- **Tone:** Gentle introduction, business-focused, success-oriented
|
||||
- **Philosophy:** First exposure to concepts before readings and Thursday lab
|
||||
- **Visualizations:** Prefer Mermaid diagrams and Python-generated charts
|
||||
|
||||
### BANA 6043 & 7075 (Graduate)
|
||||
- **Structure:** Flexible based on course needs
|
||||
- **Tone:** More formal, assumes stronger technical background
|
||||
- **Examples:** Advanced business applications, research scenarios
|
||||
- **Complexity:** Higher mathematical rigor and conceptual depth
|
||||
|
||||
## Skills Available to Agent
|
||||
|
||||
The agent has access to:
|
||||
- **pedagogy**: Presentation and lecture design principles, gentle introduction strategies
|
||||
- **content-templates**: Slide structure patterns
|
||||
- **courses/bana-4080**: BANA 4080 course profile and standards
|
||||
- **courses/bana-6043**: BANA 6043 course profile
|
||||
- **courses/bana-7075**: BANA 7075 course profile
|
||||
|
||||
## Output
|
||||
|
||||
A complete Quarto RevealJS presentation (.qmd format) including:
|
||||
- YAML header with RevealJS configuration
|
||||
- Professional title slide with background image
|
||||
- Opening and agenda slides
|
||||
- Previous week review section with interactive activity
|
||||
- Main content sections with business context
|
||||
- Interactive think-pair-share activities with timers
|
||||
- Hands-on demonstrations with code
|
||||
- Mermaid diagrams or Python-generated visualizations (preferred over external images)
|
||||
- Key takeaways and Thursday lab preview
|
||||
- Wrap-up and Q&A slides
|
||||
- Speaker notes for instructor guidance
|
||||
- Appropriate complexity for student level
|
||||
- Realistic time estimates (60-75 minutes total)
|
||||
|
||||
**Post-Generation Notes:** The agent will provide a list of any image placeholders, visualization elements created, and items requiring instructor attention before finalizing the slides.
|
||||
202
commands/create-ta-guide.md
Normal file
202
commands/create-ta-guide.md
Normal file
@@ -0,0 +1,202 @@
|
||||
---
|
||||
description: Create TA guidance notebook with solutions and teaching strategies
|
||||
---
|
||||
|
||||
# Create TA Guidance Notebook
|
||||
|
||||
Generate a comprehensive TA guidance notebook that provides complete solutions, teaching strategies, and facilitation guidance for a student lab notebook.
|
||||
|
||||
## Interactive Workflow
|
||||
|
||||
### Step 1: Locate Student Lab
|
||||
|
||||
Ask for the path to the student lab notebook:
|
||||
|
||||
```
|
||||
Please provide the path to the student lab notebook:
|
||||
(e.g., /path/to/labs/06_wk6_lab.ipynb)
|
||||
```
|
||||
|
||||
Read the student lab notebook to analyze its structure and content.
|
||||
|
||||
### Step 2: Identify Course
|
||||
|
||||
Based on the lab structure or ask the user:
|
||||
|
||||
```
|
||||
Which course is this TA guide for?
|
||||
|
||||
[1] BANA 4080 (Intro to Data Mining - Undergraduate)
|
||||
[2] BANA 6043 (Statistical Computing - Graduate)
|
||||
[3] BANA 7075 (ML in Business - Graduate)
|
||||
|
||||
Please select an option by number:
|
||||
```
|
||||
|
||||
Load the appropriate course profile.
|
||||
|
||||
### Step 3: Extract Week Number
|
||||
|
||||
Extract the week number from the filename (e.g., `06_wk6_lab.ipynb` → week 6) or ask:
|
||||
|
||||
```
|
||||
What week is this lab for?
|
||||
(Used for filename: ta_guidance_wkX.ipynb)
|
||||
```
|
||||
|
||||
### Step 4: Generate TA Guide
|
||||
|
||||
Create a comprehensive TA guidance notebook with:
|
||||
|
||||
**Section 1: Pre-Lab Preparation**
|
||||
- Overview of learning objectives
|
||||
- Key concepts from the lab
|
||||
- Connection to readings/lectures
|
||||
- Required setup and materials
|
||||
- Common technical issues to anticipate
|
||||
- Grouping strategies (for BANA 4080)
|
||||
|
||||
**Section 2: Part A Teaching Guidance** (for BANA 4080)
|
||||
For each section in Part A:
|
||||
- Teaching objectives for the section
|
||||
- Time allocation
|
||||
- Key points to emphasize
|
||||
- Demonstration strategies
|
||||
- Common student questions and suggested answers
|
||||
- Transition techniques to next section
|
||||
|
||||
**Section 3: Part B Solutions and Facilitation** (for BANA 4080)
|
||||
For each of the 6 challenges:
|
||||
- Challenge overview and learning goal
|
||||
- Complete, well-commented solution code
|
||||
- Alternative approaches students might take
|
||||
- Common errors and debugging strategies
|
||||
- Hints to provide (when and how)
|
||||
- Discussion points for concept reinforcement
|
||||
- Extension ideas for advanced students
|
||||
|
||||
**Section 4: Timing and Pacing Strategies**
|
||||
- Detailed timing breakdown
|
||||
- What to do if running ahead/behind
|
||||
- How to manage different group paces
|
||||
- When to call class back together
|
||||
- Transition management
|
||||
|
||||
**Section 5: Assessment and Wrap-up**
|
||||
- Key concepts students should have mastered
|
||||
- Reflection questions to ask
|
||||
- Connections to upcoming content/homework
|
||||
- What to look for when monitoring student work
|
||||
|
||||
**Section 6: Troubleshooting Guide**
|
||||
- Common technical issues and solutions
|
||||
- Conceptual difficulties and how to address
|
||||
- Group dynamics issues
|
||||
- Backup plans for major problems
|
||||
|
||||
### Step 5: Save Location
|
||||
|
||||
Suggest saving in the same directory as the student lab:
|
||||
|
||||
```
|
||||
Where should I save the TA guidance notebook?
|
||||
|
||||
[Suggested: same directory as student lab]
|
||||
|
||||
Please provide the directory path (or press Enter to use suggested path):
|
||||
```
|
||||
|
||||
Save as `ta_guidance_wkX.ipynb`
|
||||
|
||||
### Step 6: Completion Message
|
||||
|
||||
```
|
||||
✅ TA guidance notebook created successfully!
|
||||
|
||||
Location: [full path to created file]
|
||||
|
||||
The TA guidance includes:
|
||||
- Pre-lab preparation guidance
|
||||
- Part A teaching strategies (section-by-section)
|
||||
- Part B complete solutions (all challenges)
|
||||
- Timing and pacing strategies
|
||||
- Troubleshooting guide
|
||||
|
||||
Review the guidance and customize as needed for your teaching style.
|
||||
```
|
||||
|
||||
## What the Agent Does
|
||||
|
||||
The course-architect agent will:
|
||||
|
||||
**Analysis Phase:**
|
||||
- Read and analyze the student lab notebook
|
||||
- Identify all exercises, challenges, and learning objectives
|
||||
- Extract the lab structure (Part A sections, Part B challenges)
|
||||
- Load appropriate course profile
|
||||
|
||||
**Solution Development:**
|
||||
- Create complete, tested solutions for all challenges
|
||||
- Write well-commented code explaining each step
|
||||
- Identify alternative valid approaches
|
||||
- Document common errors and misconceptions
|
||||
|
||||
**Teaching Guidance Creation:**
|
||||
- Develop section-by-section teaching strategies for Part A
|
||||
- Provide timing guidance and pacing strategies
|
||||
- Suggest when and how to provide hints
|
||||
- Create discussion prompts and check-in questions
|
||||
|
||||
**Quality Assurance:**
|
||||
- Ensure all solutions are complete and tested
|
||||
- Verify timing estimates are realistic
|
||||
- Confirm guidance covers common student difficulties
|
||||
- Check that facilitation strategies are practical
|
||||
|
||||
## Course-Specific Requirements
|
||||
|
||||
### BANA 4080 (Undergraduate)
|
||||
|
||||
**Structure:** Must include all sections listed above
|
||||
|
||||
**Part A Guidance Should Include:**
|
||||
- Step-by-step teaching script for each section
|
||||
- What to write/show on screen
|
||||
- Questions to ask students to check understanding
|
||||
- How to explain concepts in accessible language
|
||||
- When to have students try on their own
|
||||
|
||||
**Part B Solutions Should Include:**
|
||||
- Complete working code for all 6 challenges
|
||||
- Multiple approaches where applicable
|
||||
- Common mistakes students make
|
||||
- Strategic hints (not full solutions) to provide
|
||||
- When to intervene vs. let groups struggle productively
|
||||
- Discussion points after each challenge
|
||||
|
||||
**Timing Guidance:**
|
||||
- Detailed breakdown matching the 75-minute structure
|
||||
- Flexibility strategies for different pacing
|
||||
- What to skip if running behind
|
||||
- Extension activities if running ahead
|
||||
|
||||
### BANA 6043 & 7075 (Graduate)
|
||||
|
||||
**Structure:** More flexible, focus on:
|
||||
- Complete solutions to all exercises
|
||||
- Advanced discussion topics
|
||||
- Connections to research or industry applications
|
||||
- Optional: Teaching strategies if lab is TA-led
|
||||
|
||||
## Output
|
||||
|
||||
A comprehensive Jupyter notebook (.ipynb format) including:
|
||||
- Complete solutions to all lab exercises and challenges
|
||||
- Teaching strategies for guided sections
|
||||
- Timing and pacing guidance
|
||||
- Common student difficulties and how to address them
|
||||
- Facilitation strategies for group work
|
||||
- Troubleshooting guide
|
||||
- Discussion prompts and assessment questions
|
||||
|
||||
The TA guide should be a complete resource that allows a TA to effectively facilitate the lab session even if they haven't taught it before.
|
||||
296
commands/review-chapter.md
Normal file
296
commands/review-chapter.md
Normal file
@@ -0,0 +1,296 @@
|
||||
---
|
||||
description: Reviews a textbook chapter for technical accuracy, clarity, tone, style, and grammar based on course standards.
|
||||
---
|
||||
|
||||
# Review Textbook Chapter
|
||||
|
||||
This command leverages the `course-architect` agent to perform a comprehensive review of a textbook chapter, ensuring it aligns with the specific course's pedagogical standards and style.
|
||||
|
||||
The agent will analyze the chapter based on the detected or selected course profile and provide specific, actionable feedback on:
|
||||
* Technical Accuracy (code & concepts)
|
||||
* Clarity for Beginners (using course profile audience)
|
||||
* Tone Alignment (encouraging, practical, conversational)
|
||||
* Pedagogical Elements (use of callouts, examples, checks)
|
||||
* Sentence Case Compliance (for markdown headings)
|
||||
* Grammar and Flow
|
||||
|
||||
## Interactive Workflow
|
||||
|
||||
### Step 1: Course Detection and Selection
|
||||
|
||||
Attempt to automatically detect the course based on the current working directory path.
|
||||
|
||||
**Agent Action:**
|
||||
* Get the current working directory path (e.g., using `pwd` in Bash).
|
||||
* Check if the path contains `bana-4080`, `bana-6043`, or `bana-7075`.
|
||||
|
||||
**If course detected:**
|
||||
```
|
||||
Detected course: BANA [XXXX] based on the current directory.
|
||||
|
||||
[1] Confirm BANA [XXXX]
|
||||
[2] Select a different course
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
If [1], proceed with the detected course. If [2], show the manual selection prompt below.
|
||||
|
||||
**If no course detected OR user selects [2]:**
|
||||
```
|
||||
Which course is this chapter for?
|
||||
|
||||
[1] BANA 4080 (Intro to Data Mining - Undergraduate)
|
||||
[2] BANA 6043 (Statistical Computing - Graduate)
|
||||
[3] BANA 7075 (ML in Business - Graduate)
|
||||
|
||||
Please select an option by number:
|
||||
```
|
||||
|
||||
**Agent Action (Post-Selection):**
|
||||
* Load the appropriate **course profile** (e.g., `intro-to-data-mining/course-profile.md`).
|
||||
* Load the `pedagogy/teaching-principles.md` skill.
|
||||
|
||||
### Step 2: Chapter Input
|
||||
|
||||
Ask the user for the chapter content file:
|
||||
|
||||
```
|
||||
Please provide the path to the chapter file (.qmd or .md) you want me to review:
|
||||
(e.g., /path/to/book/chapter-5.qmd)
|
||||
```
|
||||
|
||||
**Agent Action:**
|
||||
* Read the full content of the specified file.
|
||||
|
||||
### Step 3: Review and Generate Feedback
|
||||
|
||||
The agent analyzes the entire chapter based on the loaded course profile and pedagogical principles.
|
||||
|
||||
**Agent Actions:**
|
||||
* Load relevant course context from the course profile
|
||||
* Parse the chapter structure (headings, sections, code blocks, callouts)
|
||||
* Evaluate against the following criteria:
|
||||
|
||||
**Review Criteria:**
|
||||
|
||||
1. **Technical Accuracy**
|
||||
- Verify code examples run correctly and follow best practices
|
||||
- Check that concepts are explained accurately
|
||||
- Ensure libraries/functions are used appropriately
|
||||
- Validate that examples align with the course's technical stack
|
||||
|
||||
2. **Clarity for Beginners (Audience-Specific)**
|
||||
- Assess whether explanations match the target audience level (from course profile)
|
||||
- Check for assumed knowledge that hasn't been introduced
|
||||
- Verify that jargon is either avoided or clearly defined
|
||||
- Ensure examples build progressively in complexity
|
||||
|
||||
3. **Tone Alignment**
|
||||
- Verify the tone matches course standards (e.g., conversational, encouraging)
|
||||
- Check that the chapter is practical and business-focused (if applicable)
|
||||
- Ensure the writing is engaging and motivating
|
||||
- Assess whether the chapter reduces anxiety and builds confidence
|
||||
|
||||
4. **Pedagogical Elements**
|
||||
- Verify presence of learning objectives
|
||||
- Check for appropriate use of callouts (tips, warnings, notes)
|
||||
- Assess quality and relevance of examples
|
||||
- Verify inclusion of check-your-understanding questions
|
||||
- Ensure proper spacing of practice opportunities
|
||||
|
||||
5. **Sentence Case Compliance (Headings)**
|
||||
- Check all markdown headings (##, ###, ####) use sentence case
|
||||
- Flag any title case headings
|
||||
- Provide specific examples of violations
|
||||
|
||||
6. **Grammar and Flow**
|
||||
- Check for grammatical errors
|
||||
- Assess logical flow between sections
|
||||
- Verify smooth transitions
|
||||
- Check for consistency in terminology
|
||||
|
||||
### Step 4: Present Feedback Report
|
||||
|
||||
Display the comprehensive review to the user, structured by category.
|
||||
|
||||
```
|
||||
Here is the review for [chapter-file.qmd], evaluated against BANA [XXXX] standards:
|
||||
|
||||
## Overall Assessment
|
||||
|
||||
[Summary paragraph providing high-level evaluation]
|
||||
|
||||
-----
|
||||
|
||||
## 1. Technical Accuracy
|
||||
|
||||
* **Status:** [✅ Excellent / ⚠️ Needs Attention / ❌ Issues Found]
|
||||
* **Feedback:** [Specific points with line numbers or section references]
|
||||
|
||||
-----
|
||||
|
||||
## 2. Clarity for Beginners (Audience: BANA [XXXX])
|
||||
|
||||
* **Status:** [✅ Excellent / ⚠️ Needs Attention / ❌ Issues Found]
|
||||
* **Feedback:** [Specific points with examples]
|
||||
|
||||
-----
|
||||
|
||||
## 3. Tone Alignment (Target: [e.g., Conversational, Encouraging])
|
||||
|
||||
* **Status:** [✅ Excellent / ⚠️ Needs Attention / ❌ Issues Found]
|
||||
* **Feedback:** [Specific points with examples]
|
||||
|
||||
-----
|
||||
|
||||
## 4. Pedagogical Elements
|
||||
|
||||
* **Status:** [✅ Excellent / ⚠️ Needs Attention / ❌ Issues Found]
|
||||
* **Feedback:** [Specific points about callouts, examples, exercises]
|
||||
|
||||
-----
|
||||
|
||||
## 5. Sentence Case Compliance (Headings)
|
||||
|
||||
* **Status:** [✅ Compliant / ❌ Violations Found]
|
||||
* **Feedback:** [List specific headings that need correction]
|
||||
|
||||
-----
|
||||
|
||||
## 6. Grammar and Flow
|
||||
|
||||
* **Status:** [✅ Excellent / ⚠️ Needs Attention / ❌ Issues Found]
|
||||
* **Feedback:** [Specific points about grammar or flow issues]
|
||||
|
||||
-----
|
||||
|
||||
What would you like to do with this feedback?
|
||||
|
||||
[1] Save report as a GitHub Issue
|
||||
[2] Address these issues now (edit chapter)
|
||||
[3] Discard
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
|
||||
### Step 5: Save as GitHub Issue (If user selects [1])
|
||||
|
||||
**Agent Action:**
|
||||
1. Ask for confirmation on the repository (try to infer from the current directory's git remote).
|
||||
```
|
||||
I can create a GitHub issue in the repository associated with this directory: [repo name].
|
||||
|
||||
Issue Title Suggestion: "Chapter Review Feedback: [chapter-file.qmd]"
|
||||
|
||||
[1] Create issue with this title in [repo name]
|
||||
[2] Edit title before creating
|
||||
[3] Cancel
|
||||
```
|
||||
2. If confirmed, format the feedback report from Step 4 into markdown suitable for a GitHub issue body.
|
||||
3. **Create the GitHub issue** using the `gh` CLI tool via Bash:
|
||||
```bash
|
||||
gh issue create --title "Chapter Review Feedback: [chapter-file.qmd]" --body "$(cat <<'EOF'
|
||||
[Formatted feedback report]
|
||||
EOF
|
||||
)"
|
||||
```
|
||||
4. Display confirmation: `✅ GitHub issue created successfully at [link to issue]` or provide fallback instructions if `gh` is not available.
|
||||
|
||||
### Step 6: Address Issues Now (If user selects [2])
|
||||
|
||||
**Agent Action:**
|
||||
1. Ask how the user wants to proceed:
|
||||
```
|
||||
How would you like to address the feedback?
|
||||
|
||||
[1] Address all issues sequentially (guided edits)
|
||||
[2] Focus on specific issues (you tell me where to start)
|
||||
[3] Try to address all issues at once (agent makes edits, you review)
|
||||
[4] Cancel
|
||||
|
||||
Please select an option:
|
||||
```
|
||||
2. **Based on selection:**
|
||||
* **[1] Sequential:**
|
||||
* Go through each feedback point category by category (e.g., starting with Technical Accuracy).
|
||||
* For each issue within a category:
|
||||
- State the specific issue
|
||||
- Propose a fix
|
||||
- Use the Edit tool to make the change to the chapter file
|
||||
- Show the change to the user for approval
|
||||
* Repeat for the next feedback category.
|
||||
* **[2] Specific:**
|
||||
* Ask the user: "Which feedback point (e.g., 'Clarity issue in Section 3.2' or 'Sentence case violation in heading') would you like to address first?"
|
||||
* Follow the same process as Sequential, but only for the user-selected issues.
|
||||
* **[3] All at Once:**
|
||||
* Propose revising the entire chapter based on all feedback points
|
||||
* Use the Edit tool or Write tool to make comprehensive changes
|
||||
* Present a summary of changes made
|
||||
* Ask user to review the updated chapter
|
||||
* **[4] Cancel:** End the workflow.
|
||||
3. After edits (if any) are completed:
|
||||
```
|
||||
✅ Chapter edits based on feedback are complete.
|
||||
|
||||
Would you like to:
|
||||
[1] Review the chapter again to verify improvements
|
||||
[2] Exit
|
||||
```
|
||||
|
||||
### Step 7: Discard (If user selects [3])
|
||||
|
||||
**Agent Action:**
|
||||
* Display confirmation: `Feedback discarded. No changes made.`
|
||||
* End the workflow.
|
||||
|
||||
## What the Agent Does
|
||||
|
||||
The course-architect agent will:
|
||||
|
||||
**Analysis Phase:**
|
||||
- Load appropriate course profile based on selection
|
||||
- Read the entire chapter file
|
||||
- Parse structure and identify all components (headings, code, callouts, etc.)
|
||||
- Gather context about course standards and expectations
|
||||
|
||||
**Review Phase:**
|
||||
- Systematically evaluate each review criterion
|
||||
- Document specific issues with location references (section names, line numbers)
|
||||
- Assess severity of each issue
|
||||
- Compile comprehensive feedback organized by category
|
||||
|
||||
**Reporting Phase:**
|
||||
- Present structured feedback report
|
||||
- Provide status indicators for each category
|
||||
- Include specific, actionable recommendations
|
||||
- Guide user through post-review options
|
||||
|
||||
**Action Phase (if user chooses to address feedback):**
|
||||
- Make precise edits to the chapter file
|
||||
- Maintain original formatting and structure
|
||||
- Apply fixes based on the documented feedback
|
||||
- Verify changes align with course standards
|
||||
|
||||
## Skills Available to Agent
|
||||
|
||||
The agent has access to:
|
||||
- **pedagogy**: Teaching principles and pedagogical best practices
|
||||
- **content-templates**: Chapter and content structure patterns
|
||||
- **courses/bana-4080**: BANA 4080 course profile and standards
|
||||
- **courses/bana-6043**: BANA 6043 course profile and standards
|
||||
- **courses/bana-7075**: BANA 7075 course profile and standards
|
||||
|
||||
## Output
|
||||
|
||||
A comprehensive review report including:
|
||||
- Overall assessment summary
|
||||
- Detailed feedback across six key dimensions
|
||||
- Specific examples and location references
|
||||
- Status indicators (✅/⚠️/❌) for each category
|
||||
- Actionable recommendations
|
||||
- Interactive options for handling feedback (GitHub issue, immediate edits, or discard)
|
||||
|
||||
**Post-Review Actions:**
|
||||
- Optional GitHub issue creation with formatted feedback
|
||||
- Optional guided editing workflow to address feedback
|
||||
- Re-review capability to verify improvements
|
||||
45
commands/write-chapter.md
Normal file
45
commands/write-chapter.md
Normal file
@@ -0,0 +1,45 @@
|
||||
---
|
||||
description: Write a textbook chapter for a data science course
|
||||
---
|
||||
|
||||
# Write Chapter
|
||||
|
||||
Create a textbook chapter tailored to a specific course's audience and learning objectives.
|
||||
|
||||
## Process
|
||||
|
||||
1. **Invoke the course-architect agent** to handle the chapter creation
|
||||
2. The agent will:
|
||||
- Ask which course this chapter is for
|
||||
- Load the appropriate course profile
|
||||
- Ask for the chapter topic
|
||||
- Generate a chapter outline based on course standards
|
||||
- Write the complete chapter with appropriate:
|
||||
- Explanations at the right level
|
||||
- Examples using course-appropriate tools
|
||||
- Exercises and checkpoints
|
||||
- Visual aids and code snippets (if applicable)
|
||||
|
||||
## What the Agent Does
|
||||
|
||||
The course-architect will:
|
||||
- Adapt writing style to the student level (undergrad vs grad)
|
||||
- Use the technical stack specified in the course profile
|
||||
- Follow the course's pedagogical philosophy
|
||||
- Structure content according to learning objectives
|
||||
- Include hands-on examples appropriate for the course
|
||||
|
||||
The agent has access to skills for:
|
||||
- **pedagogy**: Data science teaching principles
|
||||
- **content-templates**: Chapter structure templates
|
||||
- **courses/{course-name}**: Course-specific context and standards
|
||||
|
||||
## Output
|
||||
|
||||
A complete markdown chapter ready to use in your textbook, including:
|
||||
- Learning objectives
|
||||
- Conceptual explanations
|
||||
- Code examples (if applicable)
|
||||
- Visualizations and diagrams
|
||||
- Practice problems
|
||||
- Summary and key takeaways
|
||||
Reference in New Issue
Block a user