@rubytech/taskmaster 1.12.2 → 1.13.0

package/templates/real-agent/skills/content-directory/references/module-delivery.md

@@ -0,0 +1,65 @@
+# Module Delivery
+
+## Purpose
+
+Deliver curriculum modules as interactive coaching conversations, not static content dumps.
+
+## Context to Gather
+
+Before delivering a module:
+1. **What the member asked for** — specific topic, or browsing?
+2. **Their profile context** — career stage, goals, current challenges (from `memory/users/{phone}/profile.md`)
+3. **Their progress** — what they've already completed (from `memory/users/{phone}/progress.md`)
+
+## Where to Search
+
+Search `memory/public/courses/{pillar}/` for module files. Each module is a markdown file with frontmatter:
+
+```yaml
+---
+title: Module Title
+contributor: Contributor Name
+pillar: pillar-name
+estimated_time: X minutes
+access: free
+video: https://pinata-url (optional)
+---
+```
+
+If the member asks for a topic without specifying a module, search across all pillars for the best match.
+
+## How to Deliver
+
+**Never paste the full module.** Teach through conversation:
+
+1. **Introduce** — What the module covers, who it's from, why it matters for this member specifically. Reference their profile context.
+
+2. **Teach the core concept** — Present the key insight or framework. Use the contributor's voice and perspective. "Adam's approach to this is..." or "Steve Backley's framework here is..."
+
+3. **Check understanding** — Ask the member to reflect. "How does this compare to how you currently handle...?" or "What would that look like for your patch?"
+
+4. **Go deeper** — Based on their response, expand on the areas they find most relevant. Skip parts that don't apply to their situation.
+
+5. **Offer the video** — If the module has a video link, offer it at the right moment: "Adam walks through a real example of this — want to watch it?" Don't force it.
+
+6. **Reflection questions** — After the core teaching, offer 2-3 reflection questions that help them apply the concept to their own business.
+
+7. **Bridge to next** — Recommend a logical next module or ask if they want to continue in this pillar.
+
+## Pacing
+
+Don't rush. One concept at a time. Wait for the member to respond before moving to the next section. If they engage deeply with one part, stay there — depth beats breadth.
+
+If a module is long, break it across multiple exchanges. The member controls the pace — "Want to continue?" or "Take your time, I'll be here."
+
+## When Content Doesn't Exist
+
+If a member asks for something not in the curriculum:
+1. Acknowledge the gap honestly: "We don't have a specific module on that yet."
+2. Search memory for anything adjacent that might help.
+3. If nothing exists, note it: "I'll flag this as something the team should consider adding."
+4. Write a brief note to `memory/admin/` so the admin agent can surface it.
+
+## Tone
+
+Expert tutor, not lecturer. You're walking alongside the member through the material, not reading it to them. React to their responses. Build on their experience. Make it personal.

package/templates/real-agent/skills/content-directory/references/progress-tracking.md

@@ -0,0 +1,47 @@
+# Progress Tracking
+
+## Purpose
+
+Maintain an accurate record of each member's learning journey and use it to drive personalised recommendations.
+
+## When to Update Progress
+
+Update `memory/users/{phone}/progress.md` after:
+- A member completes a module (all key concepts covered, reflection done)
+- A coaching session ends
+- A member explicitly asks to bookmark or skip a module
+- You learn something new about their goals or focus area
+
+## What to Record
+
+### Module Completion
+Add to the "Modules Completed" section:
+```
+- [YYYY-MM-DD] {pillar} / {module title}
+```
+
+### Current Focus
+Update the "Current Focus" field when the member shifts topics or starts a new learning path.
+
+### Notes
+Record anything that helps personalise future interactions:
+- Topics they found most valuable
+- Areas they struggled with
+- Specific business context they shared (their patch, their agency focus, their brand positioning)
+
+## How to Use Progress Data
+
+**For recommendations:** Check which pillars they've explored and which they haven't. Suggest unexplored pillars that match their goals. Don't repeat modules they've completed.
+
+**For returning members:** When a member comes back after a gap, check their progress and reference it: "Last time we covered {topic}. Want to continue from there, or is there something new on your mind?"
+
+**For coaching:** Progress data tells you what frameworks the member already knows. In coaching mode, you can reference: "Remember Adam's three questions from the listing presentation module? Apply that here."
+
+## When Members Ask About Progress
+
+Summarise their journey conversationally:
+- How many modules completed, across which pillars
+- Their current focus area
+- Suggested next steps based on goals and gaps
+
+Don't present progress as a report — frame it as a conversation about their journey.

package/templates/tradesupport/agents/admin/BOOTSTRAP.md

@@ -58,7 +58,19 @@ If the admin prefers to do it themselves, direct them to their Taskmaster setup
 
 These keys are optional — the assistant works without them. Don't pressure. If the admin wants to skip this and come back later, that's fine.
 
-## Step 7: Explain What's Next
+## Step 7: Set Up Opening Hours
+
+Let the admin know they can configure **opening hours** so the public assistant only responds during business hours. Outside those hours, customer messages are received silently — no reply, no read receipt — and the owner can handle them manually.
+
+Direct them to the **Opening Hours** page in the control panel (under the Advanced section). From there they can:
+- Enable or disable the opening hours gate
+- Set the business timezone
+- Configure per-day schedules (e.g., Mon–Fri 8am–6pm, Sat 9am–1pm)
+- Mark specific dates as closed (e.g., bank holidays)
+
+This is optional — if they don't set it up, the public assistant responds around the clock. They can also configure this later at any time, or ask you to do it using the `opening_hours` tool.
+
+## Step 8: Explain What's Next
 
 Tell them:
 - They can message anytime to update business info
@@ -66,7 +78,7 @@ Tell them:
 - They (admin) get full access to configure everything
 - You'll learn their business as you go
 
-## Step 8: Complete Setup
+## Step 9: Complete Setup
 
 Once all steps are done, call the `bootstrap_complete` tool (no parameters needed). It will mark setup as complete so this guide never appears again.