fix(skills): add Phase 3 Completion Gate to prevent skipping transcendence features

3ea8601dddf479a1696a5e509c7080aeb52ba2b1 · 2026-04-05 18:27:08 -0700 · Trevin Chow

The skill clearly says to build ALL transcendence features but there was
no hard gate between Phase 3 (Build) and Phase 4 (Shipcheck). The agent
could finish Priority 0 (data layer) and jump to shipcheck without
building any Priority 2 (transcendence) features. The Cal.com run
shipped with 4/8 transcendence features because of this.

The new gate counts transcendence features in the manifest vs commands
actually built, and blocks progression until they match.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Files touched

M skills/printing-press/SKILL.md

Diff

commit 3ea8601dddf479a1696a5e509c7080aeb52ba2b1
Author: Trevin Chow <trevin@trevinchow.com>
Date:   Sun Apr 5 18:27:08 2026 -0700

    fix(skills): add Phase 3 Completion Gate to prevent skipping transcendence features
    
    The skill clearly says to build ALL transcendence features but there was
    no hard gate between Phase 3 (Build) and Phase 4 (Shipcheck). The agent
    could finish Priority 0 (data layer) and jump to shipcheck without
    building any Priority 2 (transcendence) features. The Cal.com run
    shipped with 4/8 transcendence features because of this.
    
    The new gate counts transcendence features in the manifest vs commands
    actually built, and blocks progression until they match.
    
    Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 skills/printing-press/SKILL.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/skills/printing-press/SKILL.md b/skills/printing-press/SKILL.md
index 492de959..c3f90634 100644
--- a/skills/printing-press/SKILL.md
+++ b/skills/printing-press/SKILL.md
@@ -1226,6 +1226,20 @@ Include:
 - skipped body fields that remain
 - any generator limitations found
 
+### Phase 3 Completion Gate
+
+**MANDATORY. Do NOT proceed to Phase 4 until this gate passes.**
+
+Before moving to shipcheck, verify the build log against the absorb manifest:
+
+1. Count the transcendence features in the Phase 1.5 manifest's transcendence table
+2. Count the transcendence commands actually built (present in `internal/cli/` and registered in `root.go`)
+3. If built < manifest count, **STOP**. List the missing features and build them before proceeding
+
+The generator handles Priority 0 (data layer) and most of Priority 1 (absorbed API endpoints). Priority 2 (transcendence) is always hand-built — the generator does not produce these. If you skip Priority 2, the CLI ships without the features that differentiate it from every other tool.
+
+Do not rationalize skipping transcendence features because "the CLI already works for live API interaction." The absorb manifest was approved by the user. Build what was approved.
+
 ## Phase 4: Shipcheck
 
 Run one combined verification block.

← fb164adc feat(cli): per-endpoint header routing and auth inference fr · back to Cli Printing Press · feat(cli): flow transcendence features into generated README 96b9b42c →