Update to OrgX

{
  "name": "orgx-initiative-ops",
  "description": "Use when Codex is working on a repo or task that is scoped to an OrgX initiative, workstream, milestone, task, blocker, or decision and needs to use OrgX MCP as the source of truth.",
  "included_files": [],
  "skill_md_contents": "---\nname: orgx-initiative-ops\ndescription: Use when Codex is working on a repo or task that is scoped to an OrgX initiative, workstream, milestone, task, blocker, or decision and needs to use OrgX MCP as the source of truth.\n---\n\n# OrgX Initiative Ops\n\nUse this skill when the task is tied to OrgX execution state rather than just local code.\n\n## Workflow\n\n1. Orient before editing:\n- Call the OrgX workspace or initiative summary tools first.\n- For broad status/reporting questions, prefer `get_operator_chronicle` first\n  when available; it is the canonical decision, artifact, PR, goal, gap, and\n  priority readout.\n- If the hosted OrgX MCP bootstrap advertises `get_operator_chronicle` but the\n  active AI client session has a stale callable tool list, immediately use\n  `orgx_recommend` or `_orgx_recommend` with `mode: \"morning_brief\"` and report\n  the returned `reportingNarrative.briefMarkdown`. Do not wait for the client to\n  reconnect before answering the operator.\n- If an initiative, workstream, task, blocker, or decision is named, treat OrgX as the source of truth for current status.\n\n2. Reuse existing context before creating new structure:\n- Query OrgX memory or list the relevant entities first.\n- Only scaffold new work when no matching initiative structure already exists.\n\n3. Work against the current slice:\n- Prefer updating the current task or workstream instead of creating parallel duplicate work.\n- Keep your local implementation aligned with the active OrgX entity state.\n\n4. Report concrete progress:\n- Use OrgX progress/activity tools for real execution milestones.\n- Register artifacts when code, docs, plans, screenshots, or reports are produced.\n\n5. Surface decisions explicitly:\n- If work is blocked on judgment, request a decision with clear options and impact.\n- Do not bury blockers in prose.\n\n6. Close the loop:\n- When a task is truly done, verify it first.\n- Then update completion state in OrgX if the current task is known.\n\n## Quality bar\n\n- Never assume OrgX entity state from memory alone.\n- Never mark work complete without verification.\n- Prefer one verified task completion over broad unverified status claims.\n- Use `source_client=codex` whenever the tool supports client attribution.\n"
}