update 8

Author: UncleBats

docs/workshop/participant-handout.md

@@ -2179,74 +2179,85 @@ Now that you have well-structured sub-issues, you can let Copilot implement them
 
 ---
 
-### Exercise 8: Implementation Workflow
+### Exercise 8: Explore on Your Own
 
-**Use VS Code Copilot Chat with repository agent:**
+You now have all the skills to create, install, and manage agentic workflows. Use the remaining time to try one (or more!) of the following challenges. Pick whatever interests you — there are no step-by-step instructions this time.
 
-1. Type `/agents` and select agentic-workflows agent
-2. Use this prompt:
+---
 
-```
-create a workflow that triggers when someone comments "/implement" on an issue. The workflow should:
+**🔄 Challenge A: Keep Your Workflows Up to Date**
 
-1. Read the issue description and any plans
-2. Create a new branch for the feature
-3. Implement the first task in the plan
-4. Run tests to verify it works
-5. Create a draft pull request
-6. Comment back on the original issue with progress
+Your installed workflows have a `source:` reference in their frontmatter that pins them to a specific commit. Open one of your compiled workflows and look for it:
 
-This enables iterative development triggered by humans.
+```yaml
+source: githubnext/agentics/workflows/issue-triage.md@b0e9cfd3a20372ce7fe0462bb7bbca2272df4a88
 ```
 
-**Then test it:**
+This is like a dependency version — it can go stale. Build a workflow (or use the repository agent) that:
+- Runs weekly
+- Checks each workflow's `source:` reference against the latest version in the remote repository
+- Opens a PR to update outdated workflows
 
-- Comment `/implement` on the Ruby issue
-- Watch the workflow create a branch and start implementation
+Think of it as **Dependabot for your agentic workflows**. Hints: you can use `gh aw add` to re-install a workflow and it will update to the latest version. Diff the before/after to generate a changelog.
 
 ---
 
-### Exercise 9: Reuse Workflows
+**📊 Challenge B: Re-run Your Daily Report**
 
-```bash
-# Add a workflow from the community library
-gh aw add githubnext/agentics/continuous-documentation-updates
+Remember Exercise 1? Your daily-report workflow has been quietly collecting data. Trigger it again now:
 
-# Review what was added
-cat .github/workflows/continuous-documentation-updates.yml
+1. Go to **Actions** → **daily-report** → **Run workflow**
+2. Compare this report to the first one you generated
 
-# Commit
-git add .github/workflows/continuous-documentation-updates.yml
-git commit -m "Add continuous documentation updates"
-git push
-```
+With all the PRs you've merged, issues you've created, and workflows you've added, the report should be **much more interesting** now. It demonstrates how visibility workflows become more valuable over time as repository activity grows.
 
 ---
 
-### Exercise 10: Workflow Maintenance
+**📦 Challenge C: Browse and Install Community Workflows**
 
-**Use VS Code Copilot Chat with repository agent:**
+Explore the community workflow libraries and install something that catches your eye:
 
-1. Type `/agents` and select agentic-workflows agent
-2. Use this prompt:
+- **https://github.com/githubnext/agentics/** — Curated, production-ready workflows
+- **https://github.com/github/awesome-copilot** — Community contributions
 
+```bash
+# Browse what's available
+# Pick a workflow and install it
+gh aw add githubnext/agentics/<workflow-name>
 ```
-create a workflow called "agentics-maintenance" that:
 
-1. Runs weekly
-2. Checks if any workflows in our repository were imported from githubnext/agentics
-3. Compares our versions to the latest versions in the remote repository
-4. If updates are available:
-   - Creates a branch
-   - Updates the workflows
-   - Runs tests to ensure compatibility
-   - Creates a PR with changelog of what changed
-5. Labels PR as "dependencies" and "workflows"
+Some ideas: `continuous-documentation-updates`, `stale-bot`, or any workflow that solves a problem you've seen on your own projects.
 
-This keeps our imported workflows up to date automatically.
-```
+---
+
+**🤖 Challenge D: Assign a Sub-Issue to Copilot**
+
+In Exercise 7, the `/plan` command created sub-issues for the Ruby adventure. Pick one and let Copilot implement it:
+
+1. Open a sub-issue on GitHub
+2. Comment: `@copilot implement this`
+3. Watch Copilot create a branch, write code, and open a PR
+
+This closes the full automation loop: **triage → plan → implement → review**.
+
+---
+
+**🛠️ Challenge E: Build Your Own Workflow from Scratch**
+
+Use any method (CLI, cloud agent, repository agent, or manual) to create a workflow that solves a real problem you've encountered. Some inspiration:
+
+- A `/implement` command that reads an issue and creates a draft PR with an implementation
+- A workflow that checks for stale branches and opens cleanup PRs
+- A weekly summary of open issues grouped by label and priority
+- A workflow that enforces PR conventions (title format, description template, required labels)
+
+---
 
-**Save and commit:** `.github/workflows/agentics-maintenance.yml`
+> **💡 Tip:** Whatever you build, remember the patterns from the workshop:
+> - Start with `safe-outputs` to keep human review in the loop
+> - Use `protected-files: fallback-to-issue` for critical files
+> - Test on your workshop repository before bringing it to production
+> - Check the community libraries first — someone may have already built it
 
 ---