Update to august

{
  "name": "august-feedback",
  "description": "Get feedback on ideas, designs, copy, flows, products, dashboards, or research questions by routing to the August MCP — a directory of LLM twins organized by org. Twins represent BOTH end shoppers (per brand org, e.g., GNC, Backcountry) AND product/dashboard users (under the Fermat org, e.g., researchers, PMs, ops users of the Fermat or August dashboards). Picks the best twin or runs a focus group depending on the task. Use whenever the user asks for feedback, reactions, customer perspective, user testing, persona input, dashboard-UX feedback, or \"what would shoppers / dashboard users think.\" Triggers on: \"get feedback\", \"ask August\", \"what would customers say\", \"run this by a twin\", \"focus group this\", \"/august-feedback\".",
  "included_files": [],
  "skill_md_contents": "---\nname: august-feedback\ndescription: >\n  Get feedback on ideas, designs, copy, flows, products, dashboards, or\n  research questions by routing to the August MCP — a directory of LLM twins\n  organized by org. Twins represent BOTH end shoppers (per brand org, e.g.,\n  GNC, Backcountry) AND product/dashboard users (under the Fermat org, e.g.,\n  researchers, PMs, ops users of the Fermat or August dashboards). Picks the\n  best twin or runs a focus group depending on the task. Use whenever the\n  user asks for feedback, reactions, customer perspective, user testing,\n  persona input, dashboard-UX feedback, or \"what would shoppers / dashboard\n  users think.\" Triggers on: \"get feedback\", \"ask August\", \"what would\n  customers say\", \"run this by a twin\", \"focus group this\", \"/august-feedback\".\n---\n\n## ⚠️ MANDATORY TRIGGER RULE\n\n**Any time the user says the word \"feedback\" — or asks for a reaction, gut\ncheck, review, or critique on an artifact — this skill MUST run.** This is\nnon-negotiable.\n\n- Do NOT offer to run it (\"want me to also route this through August?\"). Just\n  run it.\n- Do NOT skip it because the primary ask is something else (brief-alignment\n  check, code review, copy review, etc.). Run it *in addition to* answering\n  the primary ask.\n- Do NOT ask \"do you want twin feedback too?\" — the word \"feedback\" *is* the\n  green light.\n- Only skip when the user explicitly says \"no twin feedback\" or \"skip August.\"\n\nIf the primary ask is something twins can't directly evaluate (e.g., \"does\nthis align with Josh's brief?\"), still invoke this skill on the artifact with\na question they *can* answer — a gut reaction, a usability read, an\nemotional reaction to the design. Always frame the twin question to be\nanswerable, not to be a thin proxy for the primary ask.\n\n# August Feedback\n\nRoute a feedback request to the right August twin(s) — either a single twin\n(best fit interview) or a focus group (multiple twins, broader signal).\nTools live under the August MCP.\n\n**Two flavors of twin exist:**\n- **Shopper twins** — live under each brand org (GNC, Backcountry, etc.).\n  Model real retail customers. Use for feedback on consumer-facing artifacts:\n  funnels, DPPs, product copy, pricing, ads, packaging concepts.\n- **Dashboard-user twins** — live under the **Fermat org**. Model the\n  internal/B2B users of Fermat and August dashboards (researchers, PMs,\n  merchandisers, ops). Use for feedback on tooling, dashboard UX, internal\n  workflows, admin UIs, settings screens, and the August product itself.\n\nMatch the audience to the artifact: a consumer landing page → brand-org\nshopper twins. An internal survey-builder UI → Fermat-org dashboard-user\ntwins. If you're not sure which kind, **ASK**.\n\n**Core rule:** when you don't have enough context to confidently pick the\norganization, the twin, or the format (single vs. focus group), STOP and ask.\nNever silently guess. Better to ask one question than to return feedback from\nthe wrong audience.\n\n---\n\n## STEP 1 — Understand the ask\n\nBefore calling any August tool, be clear on:\n\n- **What is being evaluated?** Copy, a design, a product concept, a pricing\n  idea, a flow, a positioning angle, a feature, a marketing message, etc.\n- **What decision will the feedback inform?** (gut check, prioritization,\n  go/no-go, refinement, A/B framing)\n- **Who is the intended audience?** A specific brand's existing customers? A\n  category buyer in general? A demographic slice?\n- **What format of response is useful?** A single deep reaction (twin),\n  multiple varied reactions (focus group), or a quick gut check?\n\nIf any of the above are unclear from the conversation, **ask the user before\nproceeding.** Use the a concise question tool when you have 2–4 discrete options\nto choose between; use plain prose questions when the answer is open-ended.\n\n---\n\n## STEP 2 — Pick the organization\n\nThe August MCP is org-scoped — every twin and focus group belongs to an\norganization. You MUST know the org before you can pick a twin or run a\ngroup.\n\n### Quick audience → org mapping:\n\n| Artifact being evaluated | Likely org |\n|---|---|\n| Consumer landing page, funnel, DPP, ad, product copy, packaging | The relevant **brand org** (GNC, Backcountry, etc.) |\n| Fermat dashboard UI, August dashboard UI, internal admin tool, survey builder, research workflow | **Fermat org** (dashboard-user twins) |\n| Internal-facing copy / docs / onboarding for Fermat employees or platform users | **Fermat org** |\n\n### Resolution order:\n\n1. If the user has named a brand or audience type (e.g., \"GNC shoppers\",\n   \"dashboard users\", \"Fermat researchers\"), match to an org via\n   `list_organizations`.\n2. If they haven't named one, infer from the artifact: is this consumer-\n   facing (→ brand org) or internal/B2B/dashboard (→ Fermat org)?\n3. If they haven't named one AND the artifact's audience is ambiguous,\n   **ASK.** Present available orgs from `list_organizations` as options.\n   Never assume.\n\nExample question if ambiguous:\n\n> Which audience should I get feedback from?\n> - Shoppers from a brand org (e.g., GNC, Backcountry) — for consumer-facing work\n> - Dashboard users in the Fermat org — for internal/product UX work\n> - Or name a specific persona and I'll find the closest match\n\n---\n\n## STEP 3 — Decide: single twin vs. focus group\n\nUse this rubric to decide. When the signal is mixed or you're not sure,\n**ASK the user** rather than guessing.\n\n### Pick a SINGLE TWIN when:\n- The user wants a deep, conversational reaction (\"what would Sarah think\n  of this?\")\n- The audience is narrow and one persona clearly fits (e.g., \"a budget-\n  conscious first-time supplement buyer\")\n- The user wants to interview / probe / follow up with the same persona\n- The task is a quick gut check on copy, a headline, or a single CTA\n- The user explicitly named a twin or persona type\n\n→ Use `list_twins` to browse, then `start_interview` followed by\n`ask_question`.\n\n### Run a FOCUS GROUP when:\n- The user wants a *range* of reactions or to see disagreement\n- The decision affects a broad audience and one twin isn't representative\n- The user is comparing multiple concepts (A vs. B vs. C) and wants varied\n  takes on each\n- The user wants signal on \"what % of customers would...\" style questions\n- The task involves pricing, positioning, or product-market fit where\n  diversity matters\n\n→ Use `list_focus_groups` to find an existing relevant group, or surface\nthe option to the user. Use `get_focus_group_results` to retrieve results.\n\n### ASK THE USER when:\n- The ask could go either way (e.g., \"feedback on this landing page\" — could\n  be one twin's deep walkthrough OR a focus group's varied first impressions)\n- You don't know how broad/narrow the intended audience is\n- The user hasn't signaled urgency or depth preference\n\nExample question when format is ambiguous:\n\n- **Single twin** — \"Deep reaction from one persona who fits the target\"\n- **Focus group** — \"Varied reactions from multiple personas\"\n- **Quick ask** — \"Open an interview and ask one question\"\n\n---\n\n## STEP 4 — Pick the specific twin (if single-twin route)\n\nOnce the org is set and you're going single-twin:\n\n1. Call `list_twins` for the org.\n2. Match against the feedback ask — demographics, behavior, category\n   affinity, buying stage, etc.\n3. **If multiple twins could fit, ASK.** Show the top 2–3 candidates with\n   one-line summaries and let the user pick.\n\nExample question when twin choice is ambiguous:\n\n> I can route this to one of these twins — which fits best?\n> - Twin A: [one-line description]\n> - Twin B: [one-line description]\n> - Twin C: [one-line description]\n\nNever pick a twin silently when two or more reasonably fit. Mis-routing\nwastes the user's time and produces feedback from the wrong audience.\n\n---\n\n## STEP 5 — Run it\n\n### For a single twin:\n- Call `start_interview` with the selected `twin_id`, then call\n  `ask_question` with the returned `interview_id`. Put the artifact in\n  `design_context` when applicable. For a quick ask, stop after one answer;\n  for a deeper conversation, continue with follow-up `ask_question` calls.\n- Use `get_interview_transcript` with the interview ID as `conversation_id`\n  when the full transcript is needed.\n\n### For a focus group:\n- Use `list_focus_groups` to select an existing relevant group. To run new\n  rounds it must already be configured and ready in August; the MCP does not\n  create focus groups or choose their panel.\n- Use `get_focus_group_results` for completed results. If a relevant ready or\n  completed group doesn't exist, tell the user to configure one in August.\n\nAlways pass the **actual artifact** being evaluated (the copy text, an image\nor description of the design, the product details). Vague prompts produce\nvague feedback.\n\n---\n\n## STEP 6 — Synthesize and return\n\nDon't dump the raw transcript. Return:\n\n1. **TL;DR** — 2–3 sentence summary of the reaction\n2. **What landed** — what the twin(s) responded positively to\n3. **What didn't** — concerns, confusion, objections\n4. **Surprises** — anything unexpected worth flagging\n5. **Suggested next move** — based on the feedback, what to change/test/keep\n6. **Source** — twin name(s) or focus group name + org, so the user can\n   trace back\n\nIf feedback was thin or off-target, say so — and offer to re-route to a\ndifferent twin or format.\n\n---\n\n## When to ask vs. proceed — quick reference\n\n| Situation | Action |\n|---|---|\n| Org is named or obvious from context | Proceed |\n| Org is unclear | **ASK** |\n| One twin clearly fits the ask | Proceed |\n| 2+ twins could fit | **ASK** |\n| Format (single vs. group) clearly indicated | Proceed |\n| Format ambiguous | **ASK** |\n| Artifact (copy/design/concept) is concrete | Proceed |\n| User said \"get feedback\" with no artifact | **ASK** what to evaluate |\n\nDefaulting to \"ask when uncertain\" is the whole point of this skill. The cost\nof one clarifying question is tiny; the cost of feedback from the wrong\naudience is a wasted decision.\n"
}