Menú
Use as a compatibility alias for brainstorming when the user asks for design shaping, tradeoff discussion, or pre-plan solution framing.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use as the canonical first-stage Agmo workflow when the user wants idea exploration, design tradeoffs, or requirement shaping before planning or implementation.
Run a Codex-native structured code review using agmo-critic and agmo-verifier where evidence is needed.
Harvest `debt:` markers across the repo into a read-only ledger without modifying code.
Audit and maintain the vault-backed llm-wiki knowledge base, including stale pages, low-confidence or contested captures, superseded captures, missing frontmatter, and broken wikilinks.
Use when prior notes, durable project knowledge, or vault-backed context should influence the current task.
Use when one execution lane is no longer enough and work should escalate to the durable `agmo team ...` runtime.
| name | design |
| description | Use as a compatibility alias for brainstorming when the user asks for design shaping, tradeoff discussion, or pre-plan solution framing. |
| argument-hint | [design question, direction, or tradeoff] |
Treat this as a compatibility alias of brainstorming, not as a separate workflow stage.
brainstorming workflow semanticsplan only after the direction is acceptedUse brainstorming in docs, onboarding, and workflow descriptions. Keep design only so existing prompts and habits still route correctly.