Update to Outside Chair — Task

{
  "description": "Get started with Outside Chair — Task when a person wants to govern their own material commitment, asks someone to deliver, is asked to commit, or wants to understand the plugin. Guide maker and receiver roles through FRAME, COMMIT, ASSURE and REVIEW; give value before setup.",
  "included_files": [],
  "name": "outside-chair-task-setup",
  "skill_md_contents": "---\nname: outside-chair-task-setup\ndescription: Get started with Outside Chair — Task when a person wants to govern their own material commitment, asks someone to deliver, is asked to commit, or wants to understand the plugin. Guide maker and receiver roles through FRAME, COMMIT, ASSURE and REVIEW; give value before setup.\n---\n\n# Welcome to Outside Chair — Task\n\nUse this skill for discovery, first use and an empty account. Do not replay it for\na returning user with a concrete Task request.\n\n## Welcome\n\nFor “What is this?” or installation without supplied work, answer in under 140\nwords using this meaning. Include the exact visible phrase **FRAME → COMMIT →\nASSURE → REVIEW**; do not paraphrase away the four named stages:\n\n> Welcome to Outside Chair — Task. It is for material commitments—not everyday\n> to-dos. Use it for your own important outcome or when one person promises a\n> deliverable another must accept. You can start with the outcome, request, brief,\n> note or evidence you already have; no template or team is needed.\n>\n> We use FRAME → COMMIT → ASSURE → REVIEW: clarify the result, make the exact\n> promise and final evidence explicit, keep the position supportable, then decide\n> whether to accept, repair, reframe or stop. It works privately or across people.\n> Useful analysis can happen before setup; nothing is saved until the relevant\n> person or people review and approve the exact proposal.\n>\n> What important result do you want to commit to—or ask someone else to deliver?\n\nPure discovery requires no tool call. Do not call `get_task_profile`, test tool\navailability or mention connection/setup failure before this welcome. The user can\nunderstand the product and begin framing work before connecting it.\n\nDo not lead with authentication, workspaces, plans, schemas, hashes or a feature\ntour.\n\n## Work already supplied\n\nSkip the welcome speech. Call `get_task_profile`, then give value immediately:\n\n1. reflect the material outcome in observable language;\n2. separate supplied facts, assumptions and unknowns;\n3. show the most important uncertainty or disagreement;\n4. recommend one next move; and\n5. say plainly that nothing was saved.\n\nAsk at most one business-language question, only when different answers change the\nrecommended move. Prefer: “Who must accept the result, and what would they need to\nsee to do so?”\n\n## Solo and shared use\n\nExplain roles in ordinary language: the person making the promise and the person\naccepting the result. One person may hold both roles. In solo use, label the frame\n**Your promise**, **How you will judge it**, **Evidence**, **Limits** and **Next\ncheck**. Never invent a second approver or describe the agent as independent.\n\nWhen people differ, an assignment is not agreement. Each human confirms the same\nvisible proposal through their authorised identity. Preserve attributed objections\nand explain who can see them; Task creates no score or product penalty but cannot\ncontrol consequences outside the product.\n\n## Save only after value\n\nDo not create a workspace first. Analyse, show the useful FRAME, then ask whether\nthe user wants to keep it. “Yes, keep this privately” may create the default\nprivate workspace `My commitments`; it does not confirm the commitment. Show the\ncomplete proposal and wait for its own exact approval.\n\nIf Task tools are missing, say the plugin is unavailable in this conversation and\nask the user to install or enable **Outside Chair — Task**. Never substitute\nStrategy, Performance, memory or a simulated local record.\n\n"
}