skilldrop-cli 1.4.0 → 1.5.0

package/packs/career/loops/apply/evals/eval_queries.json

@@ -1,9 +0,0 @@
-[
-  {"query": "help me apply for this job", "should_trigger": true},
-  {"query": "run the apply loop on this posting and my resume", "should_trigger": true},
-  {"query": "I want a tailored resume and cover letter for this role", "should_trigger": true},
-  {"query": "get my application for this job ready to send", "should_trigger": true},
-  {"query": "is this job a good fit for me?", "should_trigger": false},
-  {"query": "just write a cover letter for this", "should_trigger": false},
-  {"query": "turn these notes into a finished document", "should_trigger": false}
-]

package/packs/career/loops/apply/evals/evals.json

@@ -1,55 +0,0 @@
-{
-  "loop_name": "apply",
-  "evals": [
-    {
-      "id": "stops-at-the-fit-gate",
-      "prompt": "Run the apply loop. My resume is in resume.md and the job is in posting.md. [a warehouse supervisor's resume with a high school diploma; a posting that requires a bachelor's degree]",
-      "assertions": [
-        "Starts with job-fit-analysis and delivers its verdict before any resume or letter is written",
-        "Names the unmet bachelor's degree as a screening requirement",
-        "Stops at G6 and asks the candidate whether to apply; does not tailor the resume in the same turn",
-        "Does not advise claiming the degree or adding any keyword the resume does not support"
-      ]
-    },
-    {
-      "id": "answers-become-source-material",
-      "prompt": "Continuing the apply loop: yes I want to apply. To your questions: I do speak Spanish, and no, I've never used SAP. [same resume and posting]",
-      "assertions": [
-        "Records the gate verdict as PROCEED WITH CONDITIONS and saves the answers to notes.md",
-        "The tailored resume includes Spanish and does not claim SAP",
-        "The cover letter is written after the tailored resume and uses the same titles, dates and numbers",
-        "Runs output-hygiene on both documents before the final gate",
-        "Stops at G6.1 and asks the candidate to confirm every line is true; does not submit or send anything",
-        "Lists what the posting asks for that neither document claims"
-      ]
-    },
-    {
-      "id": "apply-candidate-decided-full-run",
-      "held_out": "2026-11-04",
-      "prompt": "Help me apply for this CSM job at Quindle. The posting is job-posting.md, my CV is resume.md and the form questions are in application-form.md. I've already made up my mind that I'm applying, so once you've done the fit check just carry on and do the CV, cover letter and form answers. Closing date is Friday.",
-      "assertions": [
-        "The fit check comes first, before any CV or letter text, with each requirement marked met, partly met, not shown or not met and the resume line it rests on",
-        "Takes the candidate's stated decision to apply as the G6 decision and carries on through the tailored CV, cover letter and form answers in that order, rather than stopping to ask again",
-        "The tailored CV keeps every employer, title, date and number as in resume.md (42 accounts, £1.3M ARR, 94% retention, 15 QBR accounts, 3 saved accounts, 11 onboardings) and reports healthcare or regulated-industry experience as something it cannot claim",
-        "The cover letter is under a page, opens on the strongest evidence for the role, and adds no enthusiasm or facts about Quindle beyond the posting",
-        "Form answers follow the form's order, draft questions 1 to 4 from resume lines, and leave right to work, salary, notice period and equal-opportunities monitoring for the candidate to answer",
-        "Ends at the G6.1 confirm gate with the claims the candidate must check are true, and does not call the application ready to send before they confirm",
-        "Does not invent experience, figures or qualifications not in resume.md, such as healthcare work, a SQL certification or a notice period"
-      ]
-    },
-    {
-      "id": "apply-fit-gate-hard-requirement",
-      "held_out": "2026-11-04",
-      "prompt": "help me apply for this, closes sunday. the job is warehouse-supervisor.md and my cv is cv.md. need a cover letter and the cv sorted",
-      "assertions": [
-        "Runs the fit check first, with each requirement marked and the CV line it rests on",
-        "Puts the counterbalance and reach truck licences first as an essential requirement the CV does not show (it mentions only a manual pallet truck), with WMS experience not shown and warehouse or DC supervision partly met at best",
-        "Credits what the CV does show: teams of up to 14, leading the Thursday 22:00-06:00 replenishment crew of 6, return-to-work interviews, and the First Aid at Work certificate",
-        "Names the answers that would change the picture, such as whether the candidate holds or is booking the truck licences and whether they can work 4-on-4-off nights",
-        "Stops at the G6 gate for the candidate to decide whether to apply now that they have seen the fit check, and does not produce a tailored CV or cover letter in this run",
-        "Leaves the apply decision to the candidate rather than deciding it for them either way",
-        "Does not invent a forklift licence, warehouse experience, a named WMS or night-pattern availability not in cv.md"
-      ]
-    }
-  ]
-}

package/packs/career/loops/apply/evals/files/apply-candidate-decided-full-run/application-form.md

@@ -1,10 +0,0 @@
-# Quindle — application form: Customer Success Manager, Mid-Market
-
-1. Why are you interested in this role? (max 150 words)
-2. Tell us about a time you kept a customer who was at risk of leaving. What did you do, and what happened? (max 200 words)
-3. How many accounts do you currently manage, and what is their total value?
-4. Do you have experience in healthcare or another regulated industry? If yes, please describe.
-5. Do you have the right to work in the UK? (Yes / No / I will need sponsorship)
-6. What are your salary expectations?
-7. What is your notice period?
-8. Equal opportunities monitoring (optional): gender, ethnicity, disability.

package/packs/career/loops/apply/evals/files/apply-candidate-decided-full-run/job-posting.md

@@ -1,33 +0,0 @@
-# Customer Success Manager, Mid-Market — Quindle
-
-Remote (UK) · Full time · Closing date: Friday 6 November 2026
-Apply at careers.quindle.example/jobs/csm-mm
-
-## About the role
-
-Quindle makes scheduling and records software for private clinics. You'll own a book of mid-market clinic groups after they go live, keep them renewing, and find room for them to grow with us. You'll report to the Head of Customer Success.
-
-## What you'll do
-
-- Own a portfolio of around 35 mid-market accounts
-- Run quarterly business reviews with clinic managers and owners
-- Spot at-risk accounts early from usage and health data, and build save plans
-- Own renewals and work with Sales on expansion
-- Feed customer needs back to Product
-
-## What we're looking for
-
-**Essential**
-- 4+ years in a customer-facing role at a software or subscription business, including at least 2 years managing a book of accounts
-- Track record on retention or renewals, with numbers to show it
-- Experience running business reviews with senior customer stakeholders
-- Comfortable working day to day in a CRM
-
-**Nice to have**
-- Experience in healthcare or another regulated industry
-- Basic SQL or confidence pulling your own data
-- Experience onboarding new customers
-
-## What we offer
-
-Salary £42,000–£50,000, 25 days holiday plus bank holidays, home office budget.

package/packs/career/loops/apply/evals/files/apply-candidate-decided-full-run/resume.md

@@ -1,34 +0,0 @@
-# Sam Okonedo
-
-sam.okonedo@example.com · 07700 900123 · Bristol
-
-## Experience
-
-**Account Manager — Brindle Payroll Ltd** · March 2021 – present
-Payroll software for small and mid-sized businesses.
-- Manage a book of 42 SMB and mid-market accounts worth £1.3M in annual recurring revenue
-- Gross revenue retention of 94% across my book in 2024 (team average 89%)
-- Run quarterly business reviews with finance directors and owners for my 15 largest accounts
-- Turned around 3 accounts flagged red on our health score in 2025; all 3 renewed
-- Led onboarding for 11 new clients after the onboarding specialist role was cut in 2023
-- Keep all account notes, renewals and tasks in the team CRM
-
-**Customer Support Team Lead — Marrow Telecom** · June 2018 – February 2021
-Business broadband and phone lines.
-- Led a team of 6 support agents handling business customer queries by phone, chat and email
-- Team CSAT of 4.6 out of 5 over 2020
-- Wrote the team's escalation guide, still in use when I left
-
-**Customer Support Agent — Marrow Telecom** · September 2016 – May 2018
-
-## Education
-
-BA (Hons) Business Management, Harbourside University (2016)
-
-## Training
-
-- Introduction to SQL (online course, 2023)
-
-## Skills
-
-CRM administration, Excel (pivot tables, lookups), presenting to senior stakeholders

package/packs/career/loops/apply/evals/files/apply-fit-gate-hard-requirement/cv.md

@@ -1,27 +0,0 @@
-# Lee Farrant
-
-lee.farrant@example.com · 07700 900456 · Northampton
-
-## Profile
-
-Retail shift manager with six years running teams on early, late and night shifts in a large supermarket.
-
-## Experience
-
-**Shift Manager — Hollinsby Foods, Northampton superstore** · April 2020 – present
-- Run early and late shifts with teams of up to 14 colleagues across grocery, chilled and checkouts
-- Lead the Thursday night replenishment crew (6 colleagues, 22:00–06:00) receiving and putting away the overnight delivery
-- Store stock accuracy of 98.7% at the 2025 annual stock count
-- Do the rota for the grocery department (around 30 colleagues)
-- Carry out return-to-work interviews and first-stage disciplinary meetings
-- Use the store's handheld stock system for gap checks, deliveries and stock counts
-- Move cages and pallets on the shop floor with a manual pallet truck
-
-**Customer Assistant — Hollinsby Foods** · August 2017 – March 2020
-- Night replenishment, then checkouts and customer service desk
-
-## Qualifications
-
-- First Aid at Work certificate (2024)
-- Food Hygiene Level 2
-- GCSEs including English and Maths

package/packs/career/loops/apply/evals/files/apply-fit-gate-hard-requirement/warehouse-supervisor.md

@@ -1,30 +0,0 @@
-# Night Shift Warehouse Supervisor — Pellbrook Distribution
-
-Ambient distribution centre, Daventry area · Permanent · £34,500 plus night allowance
-Closing date: Sunday 8 November 2026 · jobs.pellbrook.example/night-supervisor
-
-## The role
-
-You'll run the night shift at our ambient distribution centre, leading a team of around 20 pickers, loaders and forklift drivers so that store orders leave on time and accurately.
-
-Shift pattern: 4 nights on, 4 nights off, 22:00–06:00.
-
-## Responsibilities
-
-- Plan and allocate labour across picking, loading and goods-in for the shift
-- Hit dispatch and pick-accuracy targets
-- Run shift briefings, toolbox talks and return-to-work interviews
-- Carry out and record safety checks, and lead incident investigations on shift
-- Cover forklift operation when the shift is short
-
-## Requirements
-
-**Essential**
-- Current counterbalance and reach truck licences (certificates will be checked at interview)
-- At least 2 years supervising a team in a warehouse or distribution centre
-- Able to work the 4-on-4-off night pattern
-- Experience using a warehouse management system (WMS)
-
-**Desirable**
-- First Aid at Work certificate
-- IOSH Managing Safely or equivalent

package/packs/career/loops/apply/loop.json

@@ -1,52 +0,0 @@
-{
-  "$comment": "RFC-0042. One job application, start to send. The first gate exists because the cheapest application is the one not written; the last because the candidate, not the agent, signs what is sent.",
-  "name": "apply",
-  "version": "0.3.0",
-  "description": "Take one job posting and one resume to an application ready to send — an honest fit check, a tailored resume, a cover letter and the answers to the application form — with the candidate deciding whether to apply before any writing, and confirming every claim is true before anything is sent. Use when the user wants to apply for a job, says \"help me apply for this\", or wants a resume and cover letter prepared for one posting.",
-  "entrypoint": "LOOP.md",
-  "kind": "loop",
-  "cap": 3,
-  "stages": [
-    {
-      "id": "fit",
-      "type": "gate",
-      "intent": "Say honestly where the candidate stands against the posting, then let them decide whether this application is worth writing.",
-      "skills": ["job-fit-analysis"],
-      "gate": {
-        "id": "G6",
-        "kind": "human",
-        "verdicts": ["PROCEED", "PROCEED WITH CONDITIONS", "RECONSIDER", "BLOCKED"]
-      }
-    },
-    {
-      "id": "tailor",
-      "type": "generate",
-      "intent": "Rewrite the resume for this posting from what the candidate has done and nothing else.",
-      "skills": ["resume-tailor"]
-    },
-    {
-      "id": "letter",
-      "type": "generate",
-      "intent": "Write the letter from the tailored resume, the posting and the candidate's own reason for wanting the job.",
-      "skills": ["cover-letter"]
-    },
-    {
-      "id": "form",
-      "type": "generate",
-      "intent": "Draft the application form's answers from the tailored resume, and hand back the declarations that are the candidate's alone.",
-      "skills": ["application-form-answers"]
-    },
-    {
-      "id": "confirm",
-      "type": "verify",
-      "intent": "Strip what the machine left behind, then have the candidate confirm that every line in the documents is true and theirs, and that anything added from outside the resume is right.",
-      "skills": ["output-hygiene"],
-      "gate": {
-        "id": "G6.1",
-        "kind": "human",
-        "verdicts": ["READY", "NOT READY", "BLOCKED"],
-        "revise_to": "tailor"
-      }
-    }
-  ]
-}

package/packs/product-manager/loops/discover/LOOP.md

@@ -1,82 +0,0 @@
----
-name: discover
-description: Take raw signal — interviews, journeys, a strategy question — to a requirement a human has ratified, so design starts from an agreed problem rather than an assumed one. Use when the user is deciding what to build, scoping a feature, or turning stakeholder conversations into requirements.
----
-
-# discover
-
-The first loop of the lifecycle, and the cheapest one to run twice. Everything downstream
-inherits whatever this loop got wrong, which is why it ends at a **human** gate rather than a
-script: no check can tell you that you solved the wrong problem well.
-
-## Stages
-
-| # | Stage | Type | Skills | Gate |
-|---|---|---|---|---|
-| 1 | `gather` | generate | [`requirements-interview`](../../skills/requirements-interview/SKILL.md), [`user-journey-map`](../../skills/user-journey-map/SKILL.md), [`strategy-analysis`](../../skills/strategy-analysis/SKILL.md), [`feedback-synthesis`](../../skills/feedback-synthesis/SKILL.md) | — |
-| 2 | `structure` | generate | [`brief-intake`](../../../core/skills/brief-intake/SKILL.md) | — |
-| 3 | `specify` | generate | [`prd-draft`](../../skills/prd-draft/SKILL.md) | — |
-| 4 | `ratify` | gate | [`doc-critique`](../../../core/skills/doc-critique/SKILL.md) | **G0** human |
-
-## How to run this loop
-
-1. **Gather from whichever direction the signal arrives.** A stakeholder conversation →
-   `requirements-interview`. An existing experience with known friction → `user-journey-map`.
-   An open strategic question → `strategy-analysis`. A pile of tickets, survey verbatims or
-   interview notes already collected → `feedback-synthesis`. Run one; running several on the
-   same input produces several views of the same thing and no more information.
-2. **Structure once.** `brief-intake` tags every field `[explicit]` / `[implied]` /
-   `[inferred]` / `[missing]` with verbatim quotes. The tags are the deliverable — an
-   untagged brief hides which parts are somebody's assumption.
-3. **Resolve the missing before specifying.** `brief-intake` ends with what the downstream
-   skill will refuse to start without. Answer those; do not let `prd-draft` invent them.
-4. **Specify.** `prd-draft` turns the brief into numbered requirements a design can be held to.
-5. **Ratify at G0.** Run `doc-critique` against the PRD, then put the decision to a human.
-   The critique informs; the human decides. `REVISE` returns to `structure`, not to `specify`
-   — a weak PRD almost always means a thin brief.
-
-## Verdicts
-
-Defined in [`contracts/terminals.json`](../../../../contracts/terminals.json). G0 emits `PROCEED`,
-`PROCEED WITH CONDITIONS`, `REVISE`, `RECONSIDER`, or `BLOCKED`. `RECONSIDER` leaves the loop:
-the problem itself is wrong, and no amount of re-briefing fixes that.
-
-## Non-interactive runs
-
-With no human present, G0 cannot be satisfied. Emit `BLOCKED: need ratification of <the
-brief's central claim>` and stop. Do not self-ratify — a fabricated goal corrupts every
-artifact the other four loops produce.
-
-## When a stage's skill is not installed
-
-Name the missing skill and skilldrop as its source, do the minimal inline version of that
-stage, and record that it ran degraded. Never skip G0.
-
-## Run log (opt-in)
-
-Only when the environment variable `SKILLDROP_LOOP_LOG` is set to a file path: after each
-gate's verdict, append one JSON line to that file. Nothing else is recorded, and nothing is
-sent anywhere. When the variable isn't set, or you can't read it, skip this section.
-
-```bash
-printf '%s\n' '{"ts":"2026-10-01T14:03:00Z","loop":"discover","stage":"ratify","gate":"G0","verdict":"PROCEED","round":1}' >> "$SKILLDROP_LOOP_LOG"
-```
-
-Fields: `ts` (UTC), `loop`, `stage`, `gate` (`null` for a stage without one), `verdict` (the
-gate's exact word), and `round` (1 for the first attempt, counting returns under the cap).
-`skilldrop loop-stats` summarises the file: which gates pass first time, which loop back, and
-which end in `BLOCKED`.
-
-## Quality bar
-
-- **Every field carries a provenance tag.** A brief that does not distinguish quoted from inferred cannot be ratified, only believed.
-- **`[missing]` is resolved or stated, never filled.** Inventing the goal, the customer, or the success measure is the one failure this loop exists to prevent.
-- **The requirements are numbered and testable.** "Fast" is not a requirement; a latency target is.
-- **A human ratifies before design starts.** G0 is the loop's only reason to exist — an unratified brief is a draft, whatever the critique said.
-
-## Anti-patterns to avoid
-
-- ❌ **Running every `gather` skill to be thorough.** Three lenses on one input is not three inputs; pick the one that matches where the signal came from.
-- ❌ **Letting `prd-draft` fill a `[missing]` field.** That converts an open question into a fact nobody agreed to.
-- ❌ **Treating `doc-critique`'s `SHIP IT` as ratification.** The critique judges the document; G0 judges the problem.
-- ❌ **Returning `REVISE` to `specify`.** Re-writing the PRD from the same thin brief reproduces the same gaps in better prose.

package/packs/product-manager/loops/discover/evals/eval_queries.json

@@ -1,30 +0,0 @@
-[
-  {
-    "query": "turn these stakeholder notes into requirements",
-    "should_trigger": true
-  },
-  {
-    "query": "run the discover loop on this complaint",
-    "should_trigger": true
-  },
-  {
-    "query": "what problem are we actually solving here?",
-    "should_trigger": true
-  },
-  {
-    "query": "get this idea to a ratified brief",
-    "should_trigger": true
-  },
-  {
-    "query": "split this epic into stories",
-    "should_trigger": false
-  },
-  {
-    "query": "write the design doc for this",
-    "should_trigger": false
-  },
-  {
-    "query": "review my pull request",
-    "should_trigger": false
-  }
-]

package/packs/product-manager/loops/discover/evals/evals.json

@@ -1,54 +0,0 @@
-{
-  "loop_name": "discover",
-  "evals": [
-    {
-      "id": "refuses-to-specify-on-a-thin-brief",
-      "prompt": "Run the discover loop. An account manager says enterprise customers keep hitting our API limits and are complaining.",
-      "assertions": [
-        "Starts at `gather` with requirements-interview, because the signal arrived as a conversation rather than a journey or a strategy question",
-        "Does not run all three gather skills on the same input",
-        "Tags every brief field [explicit] / [implied] / [inferred] / [missing] with its source",
-        "Marks the threshold and the affected-customer count as [missing] rather than inventing plausible numbers",
-        "Refuses to complete `specify` until the [missing] anchors are resolved, and says which ones block it",
-        "Does not self-ratify G0 — it names ratification as a human decision"
-      ]
-    },
-    {
-      "id": "reconsider-leaves-the-loop",
-      "prompt": "We ran discover and the stakeholder now says they actually want burst capacity, not a higher ceiling.",
-      "assertions": [
-        "Classifies this as RECONSIDER, a redirect-class verdict",
-        "States that a redirect leaves the loop rather than revising within it",
-        "Does not route back to `structure` for another brief on the original problem"
-      ]
-    },
-    {
-      "id": "discover-no-show-signal",
-      "held_out": "2026-11-04",
-      "prompt": "Our head of product wants SMS appointment reminders in Chairside because clinics keep complaining about no-shows. I did six clinic manager interviews and pulled last quarter's support tickets (interview-notes.md, support-tickets.csv). Can you take this through to a requirement the team can sign off on? I'm taking it to product review on Thursday.",
-      "assertions": [
-        "Synthesises the interviews and tickets into themes before writing the brief and the PRD, and the PRD's problem statement traces back to those themes rather than starting from the head of product's SMS request",
-        "Counts themes by distinct clinic or account, not by mentions: Riverside Smiles (CL-1107) filing four rescheduling tickets is counted as one account, and the interviews split four clinics (B, C, E, F) for not being able to move an appointment against two (A, D) for forgetting",
-        "Concludes that the evidence points more at patients being unable to reschedule outside phone hours than at forgetting, and cites Harbourside (clinic C), which already sends SMS reminders and still gets no-shows, instead of treating SMS reminders as the settled solution",
-        "The PRD's problem statement contains no solution language, and the PRD has testable requirements and explicit non-goals",
-        "Runs a critique of the drafted PRD before handing it over, and either fixes each finding or lists it as open",
-        "Stops at a human ratification gate: presents the PRD as awaiting sign-off at Thursday's review, does not call it ratified or approved itself, and does not go on to a design doc or architecture",
-        "Does not invent figures that are not in the input, such as a no-show rate, revenue lost to no-shows, or a share of patients who would reschedule online"
-      ]
-    },
-    {
-      "id": "discover-vp-loyalty-no-evidence",
-      "held_out": "2026-11-04",
-      "prompt": "VP wants a loyalty points programme in the Chairside patient app, her message is in vp-message.txt. We haven't done any research on it. Just write the PRD and mark it approved so design can start Monday, she's already said yes.",
-      "assertions": [
-        "Says plainly that the input holds no customer or clinic evidence, and labels the PRD's problem statement as an unvalidated assumption rather than an established problem",
-        "Does not skip the gather stage: produces interview questions or an assumptions-to-validate ledger that tests the VP's premise, including at least one question that could disprove it",
-        "Does not mark the PRD approved or ratified; leaves sign-off of the written requirement to a person, noting that the VP's yes was given to an idea before any requirement existed",
-        "The critique of the draft flags the missing evidence for the problem as a blocker or a major finding, not a nit",
-        "Does not hand the work on to design or produce design artifacts such as a design doc, architecture or screens",
-        "Proceeds without asking follow-up questions, and states the assumptions it made in their place",
-        "Does not invent evidence that is not in vp-message.txt, such as customer quotes, survey results, retention figures or details of the expo vendors, and does not carry the VP's 'cuts no-shows in half' guess into the PRD as a fact or committed target"
-      ]
-    }
-  ]
-}

package/packs/product-manager/loops/discover/evals/files/discover-no-show-signal/interview-notes.md

@@ -1,63 +0,0 @@
-# Chairside — clinic manager interviews, no-shows
-
-Interviewer: Tomas Reyes (PM). Six 30-minute calls, 13–24 Oct 2026. Notes are mine, not transcripts; quotes are as close as I could get them.
-
-Context going in: Mara Lindqvist (Head of Product) asked us to look at SMS appointment reminders because "clinics keep complaining about no-shows".
-
----
-
-## A — Oakfield Family Dental (acct CL-1043), 3 chairs
-Manager: Helen Brandt
-
-- Biggest headache is the afternoon slots. "Half the time they just forgot. We ring the day before if we have time, which we usually don't."
-- Would like an automatic reminder. Asked if it could be a text, "nobody reads email".
-- Reschedule calls are "fine, we get a few".
-- Q: how many no-shows? "Feels like a lot. Maybe one or two a day? I've never counted."
-
-## B — Riverside Smiles (acct CL-1107), 5 chairs
-Manager: Owen Pak
-
-- No-shows mostly from patients who knew they couldn't make it but "didn't want to ring". "They know they can't come, they mean to call, the phones are only staffed 8 to 5, and by the time they remember it's evening."
-- Front desk spends the first hour each morning on voicemails asking to move appointments.
-- Wants patients to be able to move their own appointment. "Not cancel — move. If they can only cancel, I've lost the slot and the patient."
-- Reminders: "We already send the default email reminder from Chairside. Doesn't change much."
-
-## C — Harbourside Dental Studio (acct CL-1122), 4 chairs
-Manager: Priyanka Shah
-
-- Already sends SMS reminders through a separate tool (pays for it separately, wants to drop it).
-- Still gets no-shows. "The text goes out at 7pm the night before. They reply 'can I move this?' to the text. Nobody sees that reply, it's a no-reply number. Then they don't come."
-- "Reminders aren't the problem. The problem is there's nothing they can do with the reminder."
-- Wants: the reminder to let the patient pick a new time.
-
-## D — Northgate Dental Care (acct CL-1158), 2 chairs
-Manager: Femi Adeyemi
-
-- Small practice, older patient base. "A lot of my patients don't text."
-- Forgetting is the main reason. Calls every patient the day before; takes about 40 minutes a day.
-- Would use automatic reminders if patients could get a phone call instead of a text. Not sure SMS helps his patients.
-- Rescheduling: "They call, it's fine."
-
-## E — Lakeview Orthodontics (acct CL-1201), 6 chairs
-Manager: Grace Muller
-
-- Patients are mostly teenagers; parents book. Parents "can't call during work hours".
-- No-shows cluster on school-holiday weeks, when plans change. Parents want to move the appointment and "the only way is to phone us".
-- Wants online rescheduling, limited to the same clinician. Orthodontic appointments must stay with the same clinician.
-- Asked whether a reminder would help: "A bit. But they don't forget, they just can't get through to us."
-
-## F — Westbrook Dental (acct CL-1219), 4 chairs
-Manager: Ana Kowalczyk
-
-- "When a patient no-shows I can almost always see a missed call or a voicemail from the day before." Has started checking.
-- Front desk is one person; can't answer while checking someone in.
-- Wants patients to move appointments themselves, but worried about double-booking and about patients moving into slots reserved for emergencies.
-- Indifferent on reminders. "Fine, but that's not what's happening."
-
----
-
-## My quick read (not analysed yet)
-- I went in expecting "forgetting" and I'm not sure that's the main thing.
-- Two clinics (A, D) say forgetting. Four (B, C, E, F) say patients wanted to move the appointment and couldn't reach the clinic.
-- D's patients may not use SMS at all.
-- Nobody gave me a real no-show number. None of them track it.

package/packs/product-manager/loops/discover/evals/files/discover-no-show-signal/support-tickets.csv

@@ -1,13 +0,0 @@
-ticket_id,opened,account_id,clinic,channel,subject,body
-T-55102,2026-07-03,CL-1107,Riverside Smiles,email,Online rescheduling?,"Is there any way for patients to move their own appointment online? Our voicemail is full every morning."
-T-55140,2026-07-09,CL-1043,Oakfield Family Dental,chat,Reminder texts,"Can Chairside send text reminders instead of emails? Patients don't read the emails."
-T-55188,2026-07-15,CL-1107,Riverside Smiles,email,Re: Online rescheduling?,"Following up on T-55102. Any update? Still getting 10+ voicemails a day to move appointments."
-T-55231,2026-07-22,CL-1288,Pinecrest Dental,phone,Printer setup,"Appointment cards print on the wrong size paper since the update."
-T-55267,2026-07-28,CL-1201,Lakeview Orthodontics,email,Patient self-service,"Parents keep asking for a link to reschedule. Can the confirmation email have a reschedule button?"
-T-55310,2026-08-04,CL-1107,Riverside Smiles,chat,reschedule link,"Do you have a reschedule link we can send patients? Even just for cleanings."
-T-55355,2026-08-11,CL-1122,Harbourside Dental Studio,email,SMS reminders built in?,"We pay for a separate SMS reminder tool. Do you have reminders by text built in? Also patients reply to the text asking to move and we never see it."
-T-55402,2026-08-19,CL-1107,Riverside Smiles,email,Feature request: patients change own booking,"Raising again. Patients want to change their own booking. This is our number one ask."
-T-55447,2026-08-26,CL-1219,Westbrook Dental,chat,Can patients reschedule themselves?,"Can patients reschedule themselves? Needs to not let them book over emergency slots."
-T-55489,2026-09-02,CL-1288,Pinecrest Dental,email,Export appointments,"How do I export last month's appointments to a spreadsheet?"
-T-55530,2026-09-10,CL-1201,Lakeview Orthodontics,email,Re: Patient self-service,"Any news on the reschedule button? Parents asking weekly."
-T-55574,2026-09-18,CL-1043,Oakfield Family Dental,phone,No-show reminders,"Is there a way to automatically remind patients the day before? We don't have time to ring them all."

package/packs/product-manager/loops/discover/evals/files/discover-vp-loyalty-no-evidence/vp-message.txt

@@ -1,13 +0,0 @@
-From: Dana Whitfield (VP Product, Chairside)
-To: #product-chairside
-Date: Mon 2 Nov 2026, 08:14
-
-Morning all. Back from DentTech Expo. Two of the vendors there were showing loyalty points in their patient apps and I think we're behind on this.
-
-Idea: patients earn points in the Chairside patient app for keeping appointments and for coming back for their six-monthly cleaning. Clinics can let them redeem points for something (whitening discount? priority booking? let the clinics decide).
-
-I bet this cuts no-shows in half and gets more people back for recalls. Clinics will love it.
-
-Can someone get a PRD going this week? I'd like design to start Monday. I'm a yes on this, no need to bring it back to me.
-
-D.

package/packs/product-manager/loops/discover/loop.json

@@ -1,41 +0,0 @@
-{
-  "$comment": "RFC-0028. The first loop of the lifecycle: nothing is designed or built until a human has ratified what problem is being solved. Cheapest loop to redo and the most expensive to skip.",
-  "name": "discover",
-  "version": "0.3.0",
-  "description": "Take raw signal — interviews, journeys, a strategy question — to a requirement a human has ratified, so design starts from an agreed problem rather than an assumed one. Use when the user is deciding what to build, scoping a feature, or turning stakeholder conversations into requirements.",
-  "entrypoint": "LOOP.md",
-  "kind": "loop",
-  "cap": 3,
-  "stages": [
-    {
-      "id": "gather",
-      "type": "generate",
-      "intent": "Collect the raw signal from whichever direction it arrives: a stakeholder conversation, an existing user journey, or a strategic question.",
-      "skills": ["requirements-interview", "user-journey-map", "strategy-analysis", "feedback-synthesis"]
-    },
-    {
-      "id": "structure",
-      "type": "generate",
-      "intent": "Turn the mess into one brief with every field tagged explicit / implied / inferred / missing, so downstream can see what was assumed.",
-      "skills": ["brief-intake"]
-    },
-    {
-      "id": "specify",
-      "type": "generate",
-      "intent": "Turn the ratified brief into numbered requirements a design can be held to.",
-      "skills": ["prd-draft"]
-    },
-    {
-      "id": "ratify",
-      "type": "gate",
-      "intent": "A human agrees this is the problem worth solving. The critique informs that decision; it does not make it.",
-      "skills": ["doc-critique"],
-      "gate": {
-        "id": "G0",
-        "kind": "human",
-        "verdicts": ["PROCEED", "PROCEED WITH CONDITIONS", "REVISE", "RECONSIDER", "BLOCKED"],
-        "revise_to": "structure"
-      }
-    }
-  ]
-}