菜单
Use when enterprise work has been built and reviewed and needs a final mechanical ship gate before merge, install, or release-level signoff
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deep enterprise brainstorming that turns vibe-coded ideas into Technical Design Documents. Four phases: EXTRACT (pull intent), DISCOVER (research codebase), PRODUCT DESIGN (user journeys, UI/UX, workflows, platform context), ENGINEER (full TDD). Thinks beyond technical solutions — designs the product, not just the code. Context-aware: auto-detects project type (Shopify app, SaaS, mobile, API, CLI) and applies platform-specific design thinking.
Use when a locked enterprise contract exists and implementation must proceed through strict TDD, contract traceability, and staged review handoffs
Use when verified enterprise work or a resolved debugging session should be captured as searchable institutional knowledge with prevention guidance
Use when an enterprise implementation plan exists and work needs a locked contract with postconditions, invariants, consumer mapping, and traceability before build starts
4-phase systematic debugging: investigate, blast radius scan, root cause identification, TDD fix. Finds root causes not symptoms. Blast radius scan catches sibling bugs. 3-fail circuit breaker prevents fix-forward loops. Use for any bug, test failure, or unexpected behavior.
Use when starting enterprise work in a new repo, new worktree, unfamiliar package, or new computer, or whenever commands, paths, conventions, portability, or project traps are not yet known
| name | enterprise-harness |
| description | Use when enterprise work has been built and reviewed and needs a final mechanical ship gate before merge, install, or release-level signoff |
Final quality gate for enterprise work.
Treat the harness as a fail-closed evidence gate. Schema, query, and data-sensitive changes need live/integration DB proof; UI/PDF/file changes need headless browser proof; every changed runtime file needs code execution proof, E2E trace proof, or a documented non-runtime reason.
Run the checks in final-gate-checks.md as a fresh pass over the resulting artifacts, not as a recap of what build or review already said.
Before harness starts, run the agent-bound harness gate in agent-stage-gates.md.
Produce a compact PASS, FAIL, or WARN verdict with exact failing checks and the blocking reason.
