codex-genesis-harness 0.1.6 → 0.1.8

package/scripts/verify.sh

@@ -9,26 +9,26 @@ skill_names=(
   genesis-upgrade-design
   genesis-architecture
   genesis-planning
-  genesis-mvp-planning
   genesis-codebase-map
   genesis-design-spec
   genesis-api-contract
-  ui-ux-test-skill
+  genesis-ui-ux-test
   genesis-harness-engineering
   genesis-ai-provider
   genesis-pipeline-orchestration
-  genesis-research
-  genesis-docs
-  genesis-release
   genesis-api-sync
   genesis-debug-guide
   genesis-docs-automation
   genesis-spec-propagation
-  genesis-release-orchestration
   genesis-performance-profiling
   genesis-observability-automation
   genesis-research-first
+  genesis-release
   spec-impact-engine
+  genesis-executing-plans
+  genesis-test-driven-development
+  genesis-verification-before-completion
+  genesis-using-git-worktrees
 )
 
 required_memory_files=(
@@ -121,7 +121,14 @@ required_scripts=(
   run-verify-loop.sh
 )
 
+max_skill_lines=500
+
 fail() {
+  if [ "${VIBE_MODE:-0}" = "1" ]; then
+    echo "verify WARN (VIBE_MODE): $*" >&2
+    echo "- [$(date -u +"%Y-%m-%dT%H:%M:%SZ")] VIBE_MODE Bypass: Verify check failed - $*" >> "$repo_root/.codebase/TECH_DEBT.md"
+    return 0
+  fi
   echo "verify failed: $*" >&2
   exit 1
 }
@@ -176,9 +183,12 @@ verify_repository_harness
 verify_skill_metadata() {
   local skill_dir="$1"
   local expected_name="$2"
+  local skill_lines
 
   [ -f "$skill_dir/SKILL.md" ] || fail "missing SKILL.md: $skill_dir"
   [ -f "$skill_dir/agents/openai.yaml" ] || fail "missing agents/openai.yaml: $skill_dir"
+  skill_lines="$(wc -l < "$skill_dir/SKILL.md" | tr -d ' ')"
+  [ "$skill_lines" -le "$max_skill_lines" ] || fail "SKILL.md exceeds ${max_skill_lines} lines ($skill_lines): $skill_dir"
   grep -q "^name: $expected_name[[:space:]]*$" "$skill_dir/SKILL.md" || fail "invalid skill name frontmatter (expected 'name: $expected_name'): $skill_dir"
   grep -q '^description:' "$skill_dir/SKILL.md" || fail "missing description frontmatter: $skill_dir"
   grep -q 'default_prompt:' "$skill_dir/agents/openai.yaml" || fail "missing default_prompt: $skill_dir"
@@ -195,7 +205,7 @@ verify_harness_skill() {
   grep -q 'Definition Of Done' "$skill_dir/SKILL.md" || fail "missing Definition Of Done"
   grep -q 'Quality Rubric' "$skill_dir/SKILL.md" || fail "missing Quality Rubric"
 
-  for ref in workflows.md planning-schema.md research-rubric.md quality-rubric.md; do
+  for ref in workflows.md planning-schema.md research-rubric.md quality-rubric.md state-machine.md; do
     [ -f "$skill_dir/references/$ref" ] || fail "missing reference: $ref"
     grep -q "references/$ref" "$skill_dir/SKILL.md" || fail "SKILL.md does not mention reference: $ref"
   done
@@ -250,6 +260,7 @@ verify_minimal_skill() {
   local skill_dir="$1"
 
   [ -d "$skill_dir/templates" ] || fail "missing templates/: $skill_dir"
+  [ -d "$skill_dir/checklists" ] || fail "missing checklists/: $skill_dir"
   [ -d "$skill_dir/examples" ] || fail "missing examples/: $skill_dir"
 }
 
@@ -268,67 +279,11 @@ verify_one() {
     genesis-new-design|genesis-upgrade-design)
       verify_design_skill "$skill_dir" "$dir_name"
       ;;
-    genesis-architecture)
-      verify_skill_metadata "$skill_dir" "architecture-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-planning)
-      verify_skill_metadata "$skill_dir" "planning-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-mvp-planning)
-      verify_skill_metadata "$skill_dir" "genesis-mvp-planning"
-      verify_minimal_skill "$skill_dir"
-      ;;
-    genesis-codebase-map)
-      verify_skill_metadata "$skill_dir" "codebase-map-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-design-spec)
-      verify_skill_metadata "$skill_dir" "design-spec-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-api-contract)
-      verify_skill_metadata "$skill_dir" "api-contract-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    ui-ux-test-skill)
-      verify_skill_metadata "$skill_dir" "ui-ux-test-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-harness-engineering)
-      verify_skill_metadata "$skill_dir" "harness-engineering-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-ai-provider)
-      verify_skill_metadata "$skill_dir" "ai-provider-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-pipeline-orchestration)
-      verify_skill_metadata "$skill_dir" "pipeline-orchestration-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-research)
-      verify_skill_metadata "$skill_dir" "research-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-docs)
-      verify_skill_metadata "$skill_dir" "docs-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-release)
-      verify_skill_metadata "$skill_dir" "release-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-api-sync)
-      verify_skill_metadata "$skill_dir" "api-sync-skill"
+    genesis-architecture|genesis-planning|genesis-codebase-map|genesis-design-spec|genesis-api-contract|genesis-ui-ux-test|genesis-harness-engineering|genesis-ai-provider|genesis-pipeline-orchestration|genesis-api-sync|genesis-executing-plans|genesis-test-driven-development|genesis-verification-before-completion|genesis-using-git-worktrees)
+      verify_skill_metadata "$skill_dir" "$dir_name"
       verify_skill_protocol "$skill_dir"
       ;;
-    genesis-debug-guide)
-      verify_skill_metadata "$skill_dir" "debug-guide-skill"
-      verify_playbook_skill "$skill_dir"
-      ;;
-    genesis-docs-automation|genesis-spec-propagation|genesis-release-orchestration|genesis-performance-profiling|genesis-observability-automation)
+    genesis-debug-guide|genesis-docs-automation|genesis-spec-propagation|genesis-performance-profiling|genesis-observability-automation|genesis-release)
       verify_skill_metadata "$skill_dir" "$dir_name"
       verify_playbook_skill "$skill_dir"
       ;;

package/tests/integration/cli-smoke.test.js

@@ -0,0 +1,103 @@
+#!/usr/bin/env node
+"use strict";
+
+const assert = require("assert");
+const fs = require("fs");
+const os = require("os");
+const path = require("path");
+const { execFileSync } = require("child_process");
+
+const repoRoot = path.resolve(__dirname, "..", "..");
+const cli = path.join(repoRoot, "bin", "genesis-harness.js");
+const tmp = fs.mkdtempSync(path.join(os.tmpdir(), "genesis-cli-smoke-"));
+
+function run(args, cwd = tmp) {
+  return execFileSync(process.execPath, [cli, ...args], {
+    cwd,
+    env: {
+      ...process.env,
+      CODEX_HOME: path.join(tmp, "codex-home"),
+      GENESIS_HARNESS_HOME: path.join(tmp, "agents-home"),
+      GENESIS_HARNESS_SKIP_POSTINSTALL: "1"
+    },
+    encoding: "utf8"
+  });
+}
+
+function runPostinstall(initCwd) {
+  return execFileSync(process.execPath, [cli, "postinstall"], {
+    cwd: repoRoot,
+    env: {
+      ...process.env,
+      CODEX_HOME: path.join(initCwd, "codex-postinstall-home"),
+      GENESIS_HARNESS_HOME: path.join(initCwd, "agents-postinstall-home"),
+      INIT_CWD: initCwd
+    },
+    encoding: "utf8"
+  });
+}
+
+fs.mkdirSync(path.join(tmp, ".codebase"), { recursive: true });
+fs.mkdirSync(path.join(tmp, ".planning"), { recursive: true });
+fs.writeFileSync(path.join(tmp, ".codebase", "CURRENT_STATE.md"), "# Current State: TEST\n");
+fs.writeFileSync(path.join(tmp, ".codebase", "API_CONTRACTS.md"), "# API Contracts\n");
+fs.writeFileSync(path.join(tmp, ".planning", "SPEC_CHANGELOG.md"), "# Spec Changelog\n");
+fs.writeFileSync(path.join(tmp, "package.json"), JSON.stringify({ name: "smoke-fixture" }, null, 2));
+
+run(["install", "--target", "agents"]);
+const seededPolicyPath = path.join(tmp, ".codebase", "context-policy.json");
+assert(fs.existsSync(seededPolicyPath), "install should seed LeanCTX policy into project .codebase");
+const seededPolicy = JSON.parse(fs.readFileSync(seededPolicyPath, "utf8"));
+assert.strictEqual(seededPolicy.token_budget, 12000, "seeded LeanCTX policy should use package default");
+
+fs.writeFileSync(
+  seededPolicyPath,
+  JSON.stringify({ token_budget: 8000, compact_at: 0.7, hard_stop_at: 0.9 }, null, 2)
+);
+run(["install", "--target", "agents"]);
+const preservedPolicy = JSON.parse(fs.readFileSync(seededPolicyPath, "utf8"));
+assert.strictEqual(preservedPolicy.token_budget, 8000, "install must not overwrite customized LeanCTX policy");
+
+const postinstallTmp = fs.mkdtempSync(path.join(os.tmpdir(), "genesis-postinstall-smoke-"));
+fs.writeFileSync(path.join(postinstallTmp, "package.json"), JSON.stringify({ name: "postinstall-fixture" }, null, 2));
+runPostinstall(postinstallTmp);
+assert(
+  fs.existsSync(path.join(postinstallTmp, ".codebase", "context-policy.json")),
+  "postinstall should seed LeanCTX policy when npm exposes INIT_CWD"
+);
+
+const pathOutput = run(["path"]);
+assert(pathOutput.includes("genesis-harness"), "path should include installed skill paths");
+
+const statusOutput = run(["status"]);
+assert(statusOutput.includes("GENESIS HARNESS - STATUS REPORT"), "status should render status report");
+
+const docsOutput = run(["docs"]);
+assert(docsOutput.includes("GENESIS HARNESS - DOCUMENTATION REPORT"), "docs should render docs report");
+
+const leanCtxOutput = run(["leanctx"]);
+assert(leanCtxOutput.includes("LeanCTX Policy"), "leanctx should render policy report");
+assert(leanCtxOutput.includes("Token budget: 8000"), "leanctx should read project policy");
+assert(leanCtxOutput.includes("Command wrapper:"), "leanctx should report command wrapper detection");
+assert(leanCtxOutput.includes("rtk optional"), "leanctx should treat rtk as optional");
+assert(leanCtxOutput.includes("genesis-harness sync"), "leanctx should include portable sync command");
+
+const primeOutput = run(["prime"]);
+assert(primeOutput.includes("LeanCTX Policy"), "prime should include LeanCTX policy");
+assert(primeOutput.includes("rtk optional"), "prime should document optional wrapper behavior");
+
+const gateOutput = run(["docs-gate"]);
+assert(
+  gateOutput.includes("Docs sync check passed") || gateOutput.includes("docs sync check is limited"),
+  "docs-gate should pass in fixture"
+);
+
+run(["sync"]);
+const visual = fs.readFileSync(path.join(tmp, ".codebase", "VISUAL_GRAPH.md"), "utf8");
+assert(visual.includes("Harness Relationship Map"), "sync should generate harness relationship map");
+assert(visual.includes("genesis-harness docs-gate"), "sync graph should include docs-gate");
+assert(!visual.includes("Đăng nhập"), "sync graph must not emit stale sample roadmap");
+assert(!visual.includes("src/auth.js"), "sync graph must not emit stale sample source path");
+assert(visual.includes("```mermaid"), "sync graph should contain mermaid fences");
+
+console.log("cli smoke passed");

package/tests/unit/feature_registry.test.js

@@ -0,0 +1,152 @@
+#!/usr/bin/env node
+"use strict";
+
+/**
+ * feature_registry.test.js
+ * L08 – Feature List as Harness Primitive
+ * L11 – Observability Bên Trong Harness
+ *
+ * Tests must FAIL before implementation (Red phase).
+ * Run: node tests/unit/feature_registry.test.js
+ */
+
+const assert = require("assert");
+const fs = require("fs");
+const path = require("path");
+
+const repoRoot = path.resolve(__dirname, "..", "..");
+
+// ─────────────────────────────────────────────────────────────────────────────
+// L08 — Feature Registry checks
+// ─────────────────────────────────────────────────────────────────────────────
+
+const REGISTRY_PATH = path.join(repoRoot, "features", "REGISTRY.md");
+const REGISTRY_SCHEMA_PATH = path.join(repoRoot, "contracts", "features", "registry-schema.json");
+
+// Test 1: features/REGISTRY.md phải tồn tại
+assert(
+  fs.existsSync(REGISTRY_PATH),
+  "L08: features/REGISTRY.md must exist as machine-readable feature primitive"
+);
+
+// Test 2: REGISTRY.md phải chứa section machine-readable features table
+const registryContent = fs.readFileSync(REGISTRY_PATH, "utf8");
+assert(
+  registryContent.includes("| id |"),
+  "L08: REGISTRY.md must have a machine-readable table with 'id' column"
+);
+assert(
+  registryContent.includes("| status |"),
+  "L08: REGISTRY.md must have a 'status' column"
+);
+assert(
+  registryContent.includes("| verify_cmd |"),
+  "L08: REGISTRY.md must have a 'verify_cmd' column per feature"
+);
+
+// Test 3: Mỗi feature phải có trạng thái hợp lệ
+const validStatuses = ["planned", "in-progress", "done", "verified", "deprecated"];
+const tableRows = registryContent
+  .split("\n")
+  .filter(line => /^\|\s*F\d+\s*\|/.test(line)); // Only data rows from Feature Table (id starts with F)
+assert(
+  tableRows.length > 0,
+  "L08: REGISTRY.md must have at least one feature entry (id must start with F, e.g. F001)"
+);
+for (const row of tableRows) {
+  const cols = row.split("|").map(c => c.trim()).filter(Boolean);
+  if (cols.length < 2) continue;
+  const status = cols[1];
+  assert(
+    validStatuses.includes(status),
+    `L08: Invalid status '${status}' in REGISTRY.md — must be one of: ${validStatuses.join(", ")}`
+  );
+}
+
+// Test 4: contracts/features/registry-schema.json phải tồn tại
+assert(
+  fs.existsSync(REGISTRY_SCHEMA_PATH),
+  "L08: contracts/features/registry-schema.json must exist"
+);
+const schema = JSON.parse(fs.readFileSync(REGISTRY_SCHEMA_PATH, "utf8"));
+assert(schema.version, "L08: registry-schema.json must have a version field");
+assert(schema.required_columns, "L08: registry-schema.json must define required_columns");
+assert(
+  Array.isArray(schema.required_columns) && schema.required_columns.includes("id"),
+  "L08: required_columns must include 'id'"
+);
+
+// Test 5: REGISTRY.md phải được đề cập trong MODULE_INDEX.md
+const moduleIndex = fs.readFileSync(
+  path.join(repoRoot, ".codebase", "MODULE_INDEX.md"),
+  "utf8"
+);
+assert(
+  moduleIndex.includes("features/REGISTRY.md"),
+  "L08: features/REGISTRY.md must be listed in .codebase/MODULE_INDEX.md"
+);
+
+// ─────────────────────────────────────────────────────────────────────────────
+// L11 — Observability Live Data checks
+// ─────────────────────────────────────────────────────────────────────────────
+
+const OBS_SCHEMA_PATH = path.join(repoRoot, "contracts", "observability", "agent-run-schema.json");
+const OBS_SAMPLE_PATH = path.join(repoRoot, "observability", "agent-runs", "sample-run.json");
+const OBS_FAILURE_SCHEMA_PATH = path.join(repoRoot, "contracts", "observability", "failure-schema.json");
+const OBS_FAILURE_SAMPLE_PATH = path.join(repoRoot, "observability", "failures", "sample-failure.json");
+const OBS_DECISION_SAMPLE_PATH = path.join(repoRoot, "observability", "decision-logs", "sample-decision.md");
+
+// Test 6: contracts/observability/ phải có agent-run-schema.json
+assert(
+  fs.existsSync(OBS_SCHEMA_PATH),
+  "L11: contracts/observability/agent-run-schema.json must exist"
+);
+const agentRunSchema = JSON.parse(fs.readFileSync(OBS_SCHEMA_PATH, "utf8"));
+assert(agentRunSchema.required_fields, "L11: agent-run-schema.json must define required_fields");
+const requiredRunFields = ["session_id", "timestamp", "skill", "phase", "outcome", "evidence"];
+for (const field of requiredRunFields) {
+  assert(
+    agentRunSchema.required_fields.includes(field),
+    `L11: agent-run-schema.json must require field '${field}'`
+  );
+}
+
+// Test 7: observability/agent-runs/ phải có ít nhất 1 sample entry
+assert(
+  fs.existsSync(OBS_SAMPLE_PATH),
+  "L11: observability/agent-runs/sample-run.json must exist as live sample"
+);
+const sampleRun = JSON.parse(fs.readFileSync(OBS_SAMPLE_PATH, "utf8"));
+for (const field of requiredRunFields) {
+  assert(
+    sampleRun[field] !== undefined,
+    `L11: sample-run.json is missing required field '${field}'`
+  );
+}
+
+// Test 8: contracts/observability/failure-schema.json phải tồn tại
+assert(
+  fs.existsSync(OBS_FAILURE_SCHEMA_PATH),
+  "L11: contracts/observability/failure-schema.json must exist"
+);
+const failureSchema = JSON.parse(fs.readFileSync(OBS_FAILURE_SCHEMA_PATH, "utf8"));
+assert(failureSchema.required_fields, "L11: failure-schema.json must define required_fields");
+
+// Test 9: observability/failures/ phải có sample failure entry
+assert(
+  fs.existsSync(OBS_FAILURE_SAMPLE_PATH),
+  "L11: observability/failures/sample-failure.json must exist"
+);
+
+// Test 10: observability/decision-logs/ phải có sample thực tế (không chỉ template)
+assert(
+  fs.existsSync(OBS_DECISION_SAMPLE_PATH),
+  "L11: observability/decision-logs/sample-decision.md must exist as actual decision record"
+);
+const decisionContent = fs.readFileSync(OBS_DECISION_SAMPLE_PATH, "utf8");
+assert(
+  !decisionContent.includes("What changed."),
+  "L11: sample-decision.md must be a real decision record, not just the blank template"
+);
+
+console.log("feature_registry tests passed");

package/tests/unit/prompt_sentinel.test.js

@@ -1,6 +1,6 @@
 /**
  * Unit Test for prompt_sentinel.js
- * Part of Genesis Codex Harness v0.1.7
+ * Part of Genesis Codex Harness v0.1.8
  */
 
 const assert = require('assert');

package/tests/unit/spec_visual_sync.test.js

@@ -1,6 +1,6 @@
 /**
  * Unit Test for spec_visual_sync.js
- * Part of Genesis Codex Harness v0.1.7
+ * Part of Genesis Codex Harness v0.1.8
  */
 
 const assert = require('assert');

package/tests/unit/test_generator.test.js

@@ -1,6 +1,6 @@
 /**
  * Unit Test for test_generator.js
- * Part of Genesis Codex Harness v0.1.7
+ * Part of Genesis Codex Harness v0.1.8
  */
 
 const assert = require('assert');

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

@@ -1,46 +0,0 @@
----
-name: docs-skill
-description: Keep Codex harness docs synchronized with skills, contracts, tests, memory, and release behavior. Use after any workflow, public interface, install, verification, or package behavior change.
----
-
-# Docs Skill
-
-## Purpose
-Keep docs short, accurate, and linked to source-of-truth artifacts.
-
-## When to use
-Use after changing skills, CLI behavior, contracts, fixtures, tests, repository memory, or publish flow.
-
-## When NOT to use
-Do not use to duplicate full architecture manuals in `AGENTS.md`.
-
-## Inputs required
-Changed files, public behavior, verification results, and affected users.
-
-## Outputs required
-Updated README, AGENTS map, codebase memory, changelog-style summary, and changed docs list.
-
-## Required tests
-Run docs-related verification and package dry-run when docs affect packaging or install instructions.
-
-## Required fixtures
-Update templates/examples when docs describe reusable workflows.
-
-## Required contract updates
-Update contracts when docs describe new interface behavior.
-
-## Required codebase map updates
-Update `.codebase/CURRENT_STATE.md`, `MODULE_INDEX.md`, or summaries as needed.
-
-## Token saving rules
-Keep docs concise. Link to templates and contracts instead of repeating them.
-
-## Acceptance criteria
-Docs match behavior and do not duplicate large internal manuals.
-
-## Common mistakes
-Letting AGENTS.md grow too large, documenting unverified behavior, and missing install docs.
-
-## Recovery workflow
-If docs drift, add verify assertions or checklist items that catch the drift next time.
-

package/.codex/skills/genesis-docs/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Docs Skill"
-  short_description: "Synchronize harness documentation"
-  default_prompt: "Use $docs-skill to update concise docs and repository memory after changes."
-policy:
-  allow_implicit_invocation: true
-

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

@@ -1,114 +0,0 @@
----
-name: genesis-mvp-planning
-description: "Define, structure, and automate the creation of a standard 5-Phase MVP Roadmap right after project initialization. Guarantees a decision-complete path to production-ready launch."
----
-
-# Genesis MVP 5-Phase Planning Skill
-
-## Purpose
-
-The `genesis-mvp-planning` skill is designed to transition a newly initialized project into a structured, decision-complete **5-Phase MVP Roadmap**. Instead of leaving the repository with only a blank generic Phase 0 (Foundation) folder, this skill maps out the entire lifecycle of a production-ready Minimum Viable Product across exactly 5 logical, sequential phases.
-
----
-
-## When to use
-
-Use the `genesis-mvp-planning` skill when:
-- You have just run `/genesis-init` (or `/init`) and need to map out the implementation timeline.
-- You want to scope an application specifically to its MVP (Minimum Viable Product) boundaries.
-- You want to establish clear gates and milestones for each stage of the project lifecycle.
-
----
-
-## When NOT to use
-
-Do NOT use the `genesis-mvp-planning` skill when:
-- The project is already midway through development with a pre-existing mature roadmap.
-- The task is a minor, single-file bug fix or simple refactoring that doesn't affect the project timeline.
-- The roadmap has already been fully approved and is currently active.
-
----
-
-## Inputs required
-
-Before running this planning skill, ensure the following inputs are gathered:
-- **Project Brief / Intent**: Clear understanding of what application is being built and target users.
-- **Technology Stack**: Backend, frontend, database, auth provider, and deployment target.
-- **Core MVP Features List**: The primary business value proposition that must be delivered.
-
----
-
-## Outputs required
-
-Executing this skill creates the following structured deliverables:
-- `.planning/ROADMAP.md`: Updated roadmap with 5 distinct phases defined.
-- `.planning/phases/PHASE_1_CORE/`: Planning directory for Phase 1 (Foundation & API Core).
-- `.planning/phases/PHASE_2_AUTH/`: Planning directory for Phase 2 (Authentication & Security).
-- `.planning/phases/PHASE_3_FEATURES/`: Planning directory for Phase 3 (Core MVP Features).
-- `.planning/phases/PHASE_4_INTEGRATIONS/`: Planning directory for Phase 4 (Third-Party Integrations).
-- `.planning/phases/PHASE_5_READINESS/`: Planning directory for Phase 5 (Production Readiness & Observability).
-
----
-
-## Required tests
-
-The planning deliverables are validated using:
-- [ ] `test/planning/roadmap-structure.test.js`: Verifies `ROADMAP.md` contains all 5 phases with valid status checkboxes.
-- [ ] `test/planning/phase-completeness.test.js`: Verifies each phase directory contains standard `SPEC.md`, `PLAN.md`, and `TASKS.md`.
-
----
-
-## Required fixtures
-
-- `fixtures/planning/roadmap-expected.md`: The canonical structure of a 5-Phase MVP roadmap.
-- `fixtures/planning/phase-config-expected.json`: Complete configuration template mapping out the 5 phases.
-
----
-
-## Required contract updates
-
-Update the following files if phase boundary standards change:
-- `contracts/planning/roadmap.schema.json`: Schema validator for `ROADMAP.md` files.
-- `contracts/planning/phase.schema.json`: Schema validator for individual phase directories.
-
----
-
-## Required codebase map updates
-
-After mapping out the 5-Phase MVP:
-- **`.codebase/CURRENT_STATE.md`**: Update current phase to Phase 1, and add the full 5-phase overview.
-- **`.codebase/MODULE_INDEX.md`**: Add references to each of the 5 phase directories.
-
----
-
-## Token saving rules
-
-1. **Reuse templates**: Do not rewrite the basic structure of the phases. Use the provided phase templates in `templates/`.
-2. **Summarize context**: Do not read every detail of the repository. Use `SUMMARY.md` and module index.
-3. **Draft sequentially**: Plan one phase at a time to keep prompt sizes small.
-
----
-
-## Acceptance criteria
-
-The 5-Phase MVP roadmap is ACCEPTED when:
-- [ ] `ROADMAP.md` is updated with 5 clearly defined phases, dates, and success criteria.
-- [ ] All 5 phase planning folders (`PHASE_1_CORE` to `PHASE_5_READINESS`) are created and populated.
-- [ ] No feature code is written before the 5 phase boundaries are validated.
-
----
-
-## Common mistakes
-
-### Mistake 1: Starting Phase 3 (Core Features) before Phase 1 (API Core)
-- **Problem**: Writing UI screens without verified backend models and schemas leads to massive rework.
-- **Fix**: Complete Phase 1 and 2 to establish a solid database and API contract first.
-
----
-
-## Recovery workflow
-
-### Recovery 1: Phase drift or timeline changes
-1. Mark the affected phase as `[!] blocked` in `ROADMAP.md`.
-2. Document the change in `SPEC_CHANGELOG.md`.
-3. Adjust downstream phase boundaries accordingly.

package/.codex/skills/genesis-mvp-planning/agents/openai.yaml

@@ -1,6 +0,0 @@
-interface:
-  display_name: "Genesis MVP Planning"
-  short_description: "— Xây dựng lộ trình 5 Phase phát triển sản phẩm MVP"
-  default_prompt: "Use $genesis-mvp-planning to map out the 5 essential phases of a production-ready MVP."
-policy:
-  allow_implicit_invocation: true