菜单
Create decision-complete plans for Codex harness work, including tests, fixtures, contracts, memory updates, verification, and recovery. Use for new features, refactors, bug fixes, audits, or multi-phase autonomous work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Define UI design specs, route contracts, visual states, accessibility expectations, and UI/API synchronization before frontend implementation. Use for new screens, redesigns, visual QA, or UI contract updates.
Automatically synchronize documentation with code changes across all project phases. Detects file changes, categorizes update types, auto-generates API docs, changelog entries, implementation handoffs, and validates cross-reference integrity. Use after any phase implementation.
Initialize and operate a project planning harness for Codex. Use this skill when the user types /init, asks to create a new project, add a feature, fix a bug, plan work, generate tests first, update docs, track phases, review changes, audit a repository, or manage architecture decisions.
Create premium frontend web designs and usable first-screen experiences for new websites, web apps, dashboards, tools, and landing pages. Use when Codex is asked to design or build a new frontend UI, create a fresh page or app experience, choose a visual direction for a new product surface, or turn a product brief into implementation-ready React, Next.js, Tailwind, CSS, or HTML.
Prepare Codex harness package releases with version checks, package dry-runs, npm publish readiness, release notes, verification evidence, and rollback notes. Use before publishing or tagging releases.
Auto-enforce research-first pattern - automatically research documentation, best practices, and GitHub before any important decision. Research output feeds directly into planning. Triggered automatically for features, bugs, architecture changes, and spec updates.
| name | genesis-planning |
| description | Create decision-complete plans for Codex harness work, including tests, fixtures, contracts, memory updates, verification, and recovery. Use for new features, refactors, bug fixes, audits, or multi-phase autonomous work. |
Turn intent into a test-first, contract-first, resumable implementation plan.
Use before any non-trivial change, multi-file task, bug fix, refactor, or autonomous workflow.
Do not use for direct answers that require no repository mutation.
Read .codebase/CURRENT_STATE.md, .codebase/MODULE_INDEX.md, .codebase/TEST_MATRIX.md, plus relevant contracts.
Goal, success criteria, tests, fixtures, contracts, implementation phases, verification, memory updates, and rollback path.
Define the first failing test and expected failure reason.
List exact fixture files and expected outputs.
Identify contract files that must be created or changed.
List .codebase files to update after implementation.
Plan from memory summaries first; inspect only files needed to remove uncertainty.
An implementer can execute without making design decisions.
Planning implementation before tests, omitting fixtures, and leaving verification vague.
If a plan becomes invalid, update the failing test and fixture first, then revise phases.
When decomposing large-scale features or initializing new project modules, you must enforce the 5-Phase MVP Roadmap Standard using the provided templates:
phase-1-core.md, phase-2-auth.md)
phase-3-features.md)
contracts/api/) and mock fixture skeletons (fixtures/api/).tests/integration/ (RED state).phase-3-features.md)
phase-4-integrations.md)
phase-5-readiness.md)
checklists/mvp-readiness.mdexamples/5-phase-roadmap-example.mdtemplates/phase-1-core.md, phase-2-auth.md, phase-3-features.md, phase-4-integrations.md, phase-5-readiness.md