OrgX Initiative Ops

Use this skill when the task is tied to OrgX execution state rather than just local code.

Workflow

1. Orient before editing:

• Call the OrgX workspace or initiative summary tools first.
• For broad status/reporting questions, prefer get_operator_chronicle first

when available; it is the canonical decision, artifact, PR, goal, gap, and priority readout.

• If the hosted OrgX MCP bootstrap advertises get_operator_chronicle but the

active AI client session has a stale callable tool list, immediately use orgx_recommend or _orgx_recommend with mode: "morning_brief" and report the returned reportingNarrative.briefMarkdown. Do not wait for the client to reconnect before answering the operator.

• If an initiative, workstream, task, blocker, or decision is named, treat OrgX as the source of truth for current status.

1. Reuse existing context before creating new structure:

• Query OrgX memory or list the relevant entities first.
• Only scaffold new work when no matching initiative structure already exists.

1. Work against the current slice:

• Prefer updating the current task or workstream instead of creating parallel duplicate work.
• Keep your local implementation aligned with the active OrgX entity state.

1. Report concrete progress:

• Use OrgX progress/activity tools for real execution milestones.
• Register artifacts when code, docs, plans, screenshots, or reports are produced.

1. Surface decisions explicitly:

• If work is blocked on judgment, request a decision with clear options and impact.
• Do not bury blockers in prose.

1. Close the loop:

• When a task is truly done, verify it first.
• Then update completion state in OrgX if the current task is known.

Quality bar

• Never assume OrgX entity state from memory alone.
• Never mark work complete without verification.
• Prefer one verified task completion over broad unverified status claims.
• Use source_client=codex whenever the tool supports client attribution.