pleko-script/web-app-completeness
Plan, build, audit, and align the operational capabilities that make data-heavy web applications complete.
Audit an existing operational or data-heavy web-app area for missing, unreachable, unsafe, or unverifiable product capabilities. Use when the user explicitly invokes $completeness-audit for an evidence-based review of an app, module, or feature; explicit invocation is required. Do not invoke when the request is for marketing, e-commerce, editorial, implementation, planning, styling critique, generic code review, or cross-module consistency comparison.
Build a new or materially expanded resource or operational workflow in a data-heavy web app with an explicit completeness contract. Use when the user explicitly requests implementation of an admin, CRUD, directory, queue, or management feature, including requests that require a contract or approval stop before edits. Do not invoke when the requested deliverable is only a plan, or when the request is for marketing, e-commerce, editorial, styling-only work, an audit, a refactor-only task, a narrow bug fix, or a tiny fully specified change.
Plan a complete resource or operational workflow for a data-heavy web app before implementation. Use when a new or materially expanded admin, CRUD, directory, queue, or management feature still needs product-scope decisions and the requested deliverable is a plan, not implementation in this turn. Do not invoke when the user explicitly asks to build or implement the workflow, or when the request is for marketing, e-commerce, editorial, styling-only work, a narrow bug fix, an audit of existing behavior, or a small change whose behavior is already fully specified.
Compare two or more analogous operational web-app modules to find structural capability drift, identify an evidence-based golden path, and define a coherent target contract and migration sequence. Use when the user explicitly invokes $consistency-critique; explicit invocation is required. Do not invoke when the request is for marketing, e-commerce, editorial, a single-feature audit, implementation, visual taste critique, generic code review, or refactoring without product-behavior comparison.