State triage

Skill mskayyali/Stateful/skills/state-triage

A way of designing software where the conditions it can be in are treated as the work, not as edge cases to handle later.

Install

npx -y skills add mskayyali/Stateful --skill state-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.5 KB, as published. Nobody here has run it

Condition Triage

Make scope decisions cheap to review without transferring ownership to the agent.

Procedure

Read the complete inventory and STATEFUL.md. Require the current iteration’s feature, platforms, commitments, constraints, and available evidence.
For each condition, recommend:
- likelihood: low, medium, or high;
- impact: low, medium, or high;
- confidence: hypothesis, informed, or measured;
- a one-sentence evidence-grounded rationale;
- scope: in, out-with-implication, or out.
Do not equate likelihood with priority. Elevate irreversible, safety, security, privacy, regulatory, or high-blast-radius conditions even when rare.
For out-with-implication, name the concrete constraint on in-scope copy, naming, policy, data, architecture, or testing.
For out, record why it is deferred and what would trigger reconsideration.
Check dependencies and relationships. An in-scope condition cannot rely on an incompatible out-of-scope precondition without an explicit implication.
Summarise high-impact hypotheses separately; they require evidence collection, not confident-looking prose.
Present the full recommendation and stop. Ask the human to confirm or adjust.
Only after confirmation:
- persist scope and priority;
- set status: triaged unless a condition was already at a later status;
- update STATEFUL.md;
- preserve deferred conditions.

Output

| ID | Condition | Likelihood | Impact | Confidence | Recommended scope | Rationale / implication |
|---|---|---|---|---|---|---|

## Totals
In: <n> · Out-with-implication: <n> · Out: <n>
High-impact hypotheses: <n>

## Consistency flags
- <dependency or scope conflict>

Confirm or adjust? No decisions will be persisted until you do.

Include layers and failure cause when present.

Failure modes

Persisting agent recommendations before confirmation.
Scoping by implementation difficulty rather than relevance.
Treating out as deletion.
Omitting the implication.
Assigning false precision unsupported by evidence.
Allowing high-impact hypotheses to disappear into a total.