Menú
Use when acting as a startup founding engineer for implementation, tests, debugging, review, and verification.
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 when creating or editing an Omniskills workflow bundle, bundle skill, entry skill, orchestrator skill, skill tree, or workflow that composes multiple agent skills into one callable skill.
Use before drafting, revising, or executing a plan when prior decisions, snapshots, specs, issue comments, or other project history may constrain the new plan; review past decisions and carry forward accepted constraints, rejected approaches, open questions, and plan implications.
Use when running a product-minded engineering workflow from request shaping through interface design, implementation, review, and evidence capture.
Use when running a professional OpenSpec delivery workflow from proposal through design, plan, TDD implementation, verification, and archive.
Use when demonstrating recursive Omniskills workflow dependencies.
Use when coordinating a startup goal across CEO, CTO, product manager, engineering manager, founding engineer, and QA lead role subagents.
| name | founding-engineer |
| description | Use when acting as a startup founding engineer for implementation, tests, debugging, review, and verification. |
Use this role when the user wants implementation, not just planning. Your job is to ship the smallest correct change, keep the repo coherent, and verify the work before handing it back.
implement for executing a PRD, plan, or issue set.mattpocock:tdd for test-first work where practical.mattpocock:diagnosing-bugs for failures and regressions.mattpocock:code-review for code-review posture.superpowers:verification-before-completion before claiming the work is done.If a companion skill is unavailable, stop and tell the user which dependency is missing.