Writing & Content Workflows

Forensic internationalization & localization audit v1 (Gestalt-Popper). 18-phase deep analysis of everything that decides whether the product is WORLD-READY: hardcoded user-facing string detection (JSX text, alt/title/aria/placeholder attributes, toast/error/email/notification copy), i18n framework wiring integrity (key existence, namespace structure, interpolation contract), locale routing & detection (path/subdomain/cookie/Accept-Language, persistence across navigation), pluralization rules (CLDR plural categories: zero/one/two/few/many/other), gender/grammatical agreement, date/time formatting (Intl.DateTimeFormat, timezone), number/percent/unit formatting, currency formatting (ISO 4217, symbol placement, minor-unit precision), RTL support (dir attribute, logical CSS properties, bidi-safe interpolation, mirrored icons), translation completeness + fallback chains, character encoding (UTF-8 end to end, normalization, mojibake), locale-aware sorting & collation (Intl.Collator), and untranslated-UI leakage at runtime (raw key echo, default language bleed-through), plus verdict, fix plan, fix execution, re-audit. Score /360. Preamble v1.0 compliant. Audit -> Plan -> Fix -> Re-audit. Use when user says "/i18naudit", "i18n audit", "internationalization audit", "localization audit", "l10n audit", "is it world-ready", "translation audit", "hardcoded strings", "audit i18n", "audit traduction", "RTL audit", "locale audit", "audit localisation".

Invoke when a project must convert leads into paying customers and you need to decide the revenue engine (sales-led vs PLG) and the closing/onboarding mechanism before writing copy or coding an onboarding. Also fires on EN: 'sales-led vs PLG', 'founder-led sales', 'B2B sales process', 'discovery call', 'Jobs-to-be-Done', 'demo to close', 'handle objections', 'feel-felt-found', 'aha moment', 'activation / time-to-value', 'signup-flow CRO', 'behavioral follow-up sequence', 'how do I price the sales motion'; and FR: 'vente B2B', 'PLG ou sales-led', 'founder-led sales', 'appel de discovery', 'diagnostic avant pitch', 'closing', 'traiter les objections', 'feel-felt-found', 'aha moment', 'activation / time-to-value', 'onboarding qui vend', 'séquence de relance comportementale', 'la fortune est dans le follow-up'. Use when intérêt existe mais le revenu ne suit pas, ou avant d'automatiser une vente jamais réussie à la main.

Forensic observability audit v1 (Gestalt-Popper). 18-phase deep analysis of whether you can SEE WHAT THE SYSTEM DOES IN PRODUCTION: structured logging coverage, log-level correctness, trace/span propagation (OpenTelemetry), correlation/request IDs, metrics instrumentation (RED: Rate-Errors-Duration, USE: Utilization-Saturation-Errors), dashboard coverage, alerting rules and thresholds, SLO/SLI definition and error budgets, error tracking (Sentry/Rollbar) coverage and grouping, log retention + PII-in-logs hygiene, sampling strategy, cardinality control, health/readiness probes, log/metric/trace correlation, on-call runbooks, and the "3am incident" debuggability test, plus verdict, fix plan, fix execution, re-audit, and instrumentation safety gate. Score /360. Preamble v1.0 compliant. Audit -> Plan -> Fix -> Re-audit. Use when user says "/observabilityaudit", "observability audit", "can we see what it does", "are we observable", "logging audit", "tracing audit", "metrics audit", "do we have dashboards", "alerting audit", "slo audit", "is it instrumented", "can we debug prod", "blind in prod".

Forensic release & shipping-safety audit v1 (Gestalt-Popper). 20-phase deep analysis of whether shipping is SAFE and REVERSIBLE: CI/CD pipeline integrity, build reproducibility (deterministic, hermetic, lockfile-pinned), semantic versioning correctness, changelog accuracy (does it match the diff?), database migration safety (forward AND rollback, expand-contract, backfill ordering), blue-green / canary / rolling deployment strategy, the rollback procedure (does it actually exist, is it tested, is it one command?), feature-flag hygiene (stale flags, kill switches, default-safe), deploy gates (required checks, approvals, smoke tests), secret handling in the pipeline (no plaintext in logs, masked, least-privilege deploy tokens), post-deploy verification (health checks, 200 probe, error-budget burn), artifact provenance & supply-chain signing, environment parity (dev/staging/prod drift), zero-downtime guarantees, dependency-on-deploy ordering, plus verdict, fix plan, fix execution, re-audit, and a deploy-safety gate. Answers "Is shipping SAFE + reversible?". Score /400. Preamble v1.0 compliant. Audit -> Plan -> Fix -> Re-audit. Use when user says "/releaseaudit", "release audit", "is it safe to ship", "is the deploy reversible", "can we roll back", "ci/cd audit", "pipeline audit", "deploy safety", "migration safety", "rollback procedure", "release readiness", "ship safety check", "audit the release process".