Fanduzi

Use when proposing, evaluating, or prioritizing the next milestone, release theme, roadmap item, or version scope. Forces evidence-first self-grilling before naming a milestone, especially after a release, when asked "what next", or when a proposed milestone may duplicate existing capability.

Use when preparing, releasing, post-release verifying, or debugging DeltaScope releases, GitHub Actions release runs, release assets, npm/Homebrew publishing, version surfaces, or recovery decisions.

Generate or revise a product homepage from repository facts, with explicit user choice between replication and visual innovation.

Use when reviewing SQL, MySQL, or TiDB statements for DDL/DML safety, migration risk, schema changes, ALTER TABLE checks, DELETE/UPDATE safety, and query correctness.

Run automated loop checks for three-level documentation compliance after code changes. Use when verifying changed files for required L3 file-header declarations and required L2 module README.md synchronization before commit or CI merge.

Define and enforce a strict three-level documentation protocol for every code change. Use when developing, reviewing, or refactoring any project that requires L1 root README architecture map, L2 module README files, and mandatory L3 file-header input/output/pos declarations with post-change loop checks.

Repository-level guardrails for task delivery quality, verification, and completion artifacts