Update to Roux

{
  "name": "human-context",
  "description": "Collect missing human context through Roux and return synthesized findings to the work in progress. Use when a user asks to launch, create, share, check, or synthesize a Roux; asks teammates, customers, or stakeholders for input; needs qualitative evidence for a decision; or when Codex identifies a consequential information gap that only people can answer.",
  "included_files": [
    {
      "relative_path": "assets/roux.png",
      "size_in_bytes": 3343
    }
  ],
  "skill_md_contents": "---\nname: human-context\ndescription: Collect missing human context through Roux and return synthesized findings to the work in progress. Use when a user asks to launch, create, share, check, or synthesize a Roux; asks teammates, customers, or stakeholders for input; needs qualitative evidence for a decision; or when Codex identifies a consequential information gap that only people can answer.\n---\n\n# Human Context\n\nUse Roux to close human information gaps without inventing an answer or exposing\nrespondent identities and raw transcripts.\n\n## Decide whether to use Roux\n\n- Use Roux when the missing information is held by people: lived experience,\n  objections, priorities, constraints, decision rationale, or local knowledge.\n- Continue directly when the answer is already available in files, code, connected\n  systems, or reliable public sources.\n- Suggest a Roux when it would help, but only call `create_roux` after the user asks\n  to launch it or approves the proposed goal and questions.\n\n## Launch a Roux\n\n1. State the information gap in one sentence.\n2. Draft a specific outcome-oriented goal.\n3. Write two to five neutral questions that a respondent can answer without extra\n   context. Avoid compound, leading, or duplicative questions.\n4. Use `list_roux_workspaces` when you need to confirm which workspace this\n   OAuth connection can access. It returns the single workspace selected during\n   authorization. If the user needs a different workspace, ask them to reconnect\n   Roux and select it during authorization; never try to escape the grant.\n5. Call `create_roux` with a concise title, the goal, relevant work context, the\n   questions, a realistic response target, and a short duration.\n6. Return the respondent link and summarize exactly who should receive it and what\n   the answers will unblock.\n\nDefault to three target responses and eight minutes unless the user provides a\nbetter constraint.\n\n## Find and check Roux\n\n- Use `search_roux` for a known title, phrase, description, or goal.\n- Use `list_roux` for recent Roux or when the user wants to browse. Follow\n  `pagination.next_cursor` when more results are needed.\n- Call `get_roux_status` with the `roux_id` returned by discovery or creation.\n- Report completed versus target responses and the current state.\n- Do not infer who responded. Roux intentionally returns counts without respondent\n  PII or raw response content.\n- Do not poll repeatedly unless the user asks to monitor progress.\n\n## Synthesize and continue the work\n\n1. Generate synthesis only after at least one completed response and when the user\n   asks for the findings or wants the original work completed.\n2. Call `generate_roux_synthesis`, then use `get_roux_synthesis` once processing is\n   ready.\n3. Distinguish synthesized findings from the agent's own inference.\n4. Apply the goal answer, themes, and open questions directly to the original\n   decision or artifact. Preserve uncertainty and call out unresolved questions.\n\n## Handle failures\n\n- On an authorization error, ask the user to reconnect Roux; never request or expose\n  access tokens.\n- On insufficient credits, report the exact Roux error and let the user choose how\n  to proceed.\n- When there are no completed responses, return to collection instead of generating\n  a speculative synthesis.\n"
}