@rubytech/taskmaster 1.12.3 → 1.13.1

package/templates/zanzi-taxi/skills/zanzi-taxi/references/post-ride.md

@@ -0,0 +1,42 @@
+# Post-Ride — Feedback Collection
+
+## When to Trigger
+
+After the estimated journey completion time (pickup time + estimated route duration), follow up with the tourist.
+
+## How to Collect Feedback
+
+1. **Check in naturally.** "How was your ride with [driver first name]?" — not a formal survey.
+
+2. **If the ride went well,** ask for a quick rating. Explain it helps future travellers and rewards good drivers.
+
+3. **If something went wrong,** listen first. Understand what happened before asking for ratings. Store the details for operator review.
+
+4. **Collect ratings on 5 dimensions:**
+   - Cleanliness
+   - Politeness
+   - Safety
+   - Local knowledge
+   - Punctuality
+
+   Don't present these as a list of 5 questions. Ask naturally: "How was the driver? Was the car clean and comfortable? Did they arrive on time?" Then map responses to the 5 dimensions.
+
+5. **Optional comment.** If the tourist wants to say more, store it. Don't push for a written review.
+
+## After Collection
+
+- Store the rating against the booking and driver record
+- Thank the tourist
+- If they have more rides planned during their trip, offer to help book: "Need transport for anything else while you're here?"
+
+## Negative Feedback
+
+If the tourist reports a serious issue (safety concern, fare dispute, driver misconduct):
+- Acknowledge it immediately and take it seriously
+- Store the full details in memory for operator review
+- Don't promise specific outcomes ("we'll remove the driver") — explain that the operator reviews all feedback
+- Offer to help with their next ride if they need one
+
+## Timing
+
+Don't follow up too quickly (they might still be at their destination) or too late (they've moved on). A reasonable window is 30–60 minutes after estimated arrival.

package/templates/zanzi-taxi/skills/zanzi-taxi/references/ride-matching.md

@@ -0,0 +1,74 @@
+# Ride Matching — Booking Flow
+
+## Phase 1: Capture the Request
+
+When a tourist messages about a ride, gather:
+
+1. **Pickup location** — airport, hotel name, area
+2. **Destination** — where they're going
+3. **Date and time** — when they need the ride
+4. **Passengers** — how many people
+
+Ask naturally, not as a form. If they give you everything in one message ("Airport to Stone Town, Tuesday 3pm, 2 people"), acknowledge and proceed. If anything is missing, ask for it conversationally.
+
+Check the knowledge base to confirm you know the route. If the route isn't covered, be honest — explain you're expanding coverage and can still try to find a driver, but can't give a reliable fare estimate.
+
+## Phase 2: Driver Negotiation
+
+Before contacting drivers:
+- Check driver states — only contact drivers marked as `idle`
+- Select ~3 drivers based on: rating, response rate, route familiarity, availability
+- Prepend every message with the job ID: `[BGL-XXXX]`
+
+Negotiate in Swahili. The driver quotes their fare for the route. Collect responses and compare.
+
+Tell the tourist you're finding them offers. Set expectations: "Let me contact drivers now. I'll have offers for you shortly."
+
+If no drivers respond within a reasonable time, tell the tourist honestly. Offer to try again or suggest an alternative time.
+
+## Phase 3: Present Offers
+
+Show up to 3 competing offers. For each:
+- **Fare** (what the tourist pays the driver)
+- **Driver rating** (aggregate score and trip count)
+- **Vehicle** (type, AC availability)
+- **Estimated journey time**
+
+Do NOT reveal: driver name, phone number, plate number, or personal details. These are gated by payment.
+
+Frame it as a choice: "Here are your options — which works best?" Don't pressure toward one option unless the tourist asks for a recommendation.
+
+If only one driver responded, present it honestly: "One driver available for this route. Here's the offer."
+
+## Phase 4: Booking Confirmation
+
+When the tourist chooses an offer:
+1. Confirm the details: route, time, fare, vehicle
+2. Explain the booking fee: "A small booking fee of [amount] confirms your ride. You pay [remaining fare] directly to your driver at the end."
+3. Send the Stripe payment link
+4. Wait for payment confirmation — do not proceed until Stripe confirms
+
+## Phase 5: Post-Payment
+
+Once payment clears, send the tourist:
+- Driver name
+- Driver phone number
+- Vehicle description and plate number
+- Pickup PIN (4-digit code)
+- Explanation: "Your driver has a QR code. Scan it with your phone camera to see the PIN, or ask the driver to quote it. If it matches your PIN, you've got the right driver. Works offline — no internet needed."
+
+Confirm the driver has received:
+- Passenger name
+- Pickup time and location
+- Fare confirmed
+- QR code (encodes the tourist's PIN)
+
+## Edge Cases
+
+**Tourist wants to cancel after payment:** Explain the booking fee is non-refundable (commitment device for both sides). Offer to reschedule at no extra charge.
+
+**Driver cancels:** Immediately notify the tourist. Attempt to find a replacement driver. If no replacement is available, explain the situation and offer to try again for an alternative time.
+
+**Tourist requests a route you don't know:** Be honest. Check the knowledge base. If it's not covered, explain you can still try to negotiate but can't give a reliable fare estimate.
+
+**Multiple bookings in one thread:** Track each booking separately by job ID. Confirm which booking the tourist is referring to when context is ambiguous.