five-phase-pass

Propagate dean-stack monorepo changes through five phases with deterministic gating.

Updated May 23, 2026

Search Tags:#Playwright #Storybook #monorepo #documentation sync #code propagation #generator templates #CI gate

Ready to run

npx skills add https://github.com/matthewharwood/dean-n-dean --skill five-phase-pass

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: five-phase-pass
Source: https://github.com/matthewharwood/dean-n-dean/tree/main/.agents/skills/five-phase-pass
Command: npx skills add https://github.com/matthewharwood/dean-n-dean --skill five-phase-pass

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents dean-stack monorepo changes from drifting across the live app, generator template, regenerated test material, owning docs, and the wider skill ecosystem.

Core Features & Use Cases

Five-phase propagation: Drives the same change through P1 apps/web, P2 the generator template, P3 regeneration + CI gate, P4 docs/skill ownership updates, and P5 cross-skill coherence.
Generator integrity & CI reliability: Ensures apps born from the template aren’t stale and that the Playwright/Storybook gate runs without port/process races.
Baseline audits: Supports a P5-only baseline run to audit the cumulative current stack for narrative or conceptual drift.

Quick Start

Ask the AI to run the five-phase pass for your change, for example: propagate the change to remove jotai-family everywhere and verify the gate passes.

Frequently Asked Questions about five-phase-pass

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep monorepo changes coherent across web apps, generator templates, and documentation?▼

To keep monorepo changes coherent, use a five-phase pass that propagates edits through the web app, generator template, test artifacts, docs, and cross-skill audits. This prevents drift across the stack by enforcing deterministic CI gating and template diff parity checks.

Why does my Playwright or Storybook CI gate fail with port or process races?▼

Playwright and Storybook CI gates fail with port or process races when stale Vite processes conflict. A deterministic five-phase pass pre-kills Storybook and Vite processes before running validation checks, ensuring the CI gate runs reliably without port collisions.

What is the best way to sync a generator template change with regenerated test-project validation artifacts?▼

The best way to sync generator template changes with test artifacts is running a phased propagation that applies {{name}} substitution diffs, regenerates the test-project, and validates the output against a deterministic CI gate to ensure template parity.

Can I audit my current stack for narrative or conceptual drift without running all five phases?▼

Yes, you can audit cumulative stack drift without all five phases by executing a P5-only baseline run. This performs a cross-skill coherence sweep across skill files and AGENTS/README to identify narrative inconsistencies without applying new code changes.

How do I update owning documentation and skill files when propagating a monorepo code change?▼

To update owning documentation during monorepo code propagation, the five-phase pass executes a mechanical and narrative consistency sweep across skill files and AGENTS/README during phase four, ensuring all documentation reflects the applied template and web app changes.

Does the five-phase pass require a specific execution order for validating template changes?▼

The five-phase pass requires strict phase ordering to validate template changes correctly. It sequentially processes the web app, generator template, regenerated artifacts, owning documentation, and cross-skill audits, ensuring deterministic gating via bun run check completes without process conflicts.