Ruo Task Colour Marker

RUO Task Colour Marker

Purpose

Use this skill to keep the RUO task dashboard colour-coded from the latest facts Pafi gives. Codex owns the colour marking layer: other agents can read the same dashboard and understand which tasks are green, yellow, red, or grey without re-interpreting the conversation.

Default dashboard: /Users/pafi/Documents/RUO Peptides/output/ruo-team-task-dashboard-2026-06-22/ruo-team-task-dashboard-data.json

If that file is missing, find the active dashboard with:

rg --files "/Users/pafi/Documents/RUO Peptides" | rg 'ruo-team-task-dashboard.*data\.json$'

Colour Policy

Read references/colour-policy.md when you need examples or when a task is ambiguous.

Use these colours:

• green: verified done or safe to proceed. Evidence exists, blocker cleared, or Pafi explicitly says it is decided/done.
• yellow: open, partial, waiting, delegated, or needs verification. Use yellow when work can continue but should not be treated as fully closed.
• red: blocked, unsafe, non-compliant, stale/conflicting data, missing proof for a critical dependency, or should not proceed.
• grey: parked, planned, superseded, inactive, or not yet in execution.

Do not infer a green mark from optimism. Green requires Pafi's explicit decision or evidence you personally verified.

Authority Order

Resolve conflicts in this order:

1. Newest explicit instruction from Pafi.
2. Verified live evidence from website, Supabase, files, screenshots, or logs.
3. Current dashboard JSON.
4. Older notes, handoffs, plans, or chat summaries.

When evidence conflicts, mark yellow if work can continue with review, or red if proceeding would be unsafe or misleading. Record the conflict in colourReason.

Dashboard Fields

Add or update these fields on each task:

"colour": "yellow",
"colourReason": "Short reason tied to latest evidence/instruction.",
"colourEvidence": ["dashboard row", "Pafi instruction 2026-06-30"],
"colourUpdatedAt": "2026-06-30T12:00:00Z",
"colourUpdatedBy": "Codex"

Do not change status, owner, assignees, title, or scope unless Pafi explicitly asks for those changes too.

Task numbers are 1-based from the current tasks array. Prefer IDs when available, for example P1-014.

Quick Commands

Mark task 25 yellow:

python3 /Users/pafi/.codex/skills/ruo-task-colour-marker/scripts/mark_dashboard_task.py \
  --task 25 \
  --colour yellow \
  --reason "Open until QR implementation and scan proof exist." \
  --evidence "Pafi dashboard review"

Dry-run a change before writing:

python3 /Users/pafi/.codex/skills/ruo-task-colour-marker/scripts/mark_dashboard_task.py \
  --task P1-014 \
  --colour green \
  --reason "Pafi marked decided and evidence exists." \
  --evidence "Pafi instruction" \
  --dry-run

Workflow

1. Read the requested task row from the dashboard JSON.
2. Apply the authority order and colour policy.
3. Use the helper script for the colour update.
4. Validate JSON with python3 -m json.tool <dashboard> >/dev/null.
5. Report the task number, ID, title, colour, and reason.
6. If this changed project state, append a short note to ~/.codex/codex-to-genie.md and store a session note in Cortex when available.

Guardrails

• Preserve user edits and unrelated dashboard rows.
• Never mark a compliance-sensitive task green if legal/compliance proof is missing.
• Never mark a website or Supabase task green if you only checked one side and the acceptance requires both.
• Keep colour reason short, concrete, and audit-friendly.