← all publishers

mskayyali

@mskayyali source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 11 hours ago last updated

1. ▌
   State List · mskayyali

   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, and an optional v0.1 JSON mirror. For existing products, prefer state-audit. Do not treat the four lenses as equivalent state-machine node types or claim exhaustive completeness.
   0
   installs
2. ▌
   State Audit · mskayyali

   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 with file-line evidence and risk-aware prioritisation. Do not call code-only inference independent evidence or turn the output into a bug list.
   0
   installs
3. ▌
   State Graph · mskayyali

   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 relationships, call the result an executable statechart, or render an unreadable 50-node graph without a cut.
   0
   installs
4. ▌
   Reentry Pass · mskayyali

   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 high-risk composite scenarios. Use on lifecycle states, failures, interruptions, and surfaces; do not mark a condition specified from its name alone.
   0
   installs
5. ▌
   State Prompt · mskayyali

   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 existing map. Do not paste the whole map into a generator or use for non-stateful brand and marketing imagery.
   0
   installs
6. ▌
   State Triage · mskayyali

   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 continue to specification until a human confirms them.
   0
   installs
7. ▌
   System Sentence · mskayyali

   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 when an existing-feature audit lacks a clear structural anchor. Do not use for static marketing pages or as generic prompt optimisation.
   0
   installs