Use this skill to review a finished oh-my-openspec session for problems in its prompts. It compiles raw evidence from commands, agent reports, friction, and the final diff, then presents cited findings without changing files.
Retrospect a finished run via $oh-my-openspec:omos-retro — compile the evidence bundle, dispatch the retrospector, relay ≤8 cited findings. Read-only. Invoke via $oh-my-openspec:omos-retro.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Codex host adaptation (generated from skills/omos-retro/SKILL.md — source of truth stays there):
- Dispatch roles with
spawn_agent/send_input/wait_agent/close_agent. Subagents are asynchronous (default up to 6 concurrent threads), so a wave is one batch ofspawn_agentcalls followed bywait_agentcollection — never poll.openspec_validateis provided by this plugin's bundled MCP server asmcp__openspec__openspec_validate— call it withcwdset to your session's project directory (thechangefilter optional); the VALID/INVALID/UNAVAILABLE/ERROR one-look report format is identical to OpenCode.- This skill is invoked as a
$oh-my-openspec:omos-retromention (or picked from /skills). There is no argument substitution: arguments arrive as plain text in the user's message after the mention — read them from there; when absent, follow this skill's elicitation steps.- Roles run from
~/.codex/agents/omos-*.toml. Ifspawn_agentreports an unknown agent, stop and tell the user to run$oh-my-openspec:omos-setuponce.
Mine the current session for defects in the plugin's own prompts. Read-only: this command never edits anything — findings are for a future PR.
From the current session, assemble exactly:
$oh-my-openspec:omos-init, $oh-my-openspec:omos-plan, $oh-my-openspec:omos-apply,
$oh-my-openspec:omos-archive) and
their targets;BLOCKED:, FAIL, NEEDS-FIX, re-dispatches, extra
critic/verify rounds, user corrections ("no, I meant…");git diff --stat at the end of the run.Keep the bundle raw — quoted lines, not your paraphrase of them. The retrospector's findings must be quotable from it.
Send the bundle to omos-retrospector verbatim. One dispatch, no
rounds: the role either returns findings or No findings — run clean.
Present the report as-is. Add nothing — no commentary, no severity
re-shuffling, no "suggestions". Present the report as rendered Markdown,
never inside a code block. If the user wants fixes, that is ordinary
work in the plugin's own repository ($oh-my-openspec:omos-plan there, or direct
edits), not an action of this command.
agents/, skills/, core/, or any project file from this
command.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Plan worthwhile local tasks by checking dependencies, effects, resources, and platform boundaries, then execute the exact approved plan. It can use safe parallel work or suitable Apple-silicon backends when the project exposes them.
Record deferred engineering decisions and temporary workarounds in a debt registry, with context such as effort, ongoing cost, affected area, and payoff trigger. Entries receive short labels so they can be reviewed or dropped later.
Generate or compare AI agent code for LangChain, EINO, AutoGen, AgentScope, and CrewAI using framework-specific templates, API mappings, conventions, and project structures. Reference files include verification dates to help identify potentially outdated guidance.
Investigate a reproducible bug, test failure, or unexpected page behavior, then make a narrowly scoped fix. The workflow calls for a regression test before changing code, verifies the fix, and reports remaining risks and evidence while avoiding unrelated refactoring or feature work.
Build an AI agent project through six collaborative stages, from requirements and architecture to tools, prompts, code generation, and verification. Start framework-independent, then generate a runnable project for frameworks such as LangChain, EINO, AutoGen, AgentScope, or CrewAI.
Audit a project or learning workflow for scope drift, conflicting plans, inconsistent names, and code quality concerns. The skill reads project files and code, then reports evidence, severity, and suggested next steps without changing files.