Codex Full-Stack Workflow

An open-source Codex plugin that turns rough product requests into staged, reviewable full-stack delivery.

AI coding agents can move quickly while still missing requirements, API contracts, UI states, change impact, or verification evidence. This plugin adds a persistent workflow around those failure modes: requirements become artifacts, each delivery stage has an explicit gate, changes regress the affected stages, and completion requires test and review evidence.

中文简介：这是一个面向 Codex 的全栈开发工作流插件，将模糊需求整理为可追踪的项目工件，并通过阶段门禁、变更回归、视觉证据和质量审计降低 AI 开发中的遗漏。

What it provides

• Requirement discovery and a fixed project requirements workspace
• Artifact registry with producer, consumer, pass-condition, and failure-route contracts
• Stage gates for product scope, architecture, implementation, visual design, and verification
• Change-control rules that invalidate stale downstream artifacts
• Full-stack implementation planning with TDD and code-review gates
• HeroUI React component mapping and official documentation snapshots
• Desktop/mobile visual-evidence checks
• Backend contract, code-review, and completion audits
• Evidence-backed OSS issue triage, security remediation, PR review, and release gates
• A local MCP server exposing the workflow as structured tools
• 97 automated tests covering unit, contract, pressure, and end-to-end scenarios

Install in Codex

The repository includes a Codex marketplace manifest, so the plugin can be installed directly from GitHub:

codex plugin marketplace add kevin592/codex-full-stack-workflow
codex plugin add full-stack-development@kevin592-codex-workflows

Start a new Codex conversation after installation, then try:

Use full-stack-development to turn this rough request into a gated project plan:
build a small ecommerce admin dashboard.

You can inspect installed plugins with:

codex plugin list --json

60-second OSS maintainer demo

Start a Codex conversation in a public repository and try:

Use oss-maintainer-workflow to plan the smallest meaningful maintenance cycle
for this repository. Inspect real issues, pull requests, CI, releases, and the
dependency audit. Do not invent adoption signals. Block release until tests,
security, documentation, changelog, and review evidence pass.

The workflow calls plan_oss_maintenance_cycle to create a source-linked maintenance plan, then review_oss_release_readiness before a tag is published. See the plugin's own v0.1.2 maintenance cycle for a reproducible, honest example.

Develop locally

Requirements:

• Node.js 20 or newer
• npm
• Codex, when testing the installed plugin

git clone https://github.com/kevin592/codex-full-stack-workflow.git
cd codex-full-stack-workflow/mcp-server
npm ci
npm test

Validate the plugin structure from the plugin root when the Codex plugin validator is installed:

cd ..
node ./scripts/validate-plugin.mjs

Run the MCP server over stdio:

cd mcp-server
npm start

Repository layout

.agents/plugins/marketplace.json        Git-backed Codex marketplace
.codex-plugin/plugin.json               Plugin manifest
.mcp.json                               MCP server registration
assets/                                 Marketplace artwork
skills/                                 Workflow skills and references
mcp-server/src/                         MCP tools and workflow contracts
mcp-server/test/                        Automated test suite
scripts/                                Validation and documentation sync
docs/                                   Example generated requirement artifacts
docs/oss-maintenance/                   Source-linked maintenance and release evidence

Maintenance

Issues and pull requests are welcome. Please read CONTRIBUTING.md before proposing a change. Security reports should follow SECURITY.md.

The bundled HeroUI documentation snapshot is traceable through a generated manifest containing source URLs and SHA-256 hashes. See NOTICE for third-party attribution.

The plugin is listed in Awesome Codex Plugins through PR #337.

License

Licensed under the Apache License 2.0.