Scan engine phases for silent failures before a cycle run.
npx skills add https://github.com/pnils08/GodWorld --skill pre-mortem-pnils08
Please help me install this Agent Skill. Skill: pre-mortem Source: https://github.com/pnils08/GodWorld/tree/main/.claude/skills/pre-mortem Command: npx skills add https://github.com/pnils08/GodWorld --skill pre-mortem-pnils08
This Skill helps engineering teams prevent cascading failures by proactively scanning all engine phases prior to a cycle run. It validates dependency flow between ctx fields, checks for proper sheet headers, detects risky code patterns, and flags cascade risks that could derail cycle execution.
Run the pre-mortem scan before starting a new cycle to generate a risk report and catch potential cascading failures early.
High-intent search queries and answers about installing and using this skill.
To prevent silent engine failures before a cycle run, scan all phase engines to detect ctx dependency violations, header misalignments, and risky code patterns like Math.random usage. This generates a structured risk report with file:line references for early mitigation.
Ctx field dependency verification checks data flow across Phase 5 sub-engines and related phases to ensure ctx fields are written before they are read. This prevents cascading failures caused by out-of-order data access during cycle execution.
Validate sheet headers and write patterns by scanning phase directories for alignment issues and restricted sheet write actions. This pre-mortem check prevents silent data loss by confirming write targets exist, are writable, and match expected headers.
Yes, the pre-mortem scan detects deterministic programming issues including Math.random usage across Phase01-config through Phase10-persistence. It flags these risky code patterns to ensure cycle reproducibility and prevent silent execution failures.
Yes, you can validate neighborhood references to ensure only canonical Oakland districts are referenced, and verify write-intent targets to confirm target sheets exist and are writable. These checks run across all phase engines before cycle execution.
The scan is limited to detecting known risk patterns across Phase01-config through Phase10-persistence, including ctx flow ordering, header misalignments, and Math.random usage. It produces a risk report but does not execute or modify the cycle run itself.
pnils08Identifies code-health issues in phase*/ and utilities/ JavaScript sources, including Math.random() usage and dead code, with severity and file references.
lawvableEvaluate whistleblower policy compliance and draft compliant internal policies.
pnils08Map exported functions, context reads/writes, and dependencies across engine phase files.
AppsVortexAutomate post-launch failure analysis using Gary Klein's pre-mortem methodology.
