codex-genesis-harness 0.1.5 → 0.1.7

package/.codex/skills/genesis-harness/resources/project-template.md

@@ -1,38 +1,38 @@
-# Project
-
-## What This Project Is
-
-TBD
-
-## Target Users
-
-TBD
-
-## Core Value
-
-TBD
-
-## Product Scope
-
-- [ ] TBD
-
-## Out Of Scope
-
-- [ ] TBD
-
-## Constraints
-
-- [ ] TBD
-
-## Assumptions
-
-- [ ] TBD
-
-## Current Milestone
-
-TBD
-
-## Success Criteria
-
-- [ ] TBD
-
+# Project
+
+## What This Project Is
+
+TBD
+
+## Target Users
+
+TBD
+
+## Core Value
+
+TBD
+
+## Product Scope
+
+- [ ] TBD
+
+## Out Of Scope
+
+- [ ] TBD
+
+## Constraints
+
+- [ ] TBD
+
+## Assumptions
+
+- [ ] TBD
+
+## Current Milestone
+
+TBD
+
+## Success Criteria
+
+- [ ] TBD
+

package/.codex/skills/genesis-harness/resources/quality-score-template.md

@@ -1,11 +1,11 @@
-# Quality Score
-
-| Area | Score | Issues | Next Action |
-|---|---:|---|---|
-| Architecture | 0/10 | TBD | TBD |
-| Tests | 0/10 | TBD | TBD |
-| Docs Sync | 0/10 | TBD | TBD |
-| Security | 0/10 | TBD | TBD |
-| Maintainability | 0/10 | TBD | TBD |
-| Observability | 0/10 | TBD | TBD |
-
+# Quality Score
+
+| Area | Score | Issues | Next Action |
+|---|---:|---|---|
+| Architecture | 0/10 | TBD | TBD |
+| Tests | 0/10 | TBD | TBD |
+| Docs Sync | 0/10 | TBD | TBD |
+| Security | 0/10 | TBD | TBD |
+| Maintainability | 0/10 | TBD | TBD |
+| Observability | 0/10 | TBD | TBD |
+

package/.codex/skills/genesis-harness/resources/requirements-template.md

@@ -1,26 +1,26 @@
-# Requirements
-
-## Functional Requirements
-
-- [ ] TBD
-
-## Non-Functional Requirements
-
-- [ ] TBD
-
-## User Stories
-
-- [ ] As a user, I want TBD so that TBD.
-
-## Acceptance Criteria
-
-- [ ] TBD
-
-## Edge Cases
-
-- [ ] TBD
-
-## Known Unknowns
-
-- [ ] TBD
-
+# Requirements
+
+## Functional Requirements
+
+- [ ] TBD
+
+## Non-Functional Requirements
+
+- [ ] TBD
+
+## User Stories
+
+- [ ] As a user, I want TBD so that TBD.
+
+## Acceptance Criteria
+
+- [ ] TBD
+
+## Edge Cases
+
+- [ ] TBD
+
+## Known Unknowns
+
+- [ ] TBD
+

package/.codex/skills/genesis-harness/resources/research-template.md

@@ -1,26 +1,26 @@
-# Research
-
-## Question
-
-TBD
-
-## Local Codebase Findings
-
-- [ ] TBD
-
-## External Findings
-
-- [ ] TBD
-
-## Sources
-
-- TBD
-
-## Decision Impact
-
-TBD
-
-## Risks
-
-- [ ] TBD
-
+# Research
+
+## Question
+
+TBD
+
+## Local Codebase Findings
+
+- [ ] TBD
+
+## External Findings
+
+- [ ] TBD
+
+## Sources
+
+- TBD
+
+## Decision Impact
+
+TBD
+
+## Risks
+
+- [ ] TBD
+

package/.codex/skills/genesis-harness/resources/review-template.md

@@ -1,22 +1,22 @@
-# Review
-
-## Changed Files Reviewed
-
-- [ ] TBD
-
-## Findings
-
-| Severity | File | Issue | Required Action |
-|---|---|---|---|
-| TBD | TBD | TBD | TBD |
-
-## Cleanup Performed
-
-- [ ] Removed unnecessary files/code
-- [ ] Removed debug logs
-- [ ] Removed unrelated changes
-
-## Residual Risks
-
-- [ ] TBD
-
+# Review
+
+## Changed Files Reviewed
+
+- [ ] TBD
+
+## Findings
+
+| Severity | File | Issue | Required Action |
+|---|---|---|---|
+| TBD | TBD | TBD | TBD |
+
+## Cleanup Performed
+
+- [ ] Removed unnecessary files/code
+- [ ] Removed debug logs
+- [ ] Removed unrelated changes
+
+## Residual Risks
+
+- [ ] TBD
+

package/.codex/skills/genesis-harness/resources/spec-changelog-template.md

@@ -1,6 +1,6 @@
-# Spec Changelog
-
-| Date/Time | Change | Reason | Impacted Docs | Impacted Tests | Migration Notes |
-|---|---|---|---|---|---|
-| TBD | Initial harness setup | Project initialization | TBD | TBD | TBD |
-
+# Spec Changelog
+
+| Date/Time | Change | Reason | Impacted Docs | Impacted Tests | Migration Notes |
+|---|---|---|---|---|---|
+| TBD | Initial harness setup | Project initialization | TBD | TBD | TBD |
+

package/.codex/skills/genesis-harness/resources/stack-template.md

@@ -1,33 +1,33 @@
-# Stack
-
-## Detected Stack
-
-Language:
-Framework:
-Runtime:
-Database:
-Package manager:
-Test framework:
-Lint:
-Typecheck:
-Build:
-Deployment:
-
-## Version Constraints
-
-- [ ] TBD
-
-## Local Development Commands
-
-```sh
-# start
-# test
-# lint
-# typecheck
-# build
-```
-
-## Tooling Gaps
-
-- [ ] TBD
-
+# Stack
+
+## Detected Stack
+
+Language:
+Framework:
+Runtime:
+Database:
+Package manager:
+Test framework:
+Lint:
+Typecheck:
+Build:
+Deployment:
+
+## Version Constraints
+
+- [ ] TBD
+
+## Local Development Commands
+
+```sh
+# start
+# test
+# lint
+# typecheck
+# build
+```
+
+## Tooling Gaps
+
+- [ ] TBD
+

package/.codex/skills/genesis-harness/resources/verification-template.md

@@ -1,26 +1,26 @@
-# Verification
-
-## Test Contract
-
-- [ ] Normal input/output
-- [ ] Edge cases
-- [ ] Invalid inputs
-- [ ] Expected errors
-- [ ] Acceptance tests
-
-## Commands
-
-```sh
-# TBD
-```
-
-## Results
-
-| Command | Result | Evidence |
-|---|---|---|
-| TBD | TBD | TBD |
-
-## Manual Verification
-
-- [ ] TBD
-
+# Verification
+
+## Test Contract
+
+- [ ] Normal input/output
+- [ ] Edge cases
+- [ ] Invalid inputs
+- [ ] Expected errors
+- [ ] Acceptance tests
+
+## Commands
+
+```sh
+# TBD
+```
+
+## Results
+
+| Command | Result | Evidence |
+|---|---|---|
+| TBD | TBD | TBD |
+
+## Manual Verification
+
+- [ ] TBD
+

package/.codex/skills/genesis-harness-engineering/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: harness-engineering-skill
+name: genesis-harness-engineering
 description: "Evolve the Codex harness itself: verification loops, repository memory, test-first scaffolds, resumability, observability, and autonomous workflow reliability. Use for changes to this repository's skill system or harness architecture."
 ---
 

package/.codex/skills/genesis-new-design/SKILL.md

@@ -17,7 +17,7 @@ Use when building a new web page, app screen, dashboard, tool, landing page, or
 Do not use for redesigning existing UI without first preserving behavior; use `genesis-upgrade-design` instead.
 
 ## Inputs required
-Product intent, target users, primary workflow, stack details, route or entry point, state list, and visual constraints.
+Product intent, target users, primary workflow, stack details, route or entry point, state list, visual constraints, and the generated visual contract image `mockup.png` (which MUST be loaded via the `view_file` tool to inspect layouts, color choices, and dimensions before coding).
 
 ## Outputs required
 Implemented UI, UI contract, fixtures, responsive states, visual verification, and docs or memory updates.
@@ -55,6 +55,7 @@ If visual output fails, capture screenshot evidence, update the fixture or contr
 
 2. Define the design intent from the request:
    - Identify audience, product category, primary task, density, tone, and constraints.
+   - Proactively inspect `mockup.png` using the `view_file` tool to absorb the visual direction, color system, and placement details.
    - Choose one clear visual direction and commit to it across typography, color, spacing, surfaces, iconography, and motion.
    - For tools, dashboards, and operational apps, prioritize scanning, repeated use, compact controls, and predictable navigation over decorative hero layouts.
 

package/.codex/skills/genesis-new-design/agents/openai.yaml

@@ -1,4 +1,4 @@
-interface:
-  display_name: "Genesis New Design"
-  short_description: "Create premium frontend web designs"
+interface:
+  display_name: "Genesis New Design"
+  short_description: "— Thiết kế giao diện Web hiện đại, cao cấp"
   default_prompt: "Use $genesis-new-design to design and build a premium frontend web experience."

package/.codex/skills/genesis-pipeline-orchestration/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: pipeline-orchestration-skill
+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.
 ---
 

package/.codex/skills/genesis-planning/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: planning-skill
+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.
 ---
 
@@ -44,3 +44,28 @@ Planning implementation before tests, omitting fixtures, and leaving verificatio
 ## Recovery workflow
 If a plan becomes invalid, update the failing test and fixture first, then revise phases.
 
+---
+
+## 🏗️ 5-Phase MVP Roadmap Standards
+
+When decomposing large-scale features or initializing new project modules, you must enforce the **5-Phase MVP Roadmap Standard** using the provided templates:
+
+1. **Phase 1: Core Foundation & Base Setup** (Templates: `phase-1-core.md`, `phase-2-auth.md`)
+   - Establish environment skeletons, base CLI arguments, dependency configurations, and contract JSON structures.
+   - Core DB migrations, model schemes, and basic configurations.
+2. **Phase 2: Contract-First & Skeletal Tests** (Template: `phase-3-features.md`)
+   - Compile exhaustive contract endpoints (`contracts/api/`) and mock fixture skeletons (`fixtures/api/`).
+   - Auto-generate test skeletons in `tests/integration/` (RED state).
+3. **Phase 3: Logic Implementation & Self-Healing** (Template: `phase-3-features.md`)
+   - Implement minimal code handlers, controllers, or service endpoints.
+   - Execute closed-loop Verify-Fix cycles autonomously until all tests turn GREEN.
+4. **Phase 4: Multi-Agent & External Integrations** (Template: `phase-4-integrations.md`)
+   - Wire up external components, API sync triggers, or media providers.
+5. **Phase 5: E2E Visual QA & Release Readiness** (Template: `phase-5-readiness.md`)
+   - Execute full Playwright E2E smoke tests, visual regression checks, and packaging checklists.
+
+### Related Planning Assets
+* **Checklist**: `checklists/mvp-readiness.md`
+* **Example**: `examples/5-phase-roadmap-example.md`
+* **Templates**: `templates/phase-1-core.md`, `phase-2-auth.md`, `phase-3-features.md`, `phase-4-integrations.md`, `phase-5-readiness.md`
+

package/.codex/skills/genesis-planning/checklists/mvp-readiness.md

@@ -0,0 +1,18 @@
+# MVP Phase Planning Readiness Checklist
+
+Use this checklist to ensure all 5 phases of the MVP are fully defined and ready to proceed.
+
+## Scope & Boundaries
+- [ ] Has the product target audience been clearly defined?
+- [ ] Is the absolute minimum viable feature set (and what is explicitly OUT of scope) documented?
+- [ ] Are success metrics defined for each of the 5 phases?
+
+## Technical Feasibility
+- [ ] Is the technology stack fully decided, including database models and cloud providers?
+- [ ] Are all third-party integrations identified, along with keys/credential requirements?
+- [ ] Are testing and validation tools decided and functional locally?
+
+## Phase Definition Alignment
+- [ ] Do Phase 1 (Core) database schemas align with Phase 3 (Features) functional requirements?
+- [ ] Are security and authorization scopes in Phase 2 prepared to handle Phase 3 routes?
+- [ ] Are Phase 5 deployment and observability targets fully defined?

package/.codex/skills/genesis-planning/examples/5-phase-roadmap-example.md

@@ -0,0 +1,43 @@
+# Example: 5-Phase MVP Roadmap for "TaskFlow SaaS"
+
+This is an example roadmap representing a completed planning output for a TaskFlow SaaS application.
+
+## ROADMAP Overview
+
+- [x] Phase 0: Foundation & Project Planning (Complete)
+- [ ] Phase 1: Foundation & API Core (Target: 2026-06-15)
+- [ ] Phase 2: Authentication & Security (Target: 2026-06-22)
+- [ ] Phase 3: Core MVP Features (Target: 2026-07-06)
+- [ ] Phase 4: Third-Party Integrations (Target: 2026-07-15)
+- [ ] Phase 5: Production Readiness & Observability (Target: 2026-07-22)
+
+---
+
+## Detailed Phase Definition
+
+### Phase 1: Foundation & API Core
+- **Database ERD**: Users, Tasks, Workspaces, Comments tables.
+- **API Contracts**:
+  - `POST /api/v1/workspaces`
+  - `GET /api/v1/workspaces/:id/tasks`
+- **Verification**: SQL schema migrates successfully; mock endpoints return JSON schemas.
+
+### Phase 2: Authentication & Security
+- **Auth Provider**: Firebase Auth integration.
+- **Route Guards**: All `/api/v1/workspaces` routes require a valid Bearer token.
+- **Verification**: Request without header returns HTTP 401; request with valid token returns HTTP 200.
+
+### Phase 3: Core MVP Features
+- **Functional Flow**: Create workspace, invite user, add task, comment on task.
+- **Frontend Views**: Dashboard, Workspace page, Task Details modal.
+- **Verification**: Playwright e2e test logs in user, creates task, and verifies task appears in UI list.
+
+### Phase 4: Third-Party Integrations
+- **Payment Gateway**: Stripe subscription billing.
+- **Notifications**: Sendgrid transactional email alerts.
+- **Verification**: Stripe webhook registers subscription renewal event correctly; email triggers on task assignment.
+
+### Phase 5: Production Readiness & Observability
+- **Health Checks**: `/health`, `/readiness` checks DB + Stripe connectivity.
+- **Monitoring**: Prom-client registers HTTP request latency histograms.
+- **Verification**: Grafana dashboard imports JSON config successfully; Promtool validates alert rules.

package/.codex/skills/genesis-planning/templates/phase-1-core.md

@@ -0,0 +1,17 @@
+# Phase 1: Foundation & API Core
+
+## Goal
+Establish the backend foundation, database schemas, and robust API contracts for the MVP. No UI code is written in this phase.
+
+## Tasks
+- [ ] Research and design database models/tables
+- [ ] Define initial schemas (JSON Schemas, SQL Migrations)
+- [ ] Create API contract files under `contracts/api/`
+- [ ] Implement foundational database access layer and initial repository patterns
+- [ ] Build mock API endpoints verifying request/response formats
+- [ ] Implement and verify initial API contract tests
+
+## Success Criteria
+- All database models are defined and migrated.
+- API endpoints return successfully with mock/fixture data matching contracts.
+- Verification tests pass successfully.

package/.codex/skills/genesis-planning/templates/phase-2-auth.md

@@ -0,0 +1,17 @@
+# Phase 2: Authentication & Security
+
+## Goal
+Secure the application with user authentication, role-based access control, and route guards.
+
+## Tasks
+- [ ] Research stack-specific auth mechanisms (JWT, session, Firebase Auth, etc.)
+- [ ] Configure environment variables for token secrets/keys
+- [ ] Implement Sign-Up, Sign-In, and Sign-Out endpoints and helpers
+- [ ] Implement authorization middleware / route guards
+- [ ] Write integration tests verifying authenticated vs unauthenticated access
+- [ ] Implement secure CORS and headers setup
+
+## Success Criteria
+- User registration and login flow works correctly.
+- Protected API routes return appropriate HTTP 401/403 errors when unauthenticated.
+- All auth unit and integration tests pass successfully.

package/.codex/skills/genesis-planning/templates/phase-3-features.md

@@ -0,0 +1,17 @@
+# Phase 3: Core MVP Features
+
+## Goal
+Implement the main functional value proposition of the MVP.
+
+## Tasks
+- [ ] Answer checklists/new-feature-qa.md for the core workflows
+- [ ] Plan and outline database updates for core features
+- [ ] Implement core backend business logic, validation rules, and algorithms
+- [ ] Create UI components and pages required for the MVP journeys
+- [ ] Wire up frontend components to backend API services
+- [ ] Write integration and end-to-end user journey tests
+
+## Success Criteria
+- User can successfully complete the primary business journey end-to-end.
+- Data is correctly persisted, modified, and queried from the database.
+- Core business tests pass with >80% code coverage.

package/.codex/skills/genesis-planning/templates/phase-4-integrations.md

@@ -0,0 +1,17 @@
+# Phase 4: Third-Party Integrations
+
+## Goal
+Integrate required external services (payment gateways, notification APIs, email delivery, or background queues).
+
+## Tasks
+- [ ] Research external API capabilities, quotas, and SDKs
+- [ ] Create robust client wrappers with rate-limiting and retry logic
+- [ ] Implement local mock/stub fixtures for external service testing
+- [ ] Implement background workers / queues for asynchronous processes
+- [ ] Implement email / notification sending events and templates
+- [ ] Write integration tests verifying third-party callback/webhook handlers
+
+## Success Criteria
+- External API calls are successfully handled and tested using mock fixtures.
+- Background jobs run, retry, and log failures cleanly.
+- Webhooks are securely verified and processed.