marshallhere/codex-engineering-platform
Spec-driven Codex engineering workflows with project onboarding, independently verified jobs, design reuse and reviewed learning.
Discover existing design conventions, component APIs and UI baselines before editing a mature UI.
Execute an OpenSpec change autonomously using Codex specialist agents, verifiable acceptance criteria, and a bounded repair/polish loop.
Interactively explore localhost UI and turn observed failures into automated regression candidates.
Implement UI by reusing approved components and design tokens before creating new ones.
Route an approved UI change through design discovery, component reuse, rendered review and accessibility evidence.
Define a complete design system and first component catalog for a new UI project.
Benchmark a change to agent roles, skills, memory retrieval or guardrail rules.
Safely change established component APIs or tokens, with migration and regression coverage.
Investigate and fix reproducible bugs with root cause, regression tests and lessons.
Submit, inspect, steer or recover a bounded CEP engineering job with evidence-backed acceptance.
Propose evidence-backed engineering lessons and prepare scoped human batch review before memory promotion.
Capture verified user preferences, mistakes and engineering lessons for explicit review.
Collect required reproducible test, security and rollout evidence before declaring release readiness.
Execute explicit quality, security and regression gates before handoff or merge.
Review a branch or pull request independently for correctness, security, tests and architecture.
Inspect a project and selectively enable Codex Engineering Platform with reversible local configuration.
Implement a scoped product feature with a planned multi-agent workflow and evidence-based quality gates.
Use Storybook MCP and the actual source to discover reusable components, implement UI changes and validate stories before browser QA.
Threat-model changes to authentication, authorization, billing, privacy, or external system integration.
Verify new or changed database migrations and rollout compatibility.
Iterate on real browser screenshots, visual diffs and accessibility evidence until UI acceptance gates pass.
Document an architectural decision with options, assumptions and rollout risk.