prizmkit 1.1.189 → 1.1.191

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (49) hide show
  1. package/bin/create-prizmkit.js +4 -4
  2. package/bundled/VERSION.json +3 -3
  3. package/bundled/adapters/antigravity/assets/prizmkit-hook.cjs +150 -0
  4. package/bundled/adapters/antigravity/hooks-adapter.js +195 -0
  5. package/bundled/adapters/antigravity/paths.js +14 -0
  6. package/bundled/adapters/antigravity/rules-adapter.js +54 -0
  7. package/bundled/adapters/antigravity/skill-adapter.js +29 -0
  8. package/bundled/dev-pipeline/README.md +16 -5
  9. package/bundled/dev-pipeline/prizmkit_runtime/config.py +13 -2
  10. package/bundled/dev-pipeline/prizmkit_runtime/gitops.py +12 -12
  11. package/bundled/dev-pipeline/prizmkit_runtime/platform_detection.py +13 -4
  12. package/bundled/dev-pipeline/prizmkit_runtime/runners.py +8 -2
  13. package/bundled/dev-pipeline/prizmkit_runtime/sessions.py +186 -24
  14. package/bundled/dev-pipeline/prizmkit_runtime/status.py +2 -0
  15. package/bundled/dev-pipeline/scripts/parse-stream-progress.py +305 -17
  16. package/bundled/dev-pipeline/scripts/utils.py +5 -3
  17. package/bundled/dev-pipeline/tests/live_ai_cli_log_smoke.py +1 -0
  18. package/bundled/dev-pipeline/tests/test_python_runner_parity.py +135 -0
  19. package/bundled/dev-pipeline/tests/test_unified_cli.py +363 -0
  20. package/bundled/rules/USAGE.md +1 -0
  21. package/bundled/skills/_metadata.json +1 -1
  22. package/bundled/skills/bug-planner/SKILL.md +29 -31
  23. package/bundled/skills/bug-planner/references/generated-plan-review.md +19 -23
  24. package/bundled/skills/bug-planner/scripts/validate-bug-list.py +11 -0
  25. package/bundled/skills/feature-planner/SKILL.md +22 -22
  26. package/bundled/skills/feature-planner/references/generated-plan-review.md +19 -23
  27. package/bundled/skills/feature-planner/references/incremental-feature-planning.md +7 -7
  28. package/bundled/skills/feature-planner/references/new-project-planning.md +7 -7
  29. package/bundled/skills/feature-planner/scripts/validate-and-generate.py +11 -0
  30. package/bundled/skills/prizmkit-init/SKILL.md +1 -1
  31. package/bundled/skills/prizmkit-init/references/config-schema.md +2 -2
  32. package/bundled/skills/prizmkit-prizm-docs/assets/prizm-docs-format.md +1 -1
  33. package/bundled/skills/prizmkit-prizm-docs/references/op-init.md +1 -1
  34. package/bundled/skills/refactor-planner/SKILL.md +23 -25
  35. package/bundled/skills/refactor-planner/references/fast-path.md +4 -4
  36. package/bundled/skills/refactor-planner/references/generated-plan-review.md +19 -23
  37. package/bundled/skills/refactor-planner/scripts/validate-and-generate-refactor.py +11 -0
  38. package/package.json +1 -1
  39. package/src/ai-cli-launch.js +1 -1
  40. package/src/clean.js +40 -4
  41. package/src/config.js +64 -4
  42. package/src/detect-platform.js +10 -6
  43. package/src/external-skills.js +2 -2
  44. package/src/index.js +1 -0
  45. package/src/manifest.js +1 -1
  46. package/src/platforms.js +6 -2
  47. package/src/prompts.js +11 -3
  48. package/src/scaffold.js +59 -4
  49. package/src/upgrade.js +9 -3
@@ -1,28 +1,28 @@
1
1
  # Generated Plan Review — Bug Planner
2
2
 
3
- Use this local review loop after `.prizmkit/plans/bug-fix-list.json` has been generated and validated. This is a planner-output review, not an implementation/code-diff review.
3
+ Use this local review loop on the batch that is about to be inserted into `.prizmkit/plans/bug-fix-list.json`. This is a planner-output review, not an implementation/code-diff review, and it runs before the insert so the verdict decides whether the batch lands.
4
4
 
5
5
  ## Trigger
6
6
 
7
- Run only when the current `bug-planner` session generated, appended, or rewrote final bug planning content. For validate-only, summary-only, or draft-save flows with no new final planning content, report: `Local generated-plan review: not applicable — no new final planning content written.`
7
+ Run only when the current `bug-planner` session produced a draft batch of new or changed bugs. For validate-only, summary-only, or draft-save flows with no new batch, report: `Local generated-plan review: not applicable — no new planning content written.`
8
8
 
9
- In ordinary incremental flow, the additions draft is internal transport/recovery state. After consequential decisions and the pre-generation gate pass, immediately run `append`; do not ask for separate user approval merely to promote the draft into the final list. Keep the draft through the bounded review/fix loop, then delete the ordinary internal draft before final handoff only after this review returns `PASS` and final validation passes.
9
+ The draft is the whole review surface. Nothing is written to the final list while this loop runs: the single insert happens only after a `PASS`, so the verdict decides whether the batch lands and no final list ever holds reviewed-looking entries that were never reviewed.
10
10
 
11
11
  ## Direct Artifact Reads
12
12
 
13
13
  Planning artifacts may be gitignored, untracked, or absent from staged and unstaged diffs. Read the actual files through bounded, source-first access:
14
14
 
15
- - Final list: `.prizmkit/plans/bug-fix-list.json` — run the `context` command for root prose and recent IDs; do not load the complete historical list into AI context
16
- - Draft/source list when present: `.prizmkit/plans/bug-fix-list.draft.json` — ordinary incremental flow contains only additions and may be read completely
15
+ - Review target: `.prizmkit/plans/bug-fix-list.draft.json` — the additions-only or complete batch, read in full; this is the only planning content under review
16
+ - Final list: `.prizmkit/plans/bug-fix-list.json` — run the `context` command for root prose and recent IDs; do not load the complete historical list into AI context, and do not expect this session's batch to appear in it yet
17
17
  - Pre-session final list snapshot if captured in memory before edits — retain only bounded root context, prior task count/next ID, and the five recent `{id, description}` pairs, not full history
18
18
  - In-memory draft object if the session has not written a draft file yet
19
- - Newly appended or explicitly modified final entries — load each known ID with `python3 ${SKILL_DIR}/scripts/validate-bug-list.py show --input .prizmkit/plans/bug-fix-list.json --id B-NNN`
19
+ - Already-committed entries a reviewed item relies on — load each referenced ID with `python3 ${SKILL_DIR}/scripts/validate-bug-list.py show --input .prizmkit/plans/bug-fix-list.json --id B-NNN`
20
20
 
21
- Do not rely on `git status`, `git diff`, or `git diff --cached` to decide whether planner output exists or changed. Do not invoke `/prizmkit-code-review` for this planner-output gate; `/prizmkit-code-review` remains the implementation/code-diff review gate after `/prizmkit-implement`.
21
+ Do not rely on `git status`, `git diff`, or `git diff --cached` to decide whether planner output exists or changed. If the final list already contains this session's batch, the insert ran before the verdict — report that instead of reviewing an already-landed batch. Do not invoke `/prizmkit-code-review` for this planner-output gate; `/prizmkit-code-review` remains the implementation/code-diff review gate after `/prizmkit-implement`.
22
22
 
23
23
  ## Review Scope
24
24
 
25
- 1. For ordinary append flow, use the additions-only draft and the append result's stable bug IDs (`B-*`) as the change set; do not compare complete pre/post historical arrays in AI context.
25
+ 1. Treat the draft batch as the change set. Its `B-*` IDs are the sequential `context` IDs the writer demands at insert time, so the IDs reviewed are the IDs that land; do not compare complete pre/post historical arrays in AI context.
26
26
  2. Root project prose is reviewable content, not generator metadata. Read it through `context`; review new or changed `project_description` and `global_context` even when no bug item changed. Ignore root generator metadata and formatting-only differences such as `$schema`, `created_at`, and `created_by`.
27
27
  3. Treat bugs as changed only when item fields changed; load and review newly added bug IDs and explicitly changed bug IDs through `show`.
28
28
  4. Preserve unchanged historical bugs. Do not load unchanged entries merely to establish review completeness. Use the full-list validator for dependency/DAG truth; use `show` for an old dependency or overlap only when a specific reviewed bug requires semantic inspection.
@@ -48,6 +48,7 @@ For every reviewed bug entry, check:
48
48
  - Incident scope: keep one bug per task unless the same root cause or same failing contract is confirmed; do not domain-merge by module
49
49
  - Injected-field fidelity: confirmed actual/expected behavior and completion evidence are in `description` and `acceptance_criteria`; AI rewrite is allowed; dropping a confirmed item is not
50
50
  - Size: there is no word-count upper limit and no acceptance-criteria count upper limit
51
+ - Insert feasibility: every `dependencies` entry on a committed ID exists in the final list, the batch uses the consecutive IDs `context` reported, and the merge dry run returns `"valid": true`. Draft-only validation cannot see the merged graph, so a `PASS` without this check is a verdict the writer may reject.
51
52
  - Browser interaction and verification fields for UI-reproducible bugs when applicable
52
53
 
53
54
  ## Headless Context Completeness Gate
@@ -80,32 +81,27 @@ Do not add new JSON fields, context objects, schema versions, or pipeline runtim
80
81
  1. Present findings with IDs, severity, evidence, and suggested draft/source changes.
81
82
  2. Accept only findings that improve planner correctness, completeness, or downstream bug-fix execution readiness.
82
83
  3. Apply accepted fixes to `.prizmkit/plans/bug-fix-list.draft.json` or the in-memory draft object first.
83
- 4. For an ordinary incremental additions-only draft, rerun the existing script's append command:
84
+ 4. Re-check the fixed draft without writing:
84
85
 
85
86
  ```bash
86
- python3 ${SKILL_DIR}/scripts/validate-bug-list.py append --input .prizmkit/plans/bug-fix-list.draft.json --output .prizmkit/plans/bug-fix-list.json --replace-tail
87
+ python3 ${SKILL_DIR}/scripts/validate-bug-list.py append --input .prizmkit/plans/bug-fix-list.draft.json --output .prizmkit/plans/bug-fix-list.json --dry-run
87
88
  ```
88
89
 
89
- `--replace-tail` is allowed only for the exact final-list suffix whose IDs match this session's additions, so accepted local-review fixes replace the current session's entries without duplicating or loading history. If the suffix does not match exactly, stop rather than rewriting another task.
90
+ The dry run enforces the same base, exact-ID, dependency, and complete-DAG checks as the real insert, so keep it green instead of discovering a merge conflict after `PASS`. A new list or explicit full-list rewrite has no merged graph to check and nothing to overwrite, so its single post-`PASS` `generate` is the validator; if it rejects the draft, fix and retry, because no file was written.
90
91
 
91
- For a new list or explicit full-list rewrite, regenerate through the existing script's complete-draft command:
92
-
93
- ```bash
94
- python3 ${SKILL_DIR}/scripts/validate-bug-list.py generate --input .prizmkit/plans/bug-fix-list.draft.json --output .prizmkit/plans/bug-fix-list.json
95
- ```
96
-
97
- 5. Re-run append/generation until valid. Do not hand-patch `.prizmkit/plans/bug-fix-list.json` as the source of truth and do not add a user approval round for the mechanical rewrite.
92
+ 5. Never hand-patch `.prizmkit/plans/bug-fix-list.json` as the source of truth and do not add a user approval round for the mechanical rewrite.
98
93
  6. Repeat the local review and Headless Context Completeness Gate only for entries changed by accepted fixes.
99
- 7. Do not report `PASS` until every required fresh-session answer is available and final validation passes after regeneration.
100
- 8. After `PASS`, delete `.prizmkit/plans/bug-fix-list.draft.json` before final handoff when it is an ordinary internal draft. Retain it only for explicit draft-save, interruption or blocking before the terminal gates, or cleanup failure; report the retained path and reason. Cleanup failure leaves the reviewed final list valid but must be reported as stale recovery state.
94
+ 7. Do not report `PASS` until every required fresh-session answer is available and the draft validation plus merge dry run pass.
95
+ 8. After `PASS`, insert the batch exactly once (`append`, or `generate` for a new list), confirm the writer's `appended_ids`, then delete `.prizmkit/plans/bug-fix-list.draft.json`. Retain a draft only under the conditions in `${SKILL_DIR}/references/error-recovery.md`; report the retained path and reason.
101
96
 
102
97
  ## Report Format
103
98
 
104
99
  Report in the final handoff summary:
105
100
 
106
101
  - `Local generated-plan review: PASS` or `NEEDS_FIXES`
107
- - Reviewed bug IDs and reviewed root prose (`project_description` / `global_context`) when applicable
102
+ - Reviewed batch IDs and reviewed root prose (`project_description` / `global_context`) when applicable
103
+ - Merge dry-run result
108
104
  - Accepted fixes, or `none`
109
- - Final validation result
105
+ - Insert result: the single writer run and the `appended_ids` it reported
110
106
  - Draft cleanup result: `removed`, or retained path and recovery reason
111
- - Note when review was not applicable because no new final planning content was written
107
+ - Note when review was not applicable because no new planning content was written
@@ -15,6 +15,7 @@ Usage:
15
15
  python3 validate-bug-list.py context --input .prizmkit/plans/bug-fix-list.json
16
16
  python3 validate-bug-list.py show --input .prizmkit/plans/bug-fix-list.json --id B-001
17
17
  python3 validate-bug-list.py append --input additions.json --output .prizmkit/plans/bug-fix-list.json
18
+ python3 validate-bug-list.py append --input additions.json --output .prizmkit/plans/bug-fix-list.json --dry-run
18
19
  python3 validate-bug-list.py generate --input draft.json --output .prizmkit/plans/bug-fix-list.json
19
20
 
20
21
  Exit codes:
@@ -477,6 +478,11 @@ def cmd_append(args):
477
478
  _err(" " + error)
478
479
  return 1
479
480
 
481
+ if getattr(args, "dry_run", False):
482
+ _info("Dry run: {} bug(s) would be appended to {}".format(
483
+ len(prepared), args.output))
484
+ return 0
485
+
480
486
  try:
481
487
  _write_json_atomic(args.output, merged)
482
488
  except Exception as exc:
@@ -605,6 +611,11 @@ def main():
605
611
  action="store_true",
606
612
  help="Replace the exact existing suffix with the same IDs after local review",
607
613
  )
614
+ p_append.add_argument(
615
+ "--dry-run",
616
+ action="store_true",
617
+ help="Validate the would-be merged list without writing it",
618
+ )
608
619
 
609
620
  # -- generate --
610
621
  p_generate = subparsers.add_parser(
@@ -59,7 +59,7 @@ The user chose this skill intentionally. Respect that choice.
59
59
 
60
60
  ## Draft Lifecycle (Hard Rule)
61
61
 
62
- In an ordinary successful flow, `.prizmkit/plans/feature-list.draft.json` is internal writer/review input, not a user approval artifact or separate deliverable. Keep it through `generate`/`append`, validation, and the complete Local Generated-Plan Review fix loop. After the Local Generated-Plan Review returns `PASS` and final validation passes, delete the ordinary internal draft before final handoff. Report `Draft cleanup: removed`. Present the final written result. Retain the draft only for explicit draft-save, interruption or blocking before terminal gates, or cleanup failure; report its path and reason. Cleanup failure does not invalidate an already reviewed and validated final list, but makes the file stale recovery state. Never delete explicit recovery state merely because an older valid final exists. For later adjustments, recreate only the minimum source draft from confirmed in-memory entries or exact-ID `show`; ordinary appends must preserve the exact current suffix and use `append --replace-tail` without loading unrelated history.
62
+ In an ordinary successful flow, `.prizmkit/plans/feature-list.draft.json` is a private reasoning workspace: never presented as a deliverable, never given its own approval round, never retained after the batch lands. Build the batch there, validate it there, and run the entire Local Generated-Plan Review against it; the final list is written exactly once, after that review returns `PASS`, by a single `append` (existing list) or `generate` (new list). Then delete the draft immediately and report `Draft cleanup: removed`. A batch lost before it lands is regenerated from the confirmed decisions rather than recovered. Conditions that must keep a draft — explicit draft-save, interruption, a writer-rejected insert, cleanup failure — are defined in `${SKILL_DIR}/references/error-recovery.md`; name any retained path in the terminal report. For later adjustments, recreate only the minimum source draft from confirmed in-memory entries or exact-ID `show`; modifying entries this session did not create is the one case that still uses `append --replace-tail` for the exact current suffix.
63
63
 
64
64
  ## Fresh-Session Task Contract (Hard Rule)
65
65
 
@@ -154,14 +154,14 @@ Before questions, check optional context files (never block if absent):
154
154
  - `.prizmkit/config.json` (existing stack preferences and detected tech stack)
155
155
  - `.prizmkit/plans/project-brief.md` (project context from app-planner, if available)
156
156
  - existing `.prizmkit/plans/feature-list.json` (required for incremental mode; inspect it only through the bounded commands below)
157
- - Platform instruction file: use the `platform` field in `.prizmkit/manifest.json` as source of truth when present (`codex` → `AGENTS.md`, `cursor` → existing user-owned `AGENTS.md` when present, `claude` → `CLAUDE.md`, `codebuddy` → `CODEBUDDY.md`). A comma-separated list selects those hosts; the five-name form or an older stored `all` means read every matching file. `both` is not a supported alias.
157
+ - Platform instruction file: use the `platform` field in `.prizmkit/manifest.json` as source of truth when present (`codex` → `AGENTS.md`, `cursor` → existing user-owned `AGENTS.md` when present, `antigravity` → existing user-owned `GEMINI.md` or `AGENTS.md` when present, `claude` → `CLAUDE.md`, `codebuddy` → `CODEBUDDY.md`). A comma-separated list selects those hosts; the six-name form or an older stored `all` means read every matching file. `both` is not a supported alias.
158
158
  - If `.prizmkit/prizm-docs/root.prizm` is absent and the project has existing source code, scan the directory structure to understand the codebase layout:
159
159
  ```bash
160
160
  find . -maxdepth 2 -type d \
161
161
  -not -path '*/node_modules/*' -not -path '*/.git/*' \
162
162
  -not -path '*/dist/*' -not -path '*/build/*' \
163
163
  -not -path '*/__pycache__/*' -not -path '*/vendor/*' \
164
- -not -path '*/.agents/*' -not -path '*/.codex/*' \
164
+ -not -path '*/.agent/*' -not -path '*/.agents/*' -not -path '*/.codex/*' \
165
165
  -not -path '*/.claude/*' -not -path '*/.codebuddy/*' \
166
166
  -not -path '*/.cursor/*' -not -path '*/.prizmkit/*' \
167
167
  | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
@@ -242,8 +242,8 @@ For ordinary incremental planning, NEVER read the complete existing `.prizmkit/p
242
242
  2. Inspect those pairs only for material continuation, duplication, conflict, a shared public behavior contract, or an execution prerequisite. Add no historical content by default. Chronology, broad module overlap, shared technology, reusable implementation ideas, or similar wording alone do not establish relevance.
243
243
  3. Incorporate only the minimum exact information whose omission would make scope, behavior, compatibility, acceptance criteria, or dependency ordering incorrect. Reject vague `related to F-123` text and whole-description copying; add an old ID to `dependencies` only when it is a real execution prerequisite.
244
244
  4. Only for an explicitly identified old ID or a validation error, run `python3 ${SKILL_DIR}/scripts/validate-and-generate.py show --input .prizmkit/plans/feature-list.json --id F-NNN`.
245
- 5. For append-only planning, write `.prizmkit/plans/feature-list.draft.json` with exactly one root field, `features`, containing non-empty unchanged-schema items. This bounded draft is internal transport/recovery state, not a user approval artifact. Required draft fields are `id`, `title`, `description`, `priority`, `dependencies`, and `acceptance_criteria`; `status` may be omitted and defaults to `pending`; existing optional fields remain allowed. Copy no root metadata or historical features.
246
- 6. After consequential decisions and the pre-generation gate pass, immediately run `append`: `python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json`. Do not ask for separate user approval merely to promote the draft into the final list. The command validates the base, IDs, dependencies, and complete DAG before atomic replacement. Apply review fixes only to the bounded additions and rerun `append --replace-tail` for the exact current suffix, then follow §Draft Lifecycle before presenting the final written result. `generate` remains the initial-plan/full-rewrite path.
245
+ 5. For append-only planning, write `.prizmkit/plans/feature-list.draft.json` with exactly one root field, `features`, containing non-empty unchanged-schema items. This bounded draft is a private reasoning workspace and the review target, not a user approval artifact or a deliverable. Required draft fields are `id`, `title`, `description`, `priority`, `dependencies`, and `acceptance_criteria`; `status` may be omitted and defaults to `pending`; existing optional fields remain allowed. Copy no root metadata or historical features.
246
+ 6. After consequential decisions and the pre-generation gate pass, write the batch to the additions-only draft with the `context` IDs and check merge feasibility without writing: `python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json --dry-run`. Do not ask for separate user approval merely to promote the draft into the final list. The dry run applies the same base, ID, dependency, and DAG checks the real insert will, so a `PASS` review is a promise the insert keeps. Run the real `append` once, after §Local Generated-Plan Review Gate returns `PASS`, then follow §Draft Lifecycle. `generate` remains the initial-plan/full-rewrite path.
247
247
  ## Scenario Routing
248
248
  Classify user intent first:
249
249
 
@@ -311,11 +311,10 @@ Execute the planning workflow in conversation mode with mandatory checkpoints:
311
311
  4.2 **Browser interaction** (mandatory for fullstack/frontend projects) — see §Browser Interaction Planning below. Qualifying features get `browser_interaction` by default. Only confirm with the user as a batch summary; do NOT ask per-feature.
312
312
  5. Verify DAG/order/priorities and show the mandatory priority/complexity calibration table with short rationales for every item
313
313
  6. Run the pre-generation Headless Context Completeness Gate (see §Pre-Generation Completeness Review below)
314
- 7. Build or append `.prizmkit/plans/feature-list.json`
314
+ 7. Build the batch in `.prizmkit/plans/feature-list.draft.json` with the `context` IDs; write no final list yet
315
315
  8. Apply default testing strategy (see §Testing Defaults below)
316
- 9. Validate and fix until pass
317
- 10. Run the mandatory Local Generated-Plan Review Gate (see §Local Generated-Plan Review Gate below); apply accepted fixes to the draft/source plan, regenerate, and revalidate until pass, then complete §Draft Lifecycle cleanup
318
- 11. Summarize final feature table with local review result, validation outcome, and draft cleanup result
316
+ 9. Validate the draft batch and fix until pass, then run the mandatory Local Generated-Plan Review Gate (see §Local Generated-Plan Review Gate below) against it; apply accepted fixes to the draft, revalidate, and repeat until `PASS`
317
+ 11. Insert the batch once (`append`, or `generate` for a new list), complete §Draft Lifecycle cleanup, and summarize the final feature table with the inserted IDs, local review verdict, writer result, and cleanup result
319
318
 
320
319
  ### Checkpoints (Mandatory Gates)
321
320
 
@@ -329,9 +328,9 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
329
328
  | **CP-FP-3.1** | Browser Interaction Applied | Qualifying features have `browser_interaction` field; user confirmed or opted out | 4 |
330
329
  | **CP-FP-3.2** | Testing Defaults Applied | All features have appropriate testing expectations | 7 |
331
330
  | **CP-FP-3.3** | Completeness Review Passed | Every new or changed feature passes fresh-session simulation from `description` and `acceptance_criteria` without conversation history or `user_context` | 6 |
332
- | **CP-FP-4** | `.prizmkit/plans/feature-list.json` Generated | Schema validates, all required keys present | 7-8 |
333
- | **CP-FP-5** | Final Validation Pass | Python script returns `"valid": true` with zero errors | 9 |
334
- | **CP-FP-6** | Local Plan Review Passed | Local generated-plan review loaded `${SKILL_DIR}/references/generated-plan-review.md`, reviewed only newly added/changed feature entries, applied accepted fixes through draft/source data, regenerated, revalidated, and completed terminal draft cleanup or reported why recovery state was retained | 10-11 |
331
+ | **CP-FP-4** | Draft Batch Ready | Additions-only or complete draft holds the whole batch with `context` IDs; final list still untouched | 7-8 |
332
+ | **CP-FP-5** | Draft Validation Pass | Draft validation plus the merge dry run return `"valid": true` with zero errors | 9 |
333
+ | **CP-FP-6** | Reviewed, Then Inserted Once | Local generated-plan review loaded `${SKILL_DIR}/references/generated-plan-review.md`, reviewed only the draft batch, applied accepted fixes through the draft, revalidated, returned `PASS`, then ran exactly one `append`/`generate` whose `appended_ids` match the batch, and removed the draft | 10-11 |
335
334
 
336
335
  **Resume Detection**: If existing artifacts are found, read `${SKILL_DIR}/references/error-recovery.md` §Resume Support for checkpoint-based resumption.
337
336
 
@@ -378,12 +377,12 @@ For simple incremental planning, skip detailed Phase 2-3 analysis:
378
377
  3. Generate next sequential feature IDs
379
378
  4. Draft features (title + description + acceptance_criteria + dependencies)
380
379
  5. Run the mandatory pre-generation Headless Context Completeness Gate from Phase 6 on every drafted feature; repair the draft until each returns `PASS`.
381
- 6. Write the additions-only draft as internal input and immediately call the append command without a second draft-approval pause:
380
+ 6. Write the additions-only draft as internal input — no second draft-approval pause — and check merge feasibility without writing:
382
381
  ```bash
383
- python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json
382
+ python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json --dry-run
384
383
  ```
385
- 7. If valid → run the mandatory Local Generated-Plan Review Gate, complete §Draft Lifecycle cleanup, then present the final written result and recommend the next step
386
- 8. If invalid → apply fixes to the additions-only draft, re-run `append` (max 2 attempts, then escalate to full workflow)
384
+ 7. If valid → run the mandatory Local Generated-Plan Review Gate on the draft, insert once with `append`, complete §Draft Lifecycle cleanup, then present the final written result and recommend the next step
385
+ 8. If invalid → apply fixes to the additions-only draft and re-run the dry run (max 2 attempts, then escalate to full workflow)
387
386
 
388
387
  ## Browser Interaction Planning
389
388
 
@@ -433,13 +432,13 @@ Key requirements:
433
432
  python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json
434
433
  ```
435
434
 
436
- `generate` fills root defaults for complete drafts. `append` preserves root metadata and historical features, defaults missing new statuses, validates the merged full list, and writes only after validation passes. In ordinary incremental flow, call `append` immediately after semantic gates; the draft is not a second approval checkpoint. If either command fails, fix its source draft and retry. Do not delete the draft until the Local Generated-Plan Review and final validation pass; then follow §Draft Lifecycle.
435
+ `generate` fills root defaults for complete drafts. `append` preserves root metadata and historical features, defaults missing new statuses, validates the merged full list, and writes only after validation passes. In ordinary incremental flow the draft is not a second approval checkpoint, but it is the review target, so the real `append` runs once, after the Local Generated-Plan Review returns `PASS`; use `append --dry-run` for every earlier merged check because it validates without writing. If the writer rejects the batch, fix its source draft and retry — a rejection never leaves a partial final list. Then follow §Draft Lifecycle.
437
436
 
438
437
  ## Local Generated-Plan Review Gate
439
438
 
440
- Run this gate after `.prizmkit/plans/feature-list.json` passes generation and validation, and before the final handoff. It applies whenever this session added or changed final feature entries. For validate-only, summary-only, or draft-save flows with no final content change, report that the gate is not applicable.
439
+ Run this gate after the batch is written to the draft and passes draft validation, and before anything is written to `.prizmkit/plans/feature-list.json`: the review target is the batch about to be inserted, not a file that already contains it. For validate-only, summary-only, or draft-save flows with no batch, report that the gate is not applicable.
441
440
 
442
- Read `${SKILL_DIR}/references/generated-plan-review.md` and follow it as the single source of truth. Review the actual additions-only draft and use bounded `context` plus explicit-ID `show` for new or changed final entries because `.prizmkit` files may be gitignored; do not load unchanged historical entries. Repeat the Headless Context Completeness Gate for every reviewed new or changed feature. Keep the review planning-only, apply accepted findings to the draft/source representation, update ordinary appended entries through `append --replace-tail`, rerun validation, and repeat the local review until it returns `PASS`. Complete §Draft Lifecycle cleanup before reporting the final written result.
441
+ Read `${SKILL_DIR}/references/generated-plan-review.md` and follow it as the single source of truth. Review the draft directly, reading `.prizmkit` artifacts from disk rather than from `git status` or `git diff`, because those files may be gitignored. Use bounded `context` and explicit-ID `show` only for already-committed entries whose contract or dependency semantics a reviewed item relies on; do not load unchanged historical entries. Repeat the Headless Context Completeness Gate for every reviewed new or changed feature. Keep the review planning-only: apply accepted findings to the draft, re-run draft validation and the merge dry run, and repeat until it returns `PASS`. Only then insert once, complete §Draft Lifecycle cleanup, and present the final written result. If the insert is rejected after `PASS`, nothing landed: fix the draft, re-run validation and the dry run, and re-review the changed entries.
443
442
 
444
443
  ## Testing Defaults (Phase 8)
445
444
 
@@ -485,11 +484,12 @@ When the session appears to be ending:
485
484
 
486
485
  ## Handoff Message Template
487
486
 
488
- After successful validation and the Local Generated-Plan Review Gate, report:
487
+ After the batch is inserted, report:
489
488
  1. Output file path
490
489
  2. Total features + newly added features
491
490
  3. Dependency and priority highlights
492
- 4. Local generated-plan review result: verdict, reviewed feature IDs plus reviewed root prose when applicable, accepted fixes (or "none"), final validation result, and draft cleanup result (`removed` or retained path/reason)
493
- 5. Recommended next action: `feature-pipeline-launcher`
491
+ 4. Local generated-plan review result: verdict, reviewed batch IDs plus reviewed root prose when applicable, and accepted fixes (or "none")
492
+ 5. Insert result: the writer's `appended_ids` from the single post-review run, plus its validation output and the draft cleanup result (`removed`, or retained path and reason)
493
+ 6. Recommended next action: `feature-pipeline-launcher`
494
494
 
495
495
  Then apply the post-planning handoff in §Scope Boundary (ask before proceeding; never auto-execute).
@@ -1,28 +1,28 @@
1
1
  # Generated Plan Review — Feature Planner
2
2
 
3
- Use this local review loop after `.prizmkit/plans/feature-list.json` has been generated and validated. This is a planner-output review, not an implementation/code-diff review.
3
+ Use this local review loop on the batch that is about to be inserted into `.prizmkit/plans/feature-list.json`. This is a planner-output review, not an implementation/code-diff review, and it runs before the insert so the verdict decides whether the batch lands.
4
4
 
5
5
  ## Trigger
6
6
 
7
- Run only when the current `feature-planner` session generated, appended, or rewrote final feature planning content. For validate-only, summary-only, or draft-save flows with no new final planning content, report: `Local generated-plan review: not applicable — no new final planning content written.`
7
+ Run only when the current `feature-planner` session produced a draft batch of new or changed features. For validate-only, summary-only, or draft-save flows with no new batch, report: `Local generated-plan review: not applicable — no new planning content written.`
8
8
 
9
- In ordinary incremental flow, the additions draft is internal transport/recovery state. After consequential decisions and the pre-generation gate pass, immediately run `append`; do not ask for separate user approval merely to promote the draft into the final list. Keep the draft through the bounded review/fix loop, then delete the ordinary internal draft before final handoff only after this review returns `PASS` and final validation passes.
9
+ The draft is the whole review surface. Nothing is written to the final list while this loop runs: the single insert happens only after a `PASS`, so the verdict decides whether the batch lands and no final list ever holds reviewed-looking entries that were never reviewed.
10
10
 
11
11
  ## Direct Artifact Reads
12
12
 
13
13
  Planning artifacts may be gitignored, untracked, or absent from staged and unstaged diffs. Read the actual files through bounded, source-first access:
14
14
 
15
- - Final list: `.prizmkit/plans/feature-list.json` — run the `context` command for root prose and recent IDs; do not load the complete historical list into AI context
16
- - Draft/source list when present: `.prizmkit/plans/feature-list.draft.json` — ordinary incremental flow contains only additions and may be read completely
15
+ - Review target: `.prizmkit/plans/feature-list.draft.json` — the additions-only or complete batch, read in full; this is the only planning content under review
16
+ - Final list: `.prizmkit/plans/feature-list.json` — run the `context` command for root prose and recent IDs; do not load the complete historical list into AI context, and do not expect this session's batch to appear in it yet
17
17
  - Pre-session final list snapshot if captured in memory before edits — retain only bounded root context, prior task count/next ID, and the five recent `{id, description}` pairs, not full history
18
18
  - In-memory draft object if the session has not written a draft file yet
19
- - Newly appended or explicitly modified final entries — load each known ID with `python3 ${SKILL_DIR}/scripts/validate-and-generate.py show --input .prizmkit/plans/feature-list.json --id F-NNN`
19
+ - Already-committed entries a reviewed item relies on — load each referenced ID with `python3 ${SKILL_DIR}/scripts/validate-and-generate.py show --input .prizmkit/plans/feature-list.json --id F-NNN`
20
20
 
21
- Do not rely on `git status`, `git diff`, or `git diff --cached` to decide whether planner output exists or changed. Do not invoke `/prizmkit-code-review` for this planner-output gate; `/prizmkit-code-review` remains the implementation/code-diff review gate after `/prizmkit-implement`.
21
+ Do not rely on `git status`, `git diff`, or `git diff --cached` to decide whether planner output exists or changed. If the final list already contains this session's batch, the insert ran before the verdict — report that instead of reviewing an already-landed batch. Do not invoke `/prizmkit-code-review` for this planner-output gate; `/prizmkit-code-review` remains the implementation/code-diff review gate after `/prizmkit-implement`.
22
22
 
23
23
  ## Review Scope
24
24
 
25
- 1. For ordinary append flow, use the additions-only draft and the append result's stable feature IDs (`F-*`) as the change set; do not compare complete pre/post historical arrays in AI context.
25
+ 1. Treat the draft batch as the change set. Its `F-*` IDs are the sequential `context` IDs the writer demands at insert time, so the IDs reviewed are the IDs that land; do not compare complete pre/post historical arrays in AI context.
26
26
  2. Root project prose is reviewable content, not generator metadata. Read it through `context`; review new or changed `project_description` and `global_context` even when no feature item changed. Ignore root generator metadata and formatting-only differences such as `$schema`, `created_at`, and `created_by`.
27
27
  3. Treat features as changed only when item fields changed; load and review newly added feature IDs and explicitly changed feature IDs through `show`.
28
28
  4. Preserve unchanged historical features. Do not load unchanged entries merely to establish review completeness. Use the full-list validator for dependency/DAG truth; use `show` for an old dependency only when a specific reviewed feature requires semantic inspection of that prerequisite.
@@ -49,6 +49,7 @@ For every reviewed feature entry, check:
49
49
  - Unused nested work: new or changed items MUST NOT store required work only in `user_context`; move it into `description` and `acceptance_criteria`
50
50
  - Injected-field fidelity: confirmed WHAT, constraints, non-goals, boundaries, and completion evidence are in `description` and `acceptance_criteria`; AI rewrite is allowed; dropping a confirmed item is not
51
51
  - Size: there is no word-count upper limit and no acceptance-criteria count upper limit; long contracts are not defects
52
+ - Insert feasibility: every `dependencies` entry on a committed ID exists in the final list, the batch uses the consecutive IDs `context` reported, and the merge dry run returns `"valid": true`. Draft-only validation cannot see the merged graph, so a `PASS` without this check is a verdict the writer may reject.
52
53
  - Browser interaction fields for qualifying frontend/fullstack features when applicable
53
54
 
54
55
  ## Headless Context Completeness Gate
@@ -82,32 +83,27 @@ Do not add new JSON fields, context objects, schema versions, or pipeline runtim
82
83
  1. Present findings with IDs, severity, evidence, and suggested draft/source changes.
83
84
  2. Accept only findings that improve planner correctness, completeness, or downstream execution readiness.
84
85
  3. Apply accepted fixes to `.prizmkit/plans/feature-list.draft.json` or the in-memory draft object first.
85
- 4. For an ordinary incremental additions-only draft, rerun the existing script's append command:
86
+ 4. Re-check the fixed draft without writing:
86
87
 
87
88
  ```bash
88
- python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json --replace-tail
89
+ python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json --dry-run
89
90
  ```
90
91
 
91
- `--replace-tail` is allowed only for the exact final-list suffix whose IDs match this session's additions, so accepted local-review fixes replace the current session's entries without duplicating or loading history. If the suffix does not match exactly, stop rather than rewriting another task.
92
+ The dry run enforces the same base, exact-ID, dependency, and complete-DAG checks as the real insert, so keep it green instead of discovering a merge conflict after `PASS`. An initial plan or explicit full-list rewrite has no merged graph to check and nothing to overwrite, so its single post-`PASS` `generate` is the validator; if it rejects the draft, fix and retry, because no file was written.
92
93
 
93
- For an initial plan or explicit full-list rewrite, regenerate through the existing script's complete-draft command:
94
-
95
- ```bash
96
- python3 ${SKILL_DIR}/scripts/validate-and-generate.py generate --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json
97
- ```
98
-
99
- 5. Re-run append/generation until valid. Do not hand-patch `.prizmkit/plans/feature-list.json` as the source of truth and do not add a user approval round for the mechanical rewrite.
94
+ 5. Never hand-patch `.prizmkit/plans/feature-list.json` as the source of truth and do not add a user approval round for the mechanical rewrite.
100
95
  6. Repeat the local review and Headless Context Completeness Gate only for entries changed by accepted fixes.
101
- 7. Do not report `PASS` until every required fresh-session answer is available and final validation passes after regeneration.
102
- 8. After `PASS`, delete `.prizmkit/plans/feature-list.draft.json` before final handoff when it is an ordinary internal draft. Retain it only for explicit draft-save, interruption or blocking before the terminal gates, or cleanup failure; report the retained path and reason. Cleanup failure leaves the reviewed final list valid but must be reported as stale recovery state.
96
+ 7. Do not report `PASS` until every required fresh-session answer is available and the draft validation plus merge dry run pass.
97
+ 8. After `PASS`, insert the batch exactly once (`append`, or `generate` for a new list), confirm the writer's `appended_ids`, then delete `.prizmkit/plans/feature-list.draft.json`. Retain a draft only under the conditions in `${SKILL_DIR}/references/error-recovery.md`; report the retained path and reason.
103
98
 
104
99
  ## Report Format
105
100
 
106
101
  Report in the final handoff summary:
107
102
 
108
103
  - `Local generated-plan review: PASS` or `NEEDS_FIXES`
109
- - Reviewed feature IDs and reviewed root prose (`project_description` / `global_context`) when applicable
104
+ - Reviewed batch IDs and reviewed root prose (`project_description` / `global_context`) when applicable
105
+ - Merge dry-run result
110
106
  - Accepted fixes, or `none`
111
- - Final validation result
107
+ - Insert result: the single writer run and the `appended_ids` it reported
112
108
  - Draft cleanup result: `removed`, or retained path and recovery reason
113
- - Note when review was not applicable because no new final planning content was written
109
+ - Note when review was not applicable because no new planning content was written
@@ -83,21 +83,21 @@ The additions-only `.prizmkit/plans/feature-list.draft.json` has exactly one roo
83
83
  }
84
84
  ```
85
85
 
86
- Each item uses the unchanged final feature-item schema. Required draft fields are `id`, `title`, `description`, `priority`, `dependencies`, and `acceptance_criteria`; `status` may be omitted and defaults to `pending`; all existing optional feature fields remain allowed. Root project metadata and historical features must not be copied into this draft. Treat it as internal transport/recovery state, not as a user approval artifact.
86
+ Each item uses the unchanged final feature-item schema. Required draft fields are `id`, `title`, `description`, `priority`, `dependencies`, and `acceptance_criteria`; `status` may be omitted and defaults to `pending`; all existing optional feature fields remain allowed. Root project metadata and historical features must not be copied into this draft. Treat it as a private reasoning workspace and the review target, not as a user approval artifact or a deliverable.
87
87
 
88
88
  ### Step 4: Rebalance Priority
89
89
 
90
90
  Default to append only. Reprioritizing historical tasks is an explicit old-task modification, not part of ordinary append flow; require the user to identify the affected IDs and load only those tasks with `show`.
91
91
 
92
- ### Step 5: Append and Validate
92
+ ### Step 5: Check Feasibility, Review, Then Insert Once
93
93
 
94
- After consequential decisions and the pre-generation semantic gate pass, immediately merge the additions-only draft with untouched history outside AI context:
94
+ After consequential decisions and the pre-generation semantic gate pass, check the additions against untouched history outside AI context without writing:
95
95
 
96
96
  ```bash
97
- python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json
97
+ python3 ${SKILL_DIR}/scripts/validate-and-generate.py append --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json --dry-run
98
98
  ```
99
99
 
100
- The append command validates the existing base, exact sequential new IDs, all old/new dependencies, and the complete DAG before atomically replacing the final list. Do not ask for separate user approval merely to promote the additions draft into the final list. Fix invalid additions and rerun until valid; during local review, correct the exact current suffix with `append --replace-tail`. Keep the draft through that fix loop. After review returns `PASS` and final validation passes, delete the ordinary internal draft before final handoff. For a later adjustment, recreate only the exact current additions from confirmed in-memory entries or explicit-ID `show` results before using `append --replace-tail`. Use `generate` only for an initial plan or an explicit full-list rewrite.
100
+ The dry run checks the existing base, exact sequential new IDs, all old/new dependencies, and the complete DAG exactly as the real insert will. Do not ask for separate user approval merely to promote the additions draft into the final list, and do not insert yet: run the Local Generated-Plan Review against the draft, apply accepted fixes there, and re-run this dry run until it stays green and the review returns `PASS`. Then insert once with the real `append` and delete the draft. For a later adjustment, recreate only the exact current additions from confirmed in-memory entries or explicit-ID `show` results before using `append --replace-tail`. Use `generate` only for an initial plan or an explicit full-list rewrite.
101
101
 
102
102
  ## Merge/Rewrite Rules
103
103
 
@@ -125,6 +125,6 @@ Use concise prompts during interaction:
125
125
  - [ ] Additions-only draft contains no root metadata or historical features
126
126
  - [ ] Atomic append ran immediately after semantic gates without a post-draft approval pause
127
127
  - [ ] Existing project conventions preserved from project evidence
128
- - [ ] Complete merged dependency graph validates through `append`
129
- - [ ] Ordinary internal draft was deleted after review and final validation, or its retained recovery path and reason were reported
128
+ - [ ] Complete merged dependency graph validates through the `append` dry run
129
+ - [ ] Batch was reviewed in the draft, inserted exactly once after `PASS`, and the draft was deleted or its retained recovery path and reason were reported
130
130
  - [ ] Next step recommendation: `feature-pipeline-launcher`
@@ -54,14 +54,14 @@ Split into additional top-level features only when:
54
54
 
55
55
  ### Phase 6: Generate + Validate
56
56
 
57
- 1. Write `.prizmkit/plans/feature-list.draft.json` as internal writer/review input after the main Skill's consequential decision and pre-generation gates pass.
58
- 2. Immediately generate the final file without a separate draft-approval pause:
57
+ 1. Write `.prizmkit/plans/feature-list.draft.json` as the private review workspace after the main Skill's consequential decision and pre-generation gates pass.
58
+ 2. Run the main Skill's mandatory Local Generated-Plan Review against that complete draft and apply accepted fixes through the draft. Nothing is written to `feature-list.json` yet.
59
+ 3. After review returns `PASS`, generate the final file once without a separate draft-approval pause:
59
60
  ```bash
60
61
  python3 ${SKILL_DIR}/scripts/validate-and-generate.py generate --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json
61
62
  ```
62
- 3. Fix draft errors, then re-run `generate` until validation passes.
63
- 4. Run the main Skill's mandatory Local Generated-Plan Review and apply accepted fixes through the complete draft.
64
- 5. After review returns `PASS` and final validation passes, delete the ordinary internal draft before final handoff. Retain it only under the main Skill's explicit recovery conditions and report the reason.
63
+ 4. If `generate` rejects the draft, fix the draft and retry; a rejection writes no file, so the final list is never partial.
64
+ 5. After the single successful `generate`, delete the draft and report `Draft cleanup: removed`. Retain it only under the main Skill's explicit recovery conditions and report the reason.
65
65
 
66
66
  ## Quality Rules
67
67
 
@@ -80,6 +80,6 @@ Split into additional top-level features only when:
80
80
  - [ ] User confirmed initial feature scope
81
81
  - [ ] IDs are sequential
82
82
  - [ ] `status` initialized to `pending`
83
- - [ ] Validation and Local Generated-Plan Review pass
84
- - [ ] Ordinary internal draft was deleted, or its retained recovery path and reason were reported
83
+ - [ ] Validation and Local Generated-Plan Review passed on the draft, then exactly one `generate` ran
84
+ - [ ] Ordinary internal draft was deleted after that single insert, or its retained recovery path and reason were reported
85
85
  - [ ] Next step recommendation: `feature-pipeline-launcher`
@@ -19,6 +19,7 @@ Usage:
19
19
  python3 validate-and-generate.py context --input .prizmkit/plans/feature-list.json
20
20
  python3 validate-and-generate.py show --input .prizmkit/plans/feature-list.json --id F-001
21
21
  python3 validate-and-generate.py append --input additions.json --output .prizmkit/plans/feature-list.json
22
+ python3 validate-and-generate.py append --input additions.json --output .prizmkit/plans/feature-list.json --dry-run
22
23
  python3 validate-and-generate.py generate --input draft.json --output .prizmkit/plans/feature-list.json
23
24
  python3 validate-and-generate.py summary --input .prizmkit/plans/feature-list.json [--format markdown|json]
24
25
  python3 validate-and-generate.py grade --workspace /.codebuddy/skill-evals/feature-planner-workspace --iteration iteration-1
@@ -837,6 +838,11 @@ def cmd_append(args):
837
838
  _err(" " + error)
838
839
  return 1
839
840
 
841
+ if getattr(args, "dry_run", False):
842
+ _info("Dry run: {} feature(s) would be appended to {}".format(
843
+ len(prepared), args.output))
844
+ return 0
845
+
840
846
  try:
841
847
  _write_json_atomic(args.output, merged)
842
848
  except Exception as exc:
@@ -1113,6 +1119,11 @@ def main():
1113
1119
  action="store_true",
1114
1120
  help="Replace the exact existing suffix with the same IDs after local review",
1115
1121
  )
1122
+ p_append.add_argument(
1123
+ "--dry-run",
1124
+ action="store_true",
1125
+ help="Validate the would-be merged list without writing it",
1126
+ )
1116
1127
 
1117
1128
  # -- generate --
1118
1129
  p_generate = subparsers.add_parser(
@@ -82,7 +82,7 @@ BROWNFIELD WORKFLOW (existing project):
82
82
  - TOP-LEVEL modules: directories directly under project root that contain source files or sub-directories with source files (e.g. `src/`, `internal/`, `lib/`)
83
83
  - SUB-MODULES: directories INSIDE a top-level module (e.g. `src/routes/`, `src/models/`)
84
84
  - Exact `root.prizm` is L0; top-level module M maps to direct-child `.prizmkit/prizm-docs/<M>.prizm` (L1); sub-module S maps to nested `.prizmkit/prizm-docs/<M>/<S>.prizm` (L2). Deeper source ownership remains L2 and never creates L3.
85
- - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.agents/`, `.codex/`, `.claude/`, `.codebuddy/`, `.pi/`, `.cursor/`, and the complete `.prizmkit/` framework directory. This excludes installed `.prizmkit/dev-pipeline/` artifacts but not canonical top-level `dev-pipeline/` source.
85
+ - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.agent/`, `.agents/`, `.codex/`, `.claude/`, `.codebuddy/`, `.pi/`, `.cursor/`, and the complete `.prizmkit/` framework directory. This excludes installed `.prizmkit/dev-pipeline/` artifacts but not canonical top-level `dev-pipeline/` source.
86
86
  - **Bounded discovery contract** — use the current Host's available directory-listing or file-search capability to enumerate at most two directory levels, apply the exclusions above before analysis, preserve parent/child relationships, and report the resulting project-relative structure. Do not require a POSIX shell pipeline or any other operating-system-specific command.
87
87
  3. Identify entry points by language convention
88
88
  4. Catalog dependencies (external packages)
@@ -20,13 +20,13 @@ Handles re-init without losing user edits:
20
20
  | Field | Type | Description |
21
21
  |-------|------|-------------|
22
22
  | `adoption_mode` | string | `"passive"` \| `"advisory"` \| `"active"` |
23
- | `platform` | string | Installed host metadata: a single id (`codebuddy`, `claude`, `codex`, `pi`, `cursor`), a canonical comma-separated subset such as `claude,cursor`, or the five-name form `codebuddy,claude,codex,pi,cursor`. It records installation, not a canonical behavior allowlist. Input alias `all` expands to the five names on write. |
23
+ | `platform` | string | Installed host metadata: a single id (`codebuddy`, `claude`, `codex`, `pi`, `cursor`, `antigravity`), a canonical comma-separated subset such as `claude,antigravity`, or the six-name form `codebuddy,claude,codex,pi,cursor,antigravity`. It records installation, not a canonical behavior allowlist. Input alias `all` expands to the six names on write. |
24
24
  | `tech_stack` | object | Detected or user-provided tech stack |
25
25
  | `tech_stack._auto_detected` | boolean | `true` if auto-detected, `false` if user-provided |
26
26
  | `detected_layers` | string[] | Development layers observed in the project. Written by prizmkit-init Phase 4.5. Values: `frontend` / `backend` / `database` / `mobile`. Empty only when no layers are observed. Always refreshed from code and never cleared by rule-adoption choices. |
27
27
  | `enabled_rule_profiles` | string[] | Rule profiles the user explicitly enabled. This is independent from `detected_layers`; an empty array means no custom profile is enabled, not that the project has no detected layers. |
28
28
 
29
- New writes must use a single host id, a canonical comma-separated subset, or the five concrete names. `all` is an installer input alias only. `both` is not a supported value.
29
+ New writes must use a single host id, a canonical comma-separated subset, or the six concrete names. `all` is an installer input alias only. `both` is not a supported value.
30
30
 
31
31
  ## Examples
32
32
 
@@ -603,7 +603,7 @@ HIERARCHY RULE: if directory X lives inside top-level module M, X is a sub-modul
603
603
 
604
604
  CAPACITY RULE: use MODULE_GROUPS whenever MODULE_INDEX cannot fit L0 within 4096B. Do not change hard limits for project size. Init does not create semantic or mirrored L2 placeholders; later Update/Rebuild/Migrate may create complete L2 documents when durable knowledge and unambiguous identity exist.
605
605
 
606
- EXCLUDE: .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .codex/, .agents/, .pi/, .cursor/, .prizmkit/
606
+ EXCLUDE: .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .codex/, .agent/, .agents/, .pi/, .cursor/, .prizmkit/
607
607
  SOURCE_BOUNDARY: Excluding `.prizmkit/` excludes the installed Runtime at `.prizmkit/dev-pipeline/`; never exclude a repository's canonical top-level `dev-pipeline/` source module by basename.
608
608
 
609
609
  ## 9.2 Post-Init Behavior
@@ -11,7 +11,7 @@ STEPS:
11
11
  - TOP-LEVEL modules: directories directly under project root (or under src/ for src-based layouts) that qualify.
12
12
  - SUB-MODULES: directories INSIDE a top-level module that qualify. Record them as source structure in the direct-child parent L1; if durable L2 is created later, its nested path mirrors the sub-module.
13
13
  - HIERARCHY RULE: exact `root.prizm` is L0; top-level module M maps to direct-child `.prizmkit/prizm-docs/<M>.prizm` (L1); directory X inside M maps to nested `.prizmkit/prizm-docs/<M>/<X>.prizm` (L2). Deeper source ownership remains L2 and never creates L3.
14
- - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .codex/, .agents/, .pi/, .cursor/, and the complete `.prizmkit/` framework directory. This excludes installed `.prizmkit/dev-pipeline/` artifacts but never excludes a repository's canonical top-level `dev-pipeline/` source module by basename. If total module count > 30, ask user for include/exclude patterns.
14
+ - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .codex/, .agent/, .agents/, .pi/, .cursor/, and the complete `.prizmkit/` framework directory. This excludes installed `.prizmkit/dev-pipeline/` artifacts but never excludes a repository's canonical top-level `dev-pipeline/` source module by basename. If total module count > 30, ask user for include/exclude patterns.
15
15
  3. Apply the Value Gate from SKILL.md and the format specification to every metadata, rule, pattern, dependency, file, and summary candidate. Keep navigational structure only when needed to locate ownership. Reject source-derivable signatures, history, test inventories, temporary conclusions, stale/duplicate meanings, procedures, and low-value file lists.
16
16
  4. Create `.prizmkit/prizm-docs/` and only the mirrored directories needed by documents that will exist. Do not create placeholder detail files.
17
17
  5. Generate `root.prizm` (L0) with concise PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY, navigation pointers, and only Value-Gate-qualified global RULES/PATTERNS/CROSS_CUTTING facts. Set `PRIZM_VERSION: 4`. Keep L0 a summary/pointer map; never copy child interfaces, data flow, traps, decisions, or full rules. No CHANGELOG sections/files, UPDATED/date metadata, feature/bug/refactor/task/session/run/pipeline/workflow IDs, branch names, absolute worktree paths, or `.prizmkit/specs` / `.prizmkit/dev-pipeline` artifact paths.