メニュー
Run end-to-end Codex harness orchestration phases from repository analysis through tests, fixtures, implementation, contracts, memory, docs, and change summaries. Use for autonomous multi-phase 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.
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.
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.
| name | genesis-pipeline-orchestration |
| description | Run end-to-end Codex harness orchestration phases from repository analysis through tests, fixtures, implementation, contracts, memory, docs, and change summaries. Use for autonomous multi-phase work. |
Make autonomous work phase-gated, resumable, observable, and impossible to complete without verification.
Use for end-to-end implementation, multi-session work, or pipelines with several dependent agents.
Do not use for small read-only questions.
Goal, current state, module index, test matrix, contracts, fixtures, and acceptance criteria.
Phase logs, tests, fixtures, implementation, contracts, memory updates, docs updates, and change summary.
Create failing tests in Phase 1 before implementation.
Create fixtures in Phase 2 before implementation.
Update contracts in Phase 5 and verify implementation matches them.
Update .codebase in Phase 6.
Never scan the whole repo first. Read memory, map, and test matrix before source.
No phase is skipped and the final report includes verification evidence.
Combining phases, implementing before fixtures, and leaving state non-resumable.
If interrupted, resume from the last completed phase log and rerun verification before continuing.
