full-stack-development
v0.1.2A Codex workflow for fixed product requirements, gated full-stack delivery, and evidence-backed open-source maintenance and releases.
By kevin592License: Apache-2.01.1k GitHub starsUpdated 15 hours ago
Directory evidence
- Runtimes
- Codex
- Parsed components
- 15 skill or MCP entries
- Source updated
- Sep 23, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install full-stack-development for Codex
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add full-stack-development@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/hashgraph-online/awesome-codex-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/kevin592/codex-full-stack-workflow/.
Plugin files
├── .codex-plugin/plugin.json├── skills/artifact-contract-manager/SKILL.md├── skills/change-control/SKILL.md├── skills/completion-verifier/SKILL.md├── skills/full-stack-development/SKILL.md├── skills/hero-ui-craft/SKILL.md├── skills/implementation-planner/SKILL.md├── skills/oss-maintainer-workflow/SKILL.md├── skills/quality-auditor/SKILL.md├── skills/requirement-discovery/SKILL.md├── skills/stage-gate-reviewer/SKILL.md├── skills/tailwind-reference-adapter/SKILL.md├── skills/visual-design-orchestrator/SKILL.md├── skills/visual-evidence-gate/SKILL.md└── .mcp.json
Included Skills13
Use when creating, reviewing, or updating the Artifact Registry and artifact PASS conditions for a product development workspace.
Use whenever the user changes, upgrades, or corrects requirements after initial intake.
Use before claiming a feature, plugin change, UI, API, backend, or full-stack implementation is complete.
MUST use first when Codex works on a product, feature, app, website, landing page, brand site, admin system, backend, database, API, front-end design draft, Pencil/Figma design, full-stack implementation, or any rough goal needing requirements, architecture, design, implementation, verification, or requirement-change handling. When brainstorming also applies, this skill's requirement-discovery and fixed workspace run before brainstorming, visual companion, Pencil/Figma, or code.
Use when Codex works on any front-end implementation, UI polish, dashboard, product screen, internal tool, design system, React component, Tailwind CSS v4 surface, HeroUI React v3 setup, shadcn-to-HeroUI migration, or any task that should use HeroUI. Enforces official HeroUI context, Pencil/Figma component-detail visual approval before coding, HeroUI component selection, and final visual/accessibility verification.
Use after requirements, contracts, and visual gates pass to create a TDD-ready implementation plan.
Use when maintaining or releasing a public open-source repository, including issue triage, pull request review, dependency or security remediation, release preparation, and source-linked adoption reporting.
Use before completion or release to audit visual metrics, HeroUI component graph, backend/API contracts, code review evidence, and official docs freshness.
MUST use before brainstorming, visual companion, Pencil/Figma, or implementation when a user gives a rough product, feature, app, website, landing page, brand site, front-end design draft, or "do not develop yet" goal. Draft the first structured requirement contract and fixed workspace before design or implementation.
Use before moving from requirements to design, design to implementation, implementation to verification, or verification to release.
Use when the user provides a local TailwindUI or Tailwind Plus folder as visual reference material for a HeroUI React/Tailwind v4 implementation.
Use after requirements are approved to run the one-pass Pencil or Figma workflow that creates visual boards, exports images, records approval, and hands off to implementation gates.
Use after requirements are approved and before UI implementation when a product feature needs Pencil or Figma visual design evidence.
MCP servers2
- command
- node
- args
- ./mcp-server/src/index.js
- cwd
- .
- command
- npx
- args
- -y @heroui/react-mcp@latest
Plugin manifests1
{
"name": "full-stack-development",
"version": "0.1.2",
"description": "A Codex workflow for fixed product requirements, gated full-stack delivery, and evidence-backed open-source maintenance and releases.",
"author": {
"name": "kevin592",
"url": "https://github.com/kevin592"
},
"homepage": "https://github.com/kevin592/codex-full-stack-workflow",
"repository": "https://github.com/kevin592/codex-full-stack-workflow",
"license": "Apache-2.0",
"keywords": [
"codex",
"full-stack",
"requirements",
"mcp",
"quality-gates",
"heroui",
"open-source-maintenance"
],
"skills": "./skills/",
"interface": {
"displayName": "全栈开发",
"shortDescription": "Create gated product workspaces and evidence-backed OSS releases.",
"longDescription": "Adds reusable Codex workflows for fixed product requirements, stage tracking, requirement-change regression, backend/frontend contracts, HeroUI delivery, and public open-source maintenance. OSS release gates require source-linked rationale, fresh tests, a clean critical/high security audit, documentation, changelog, pull request review, and honest adoption evidence.",
"developerName": "kevin592",
"category": "Developer Tools",
"capabilities": [
"Read",
"Analyze",
"Generate"
],
"composerIcon": "./assets/icon.svg",
"logo": "./assets/icon.svg",
"defaultPrompt": [
"Use 全栈开发 to clarify and plan this product before implementation.",
"Create the fixed full-stack requirement workspace for this feature.",
"Plan backend, data, API, frontend, HeroUI visual approval, and verification gates.",
"Review this implementation against the full-stack stage contract."
]
},
"mcpServers": "./.mcp.json"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[full-stack-development on Agent Plugins Marketplace](https://pluginsmp.com/plugins/full-stack-development)