Menu
Turn a MiVault spec note into a gated implementation plan and handoff.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Improve, audit, simplify, rewrite, or migrate prompts, tool descriptions, agent instructions, and prompt stacks for GPT-5.6 Sol or the GPT-5.6 family. Use for outcome-first prompt design, autonomy boundaries, tool routing, PTC, grounding, verbosity, reasoning effort, and prompt evals.
Apply a deep, design-minded engineering workflow for complex work that needs careful planning, iteration, and simplification.
Use when preparing or running a Claude CLI agentic engineering review through claude -p for repository audits, architecture analysis, system design, security review, large refactors, specs, RFCs, or evidence-grounded long-form engineering analysis.
Use when preparing or running a ZCode GLM-5.2 agentic builder workflow through zcode --prompt for fast implementation, iterative code generation, focused fixes, and validation on an existing repository.
Apply adversarial opposite-analysis to plans, specs, architecture, code changes, and claims. Use when the user asks for adversarial review, opposing analysis, contrarian review, red-team reasoning, or Z.ai and MiniMax cross-checks through the Ralph MCP router.
Review and adjudicate Bugbot, Cursor, Seer, and similar automated PR feedback with local evidence before accepting, fixing, or dismissing findings.
| name | obsidian-spec |
| description | Turn a MiVault spec note into a gated implementation plan and handoff. |
Use this skill when a vault note is the source of truth for an implementation request. The spec stays in MiVault. The repo receives only code, tests, checkpoints, and sanitized docs required by the task.
Read the spec note from VAULT_DIR or ~/Documents/Obsidian/MiVault. Block RED specs. For GREEN or YELLOW specs, generate a dry-run plan with scripts/vault/obsidian-spec-plan.py --spec <note>.
After the user approves implementation, invoke the orchestrator skill to split the work. Apply the relevant gates before marking the spec complete. Update the spec or a handoff note with the plan path, changed files, validation commands, and residual risks.
Do not copy raw vault notes into the repo. Do not externalize RED content. External model use must follow cost-router and model-router policy, and only sanitized GREEN or YELLOW context can leave Codex.
The spec has a plan, the implementation has gate evidence, and the handoff explains what changed without embedding private vault content.