prizmkit 1.1.57 → 1.1.60

package/bundled/dev-pipeline-windows/templates/session-status-schema.json

@@ -0,0 +1,83 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Dev-Pipeline Session Status",
+  "description": "Schema for session-status.json written by agent at session end",
+  "type": "object",
+  "required": ["session_id", "feature_id", "status", "timestamp"],
+  "properties": {
+    "session_id": {
+      "type": "string",
+      "minLength": 1
+    },
+    "feature_id": {
+      "type": "string",
+      "pattern": "^F-\\d{3}(-[A-Z])?$"
+    },
+    "status": {
+      "type": "string",
+      "enum": ["success", "partial", "failed", "commit_missing", "docs_missing", "merge_conflict"]
+    },
+    "completed_phases": {
+      "type": "array",
+      "items": {
+        "type": "integer",
+        "minimum": 0,
+        "maximum": 7
+      }
+    },
+    "current_phase": {
+      "type": "integer",
+      "minimum": 0,
+      "maximum": 7
+    },
+    "checkpoint_reached": {
+      "type": "string",
+      "pattern": "^CP-[0-3]$"
+    },
+    "tasks_completed": {
+      "type": "integer",
+      "minimum": 0
+    },
+    "tasks_total": {
+      "type": "integer",
+      "minimum": 0
+    },
+    "errors": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "required": ["message"],
+        "properties": {
+          "phase": { "type": "integer" },
+          "type": { "type": "string" },
+          "message": { "type": "string" },
+          "recoverable": { "type": "boolean" }
+        }
+      }
+    },
+    "can_resume": {
+      "type": "boolean"
+    },
+    "docs_maintained": {
+      "type": "boolean"
+    },
+    "retrospective_done": {
+      "type": "boolean"
+    },
+    "resume_from_phase": {
+      "type": ["integer", "null"]
+    },
+    "artifacts": {
+      "type": "object",
+      "properties": {
+        "spec_path": { "type": "string" },
+        "plan_path": { "type": "string" },
+        "context_snapshot_path": { "type": "string" }
+      }
+    },
+    "timestamp": {
+      "type": "string",
+      "format": "date-time"
+    }
+  }
+}

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.57",
+  "version": "1.1.60",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

package/bundled/skills/app-planner/SKILL.md

@@ -35,11 +35,19 @@ If you believe the task is better suited for a different workflow, you MUST:
 
 **Your ONLY writable outputs are:**
 1. `.prizmkit/plans/project-brief.md` (`.prizmkit/plans/` — accumulated project context brief)
-2. Project conventions and architecture decisions appended to `CLAUDE.md` / `CODEBUDDY.md` (with user consent)
-3. Infrastructure configuration (database conventions, deployment config, **cloud services**) appended to `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section
+2. Project conventions and architecture decisions appended to `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` (with user consent)
+3. Infrastructure configuration (database conventions, deployment config, **cloud services**) appended to `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section
 4. `.prizmkit/rules/<layer>-rules.md` — per-layer development rules generated by Rules Configuration
 5. `.prizmkit/prizm-docs/root.prizm` — `RULES:` pointer line only (not other root.prizm content; created minimally if absent)
 
+**Project instruction file selection**:
+- If `.prizmkit/manifest.json` exists, use its `platform` field as the source of truth.
+- Codex → `AGENTS.md`
+- Claude Code → `CLAUDE.md`
+- CodeBuddy → `CODEBUDDY.md`
+- `both` → `CLAUDE.md` and `CODEBUDDY.md`; `all` → all three files.
+- Only when the manifest is missing, fall back to installed PrizmKit-owned platform files such as `.codex/agents/*.toml`, `.claude/commands/prizm-kit.md`, or `.codebuddy/skills/prizm-kit/SKILL.md`. Do not treat a generic `.agents/` directory as Codex.
+
 **After planning is complete**, you MUST:
 1. Present the summary of captured project-level context (vision, conventions, architecture decisions, project brief)
 2. List the artifacts produced and suggest possible next steps (e.g., `feature-planner`, `prizmkit-plan`, etc.) — but do NOT auto-invoke any of them
@@ -74,7 +82,7 @@ Do NOT use this skill when:
    - During brainstorm Phase C → also read `${SKILL_DIR}/references/red-team-checklist.md`
 
 3. **Project conventions discovery** — after Intent Confirmation, before brainstorm or vision work:
-   → Read `CLAUDE.md` / `CODEBUDDY.md` and check for `### Project Conventions` section
+   → Read `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` and check for `### Project Conventions` section
    → If section exists and covers the project well → skip silently
    → If section is missing or incomplete → run the **AI-driven convention discovery** below:
 
@@ -123,12 +131,12 @@ Do NOT use this skill when:
    - Propose as many conventions as the project genuinely needs, but don't pad with irrelevant ones
    - The "Anything I missed?" question is NOT the end — if the user adds items, ask follow-up `AskUserQuestion` calls to clarify those too
 
-   → Save answers to `CLAUDE.md` / `CODEBUDDY.md` under `### Project Conventions` section (format: one bullet per convention)
+   → Save answers to `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` under `### Project Conventions` section (format: one bullet per convention)
    → Output format will naturally vary per project — that is the intended behavior
 
    **Infrastructure Convention Discovery (Database + Deployment)**
 
-   After project conventions are captured, check `CLAUDE.md` / `CODEBUDDY.md` for `### Infrastructure` section:
+   After project conventions are captured, check `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` for `### Infrastructure` section:
 
    - If `### Infrastructure` section does not exist → this project was not initialized with prizmkit-init's Phase 4.6. Treat as if both database and deployment are undecided — run full inquiry below.
    - If `<!-- infrastructure: deferred -->` → user explicitly skipped at init time. Ask: "During project init you deferred infrastructure decisions. Would you like to configure them now?" (options: "Yes — configure now (Recommended)", "Skip — decide later")
@@ -195,7 +203,7 @@ Do NOT use this skill when:
    Use `AskUserQuestion` for both rounds. Each question MUST include a "Skip — decide later" option.
 
    **After infrastructure inquiry**:
-   - Update `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section with all collected information. Replace `<!-- deferred -->` markers with real values. Preserve any existing values that were confirmed unchanged. Full format:
+   - Update `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section with all collected information. Replace `<!-- deferred -->` markers with real values. Preserve any existing values that were confirmed unchanged. Full format:
      ```markdown
      ### Infrastructure
 
@@ -228,7 +236,7 @@ Do NOT use this skill when:
        - [vendor]: [service type]
      <!-- If user picked "None" in Round 1, replace this block with: cloud-services: none -->
      ```
-   - Items still marked "Skip — decide later" remain as `<!-- [topic]: deferred -->` in CLAUDE.md for `prizmkit-deploy` to pick up later.
+   - Items still marked "Skip — decide later" remain as `<!-- [topic]: deferred -->` in the selected project instruction file for `prizmkit-deploy` to pick up later.
 
 4. **Project brief accumulation** — throughout all interactive phases:
    → Read `${SKILL_DIR}/references/project-brief-guide.md` for template and rules
@@ -383,8 +391,8 @@ Proceed to Prerequisites and continue the app-planner workflow.
 Before questions, check optional context files (never block if absent):
 - `.prizmkit/prizm-docs/root.prizm` (architecture/project context)
 - `.prizmkit/config.json` (existing stack preferences and detected tech stack)
-- `CLAUDE.md` / `CODEBUDDY.md` `### Project Conventions` section (previously answered project conventions)
-- `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section (database and deployment config from prizmkit-init or previous app-planner run)
+- `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Project Conventions` section (previously answered project conventions)
+- `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section (database and deployment config from prizmkit-init or previous app-planner run)
 
 **Tech stack auto-population from config.json:**
 - If `.prizmkit/config.json` contains a `tech_stack` object, use it to pre-fill tech assumptions.
@@ -429,8 +437,8 @@ This applies to:
 After initial greeting, use `AskUserQuestion` to confirm intent:
 
 **Question**: "What would you like to do?"
-- **Produce a project plan (Recommended)** — define vision, tech stack, and constraints → generates project-brief.md for pipeline use
-- **Explore ideas first** — brainstorm and refine ideas before committing to a plan
+- **Explore ideas first (Recommended)** — brainstorm and refine ideas before committing to a plan
+- **Produce a project plan** — define vision, tech stack, and constraints → generates project-brief.md for pipeline use
 - **Generate project context only** — for an existing project that needs a project brief without full planning
 
 Route by answer:
@@ -565,8 +573,8 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 | Checkpoint | Artifact/State | Criteria | Phase |
 |-----------|----------------|----------|-------|
 | **CP-AP-0** | Intent Confirmed | User confirmed session goal (produce / explore) | 1 |
-| **CP-AP-1** | Conventions Checked | Project conventions loaded or asked; `### Project Conventions` section in `CLAUDE.md` / `CODEBUDDY.md` up to date | 1 |
-| **CP-AP-1.5** | Infrastructure Checked | Infrastructure config loaded or asked; `### Infrastructure` section in `CLAUDE.md` / `CODEBUDDY.md` addressed — database, deployment **and cloud services** each configured or explicitly deferred | 1-2 |
+| **CP-AP-1** | Conventions Checked | Project conventions loaded or asked; `### Project Conventions` section in `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` up to date | 1 |
+| **CP-AP-1.5** | Infrastructure Checked | Infrastructure config loaded or asked; `### Infrastructure` section in `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` addressed — database, deployment **and cloud services** each configured or explicitly deferred | 1-2 |
 | **CP-AP-1.6** | Rules Configured | For each detected layer (from config.json or self-detection), rules file exists in `.prizmkit/rules/` or user explicitly skipped. `root.prizm` `RULES:` pointer up-to-date. | 2 |
 | **CP-AP-2** | Vision Summary | Goal/users/differentiators confirmed by user. For brownfield: existing purpose confirmed or refined. | 1-2 |
 | **CP-AP-3** | Frontend Design Evaluated | For frontend projects: checked for existing UI/UX design system; user was asked if missing. **Auto-pass** for backend-only or non-UI projects. | 2 |
@@ -578,8 +586,8 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 After Phase 2, if framework-shaping architecture decisions emerged during planning (tech stack, communication patterns, data model strategies — not individual feature details), read `${SKILL_DIR}/references/architecture-decisions.md` and follow the capture flow. Most sessions will NOT produce architecture decisions — only capture when genuinely impactful.
 
 **How it works**:
-1. If decisions are captured → append to `CLAUDE.md` / `CODEBUDDY.md` under `### Architecture Decisions` section
-2. Downstream skills (feature-planner, prizmkit-plan, etc.) read `CLAUDE.md` / `CODEBUDDY.md` as standard context, so they automatically receive these decisions
+1. If decisions are captured → append to `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` under `### Architecture Decisions` section
+2. Downstream skills (feature-planner, prizmkit-plan, etc.) read `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` as standard context, so they automatically receive these decisions
 3. Do NOT write architecture decision content directly to `.prizmkit/prizm-docs/root.prizm` — that file is maintained by `prizmkit-prizm-docs` and `prizmkit-retrospective`. (The `RULES:` pointer line is managed by Rules Configuration, not by this section.) If the project needs `.prizmkit/prizm-docs/`, recommend the user run `prizmkit-prizm-docs` init after planning.
 
 ## Project Brief Accumulation
@@ -612,10 +620,10 @@ When the session appears to be ending:
 After all checkpoints pass, present a summary and end the session:
 
 1. **Summary** (as text): List all project-level artifacts produced:
-   - Project conventions → `CLAUDE.md` / `CODEBUDDY.md` `### Project Conventions`
-   - Infrastructure config → `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` (database conventions + deployment config)
+   - Project conventions → `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Project Conventions`
+   - Infrastructure config → `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` (database conventions + deployment config)
    - Tech stack → `.prizmkit/config.json`
-   - Architecture decisions (if any) → `CLAUDE.md` / `CODEBUDDY.md` `### Architecture Decisions`
+   - Architecture decisions (if any) → `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Architecture Decisions`
    - Dev rules (if configured) → `.prizmkit/rules/<layer>-rules.md` (with `root.prizm` `RULES:` pointer)
    - Project brief → `.prizmkit/plans/project-brief.md`
 

package/bundled/skills/app-planner/references/architecture-decisions.md

@@ -25,10 +25,14 @@ After Phase 2 (Confirm constraints and tech assumptions), before Phase 3 (Captur
 ## How to Capture
 
 1. **Detect platform** — determine which project instruction file to update:
-   - `.claude/` directory exists → append to `CLAUDE.md`
-   - `.codebuddy/` directory exists → append to `CODEBUDDY.md`
-   - Both exist → append to both
-   - Neither exists → skip (no project instruction file)
+   - If `.prizmkit/manifest.json` exists, read `platform` and use it as the source of truth.
+   - `codex` → append to `AGENTS.md`
+   - `claude` → append to `CLAUDE.md`
+   - `codebuddy` → append to `CODEBUDDY.md`
+   - `both` → append to `CLAUDE.md` and `CODEBUDDY.md`; `all` → append to all three files.
+   - Only when the manifest is missing, fall back to PrizmKit-owned install artifacts: `.codex/agents/*.toml`, `.claude/commands/prizm-kit.md`, `.codebuddy/skills/prizm-kit/SKILL.md`.
+   - Do not treat a generic `.agents/` directory as Codex; it may contain unrelated third-party skills.
+   - If no platform can be determined, skip (no project instruction file).
 
 2. **Check for existing section** — read the target file and look for `### Architecture Decisions` heading:
    - If heading exists → append new entries below it (avoid duplicates with existing entries)
@@ -43,6 +47,6 @@ After Phase 2 (Confirm constraints and tech assumptions), before Phase 3 (Captur
    ```
 
 4. **User confirmation** — before writing, show the collected decisions and ask:
-   > "These architecture decisions were identified during planning. Record them to [CLAUDE.md / CODEBUDDY.md]? (Y/n)"
+   > "These architecture decisions were identified during planning. Record them to [AGENTS.md / CLAUDE.md / CODEBUDDY.md]? (Y/n)"
 
    If user declines, skip without further prompting.

package/bundled/skills/app-planner/references/frontend-design-guide.md

@@ -2,7 +2,7 @@
 
 > Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics.
 
-**app-planner context**: In the planning phase, use this guide to establish **design direction decisions** (aesthetic tone, typography approach, color strategy, layout philosophy). Do NOT produce CSS, code, or implementation artifacts — capture the design direction as decisions in the project instruction file (`CLAUDE.md` / `CODEBUDDY.md`). Downstream implementation skills will consume these decisions when building features.
+**app-planner context**: In the planning phase, use this guide to establish **design direction decisions** (aesthetic tone, typography approach, color strategy, layout philosophy). Do NOT produce CSS, code, or implementation artifacts — capture the design direction as decisions in the project instruction file (`AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md`). Downstream implementation skills will consume these decisions when building features.
 
 Load this guide **only when the feature involves frontend/UI work**. Skip for backend-only or infrastructure features.
 

package/bundled/skills/feature-planner/SKILL.md

@@ -111,10 +111,17 @@ Before questions, check optional context files (never block if absent):
 - `.prizmkit/config.json` (existing stack preferences and detected tech stack)
 - `.prizmkit/plans/project-brief.md` (project context from app-planner, if available)
 - existing `.prizmkit/plans/feature-list.json` (required for incremental mode)
-- `CLAUDE.md` / `CODEBUDDY.md`
+- Platform instruction file: use the `platform` field in `.prizmkit/manifest.json` as source of truth when present (`codex` → `AGENTS.md`, `claude` → `CLAUDE.md`, `codebuddy` → `CODEBUDDY.md`; `both`/`all` → read every matching file)
 - If `.prizmkit/prizm-docs/root.prizm` is absent and the project has existing source code, scan the directory structure to understand the codebase layout:
   ```bash
-  find . -maxdepth 2 -type d -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/__pycache__/*' -not -path '*/vendor/*' | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
+  find . -maxdepth 2 -type d \
+    -not -path '*/node_modules/*' -not -path '*/.git/*' \
+    -not -path '*/dist/*' -not -path '*/build/*' \
+    -not -path '*/__pycache__/*' -not -path '*/vendor/*' \
+    -not -path '*/.agents/*' -not -path '*/.codex/*' \
+    -not -path '*/.claude/*' -not -path '*/.codebuddy/*' \
+    -not -path '*/.prizmkit/*' \
+    | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
   ```
 
 **Tech stack from config.json:**

package/bundled/skills/prizmkit-init/SKILL.md

@@ -5,7 +5,7 @@ description: "Project takeover and bootstrap. Scans any project, generates Prizm
 
 # PrizmKit Init
 
-Project takeover and bootstrap skill. Scans any project (brownfield or greenfield), generates Prizm documentation and project brief. Supports CodeBuddy, Claude Code, and dual-platform installations.
+Project takeover and bootstrap skill. Scans any project (brownfield or greenfield), generates Prizm documentation and project brief. Supports Codex, Claude Code, CodeBuddy, and multi-platform installations.
 
 ### When to Use
 - Taking over a new project (brownfield or greenfield)
@@ -25,7 +25,7 @@ Project takeover and bootstrap skill. Scans any project (brownfield or greenfiel
 ## Execution Steps
 
 **Phase 1: Platform Detection**
-1. Detect which platform is running (CodeBuddy or Claude Code) via AI CLI environment.
+1. Detect which platform is running (Codex, Claude Code, or CodeBuddy) via AI CLI environment.
 2. Hold detected platform value in memory — written to disk in Phase 6 along with other config fields.
 
 **Phase 2: Mode Detection**
@@ -71,14 +71,15 @@ BROWNFIELD WORKFLOW (existing project):
    - TOP-LEVEL modules: directories directly under project root that contain source files or sub-directories with source files (e.g. `src/`, `internal/`, `lib/`)
    - SUB-MODULES: directories INSIDE a top-level module (e.g. `src/routes/`, `src/models/`)
    - A sub-module maps to `.prizmkit/prizm-docs/<M>/<S>.prizm`, never to `.prizmkit/prizm-docs/<S>.prizm` — flattening would create ambiguous paths when two modules have identically-named sub-modules
-   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.claude/`, `.codebuddy/`, `.prizmkit/`
+   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.agents/`, `.codex/`, `.claude/`, `.codebuddy/`, `.prizmkit/`
    - **Scan command** — run this to get a 2-level directory tree (excludes noise directories):
      ```bash
      find . -maxdepth 2 -type d \
        -not -path '*/node_modules/*' -not -path '*/.git/*' \
        -not -path '*/dist/*' -not -path '*/build/*' \
        -not -path '*/__pycache__/*' -not -path '*/vendor/*' \
-       -not -path '*/.claude/*' -not -path '*/.codebuddy/*' \
+      -not -path '*/.agents/*' -not -path '*/.codex/*' \
+      -not -path '*/.claude/*' -not -path '*/.codebuddy/*' \
        -not -path '*/.prizmkit/*' -not -path '*/target/*' \
        | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
      ```
@@ -138,7 +139,7 @@ Detect database and deployment signals, then ask 1-2 brief questions. This phase
    - If "SaaS platform": follow up with platform selection (Vercel / Railway / Fly.io / Cloudflare / AWS / Other)
 
 3. **Write results**:
-   - Append `### Infrastructure` section to `CLAUDE.md` (or `CODEBUDDY.md` based on detected platform) with detection results and user answers. Format:
+   - Append `### Infrastructure` section to the detected platform instruction file (`AGENTS.md` for Codex, `CLAUDE.md` for Claude Code, `CODEBUDDY.md` for CodeBuddy) with detection results and user answers. Format:
      ```markdown
      ### Infrastructure
 
@@ -300,7 +301,7 @@ Layer Detection:
 Infrastructure Quick Scan:
   Database: PostgreSQL (Prisma) — detected from dependencies
   Deployment: Vercel — detected from vercel.json
-  → Written to CLAUDE.md ### Infrastructure
+  → Written to the detected platform instruction file `### Infrastructure`
 
 Rules Quick Entry:
   Matched layers: frontend (React), backend (Express.js), database (Prisma) → keeping default rules

package/bundled/skills/recovery-workflow/scripts/detect-recovery-state.py

@@ -354,6 +354,8 @@ def detect_code_changes(project_root, main_branch="main"):
     # Note: .prizmkit/plans/*.json paths are caught by IGNORED_PREFIXES below
     IGNORED_PREFIXES = (
         ".prizmkit/",
+        ".agents/",
+        ".codex/",
         ".claude/",
         ".codebuddy/",
     )