A way of designing software where the conditions it can be in are treated as the work, not as edge cases to handle later.
Skill Claude CodeCodex
Part of stateful
Specify every in-scope Stateful condition and run the five-question re-entry review on each non-transient lifecycle state. Use after human-confirmed triage to add behavior, owner, acceptance criteria, category-specific recovery or surface requirements, explicit applicable/not-applicable re-entry verdicts, and…
Skill Claude CodeCodex
Part of stateful
Audit an existing software feature or surface by deriving an expected, evidence-sourced condition inventory and comparing it with code, tests, designs, telemetry, incidents, support history, requirements, and domain rules. Use to find undesigned or unimplemented lifecycle states, failures, interruptions, and surfaces…
Skill Claude CodeCodex
Part of stateful
Render an existing Stateful v0.1 condition map as Mermaid, grouping lifecycle states, failures, interruptions, and surfaces while drawing only recorded typed relationships and styling confirmed scope. Use for visual overviews in STATEFUL.md, READMEs, reviews, or stakeholder discussions. Do not invent conditions or…
Skill Claude CodeCodex
Part of stateful
Build a Stateful condition inventory for a confirmed system sentence across four related lenses: lifecycle states, failures, interruptions, and surfaces. Use after system-sentence on greenfield or feature-level work when the user needs systematic discovery with evidence, explicit coverage checks, typed relationships…
Skill Claude CodeCodex
Part of stateful
Rewrite a generic product-design prompt into a paste-ready prompt for one specific Stateful condition or one explicit high-risk composition of lifecycle state, interruption context, surface, and changed-data or dependency condition. Use when generating a screen, component, email, notification, or prototype from an…
Skill Claude CodeCodex
Part of stateful
Recommend evidence-aware risk and scope decisions for a complete Stateful condition inventory, recording likelihood, impact, confidence, rationale, and one of in, out-with-implication, or out for human confirmation. Use after state-list or state-audit and before specification. Do not persist recommendations or…
Skill Claude CodeCodex
Part of stateful
Produce and confirm a structural system sentence describing what a software feature or surface is as an object that exists over time, with enough temporal and lifecycle structure to generate 3–5 materially distinct conditions. Use at the start of Stateful work, when a description is feature-framed or flow-framed, or…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: