Menú
Enforces structured output format for analyses, reports, and recommendations — Executive Summary, Detailed Analysis, Next Steps, Metrics. Prevents wall-of-text responses.
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
Dispatches research agents to find real projects, papers, and documented failures before proposing any feature, architecture, or technology choice. Triggers on creative/design tasks, not on implementation of already-designed specs.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests.
Detects and prevents shortcut rationalization — when the agent is about to skip a step, simplify a requirement, or optimize away a constraint. Triggers proactively when rationalization patterns are noticed.
Provides a persistent cross-session task queue for work that should be done but isn't blocking current tasks. Enables background and future-session work tracking.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
| name | vibe-structured-output |
| description | Enforces structured output format for analyses, reports, and recommendations — Executive Summary, Detailed Analysis, Next Steps, Metrics. Prevents wall-of-text responses. |
| user-invocable | true |
Structure aids comprehension. Every analysis should be scannable before it's readable.
Every structured output has 4 sections:
Tables, sections, evidence. This is the meat.
Numbered, actionable items:
| Metric | Current | Target | Status |
|---|---|---|---|
| [name] | [value] | [value] | ✓/⚠/✗ |
