Menu
Use when Codex is running work that originated from DecisionsAI tickets, projects, workflows, or Initiative proposals.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | decisions-codex-worker |
| description | Use when Codex is running work that originated from DecisionsAI tickets, projects, workflows, or Initiative proposals. |
When a task comes from DecisionsAI:
Status: completed | failed | needs_input
Summary: ...
Files changed: ...
Tests: ...
Evidence: ...
Blockers: ...
Next step: ...
Status: needs_input with the
specific missing decision instead of inventing requirements.Next step to the exact continuation DecisionsAI should queue.ponytail skill) — YAGNI ladder, stdlib-first, minimal diff; mark shortcuts with ponytail: comments.fallow skill) — on JS/TS repos, run npx fallow audit --format json --quiet || true before reporting complete and attach the verdict in Tests: or Evidence:.browser-qa, decisions-playwright, webapp-testing when touching UI; use Hermes playwright_browser when Decisions is running.content-engine, article-writing, remotion-video-creation, fal-ai-media when the ticket is content work (see ~/.decisions/harness/mcp-recommendations.json for fal MCP).decisions-ui-ideation then decisions-design-references before new screens; use Refero/Mobbin MCP when configured (see ~/.decisions/harness/mcp-setup-design.sh).decisions-agent-reach + agent-reach for URLs, social, video, GitHub, RSS; run agent-reach doctor --json first.last30days when the ticket needs “what people said lately” (heavier than agent-reach; needs last30days scripts + optional API keys).humanizer after drafts; decisions-marketing-skills + product-marketing for GTM work.decisions-yt-dlp or workflow ytdlp steps; not for Bilibili (use agent-reach bili).decisions-composio (Composio Connect MCP); not Rube (deprecated).python3 ~/plugins/decisions-codex/scripts/report_decisions_event.py --event-type codex_prompt_submitted --status observed --input "<user prompt>" --thread-id "<codex thread id when known>"
Before the final response, call:
python3 ~/plugins/decisions-codex/scripts/report_decisions_event.py --event-type codex_completed --status completed --output "<short result summary>" --thread-id "<codex thread id when known>"
If both sides of a completed turn are only available at the end, call:
python3 ~/plugins/decisions-codex/scripts/report_decisions_event.py --turn-input "<user prompt>" --turn-output "<short result summary>" --thread-id "<codex thread id when known>"
The reporter resolves the DecisionsAI project from the current working
directory and creates or resumes the Codex IDE session. If DecisionsAI is
not running, the reporter exits quietly and Codex continues normally.[DECISIONS CODEX CALLBACK] block, treat that as
live workflow metadata. Use the callback URL or reporter script in that
block to report meaningful events back to DecisionsAI:
codex_started when work begins.codex_prompt_submitted after every user prompt or Codex instruction
submission connected to this DecisionsAI run, including follow-up prompts
typed directly in Codex.user_steer when the human changes direction, adds constraints, or
corrects the approach.codex_waiting or codex_needs_input when blocked on a decision.codex_interrupted when the current task is paused or superseded.codex_progress for material implementation milestones.codex_completed or codex_failed when the work finishes.
If there is no workflow callback block, still report project chat events
through the reporter script. It will use the current working directory to
create or resume a DecisionsAI project IDE session:
python3 ~/plugins/decisions-codex/scripts/report_decisions_event.py --event-type codex_prompt_submitted --status observed --message "<what changed>" --thread-id "<codex thread id when known>"python3 ~/plugins/decisions-codex/scripts/report_decisions_event.py --source ambient --harness codex --event-type codex_progress --status observed --message "<what changed>"
Ambient reporting is best-effort. If DecisionsAI is switched off or
unreachable, the reporter must fail silently and Codex work continues.MUST USE when user wants to research/search/look up/find anything on the internet — e.g. "research this topic", "do a deep dive on X", "search the web for X", "see what people say about X", "look this up". Also MUST USE when user mentions any platform or shares any URL/link: Twitter/X, Reddit, Facebook, Instagram, YouTube, GitHub, Bilibili, XiaoHongShu, Xiaoyuzhou Podcast, LinkedIn/jobs/recruiting, V2EX, Xueqiu (stocks), RSS. 15 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: writing reports/analysis/translation (this skill only FETCHES internet content); posting/commenting/liking (write operations); platforms that already have a dedicated skill installed (prefer that skill).
Dark-themed cloud-platform aesthetic with modular grids, glass-like panels, and strong data hierarchy for productivity dashboards.
Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web.
Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.
Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.
Pick a design aesthetic from awesome-design-skills — bundled minimal/professional/enterprise/shadcn/bento; full catalog in reference for on-demand load.