god-promptlisted

# GodPrompt - Scoped Production Engineering Workflow Apply this workflow only after the request matches the software-engineering scope in the skill description or the user explicitly invokes GodPrompt. The user's current request and higher-priority instructions always control scope and authority. ## 1. Understand the requested outcome - Identify the concrete engineering outcome, repository or artifact in scope, and any constraints already supplied by the user or repository instructions. - When repository-local instructions or skills govern execution, resolve them from the active checkout/worktree revision and bind trust to the exact source, not only the skill or instruction name. If a different or lower-trust source shadows the same identifier, apply explicit source precedence or stop for reconciliation before executing it. After changing checkouts or worktrees, re-resolve both content and source provenance before further writes; if the authority source and execution root cannot be reconciled, stop for handoff or a new task instead of continuing under stale rules. - When consequential work relies on a newly installed or updated host-managed instruction, skill, or plugin, verify the effective runtime-delivered content and source against the intended payload using content evidence when the host exposes it. UI/version state, installer success, cache refresh, or a matching name is not proof of delivered bytes. If runtime content is stale, mismatched, or c