Dotnet workflow foundation

Skill Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-workflow-foundation

Maintain or assess Workflow Foundation-based solutions on .NET Framework, especially where long-lived process logic or legacy designer artifacts still matter.From its SKILL.md

Install

npx -y skills add Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-workflow-foundation

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

One thing to look at

8 stars8 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.

SKILL.md

2.0 KB, 301 tokens by cl100k_base, as published. Nobody here has run it

Windows Workflow Foundation

Trigger On

working on WF activities, workflows, or designer-backed process logic
reviewing long-lived workflow state and persistence behavior
assessing whether to keep, isolate, or replace Workflow Foundation

Workflow

Treat WF as legacy infrastructure and start by understanding what workflow behavior is still business-critical before proposing replacement.
Separate workflow host concerns, activity logic, persistence, and integration points so risk is visible.
Avoid half-migrations that leave workflow state and business rules split across two orchestration systems without ownership.
If replacement is needed, define explicit equivalence for triggers, compensation, persistence, and audit expectations.
Stabilize current behavior with targeted tests or scenario captures before changing designer-driven artifacts.
Validate with representative long-running and failure scenarios, not just a single successful execution path.

Deliver

practical maintenance or migration guidance for WF
clear boundaries around host, workflow, and persistence responsibilities
risk-aware change plans for legacy process logic

Validate

business-critical workflow behavior is identified before change
migration work preserves state and audit expectations
designer artifacts are treated carefully

References

Migration Guidance - decision framework for keeping, replacing, or isolating WF; migration targets and steps; common pitfalls
Maintenance Patterns - host management, persistence, activity design, testing, and operational patterns for WF systems

What ships with it: 2 files

11.8 KB alongside SKILL.md

references/

migration.md4.4 KB
patterns.md7.5 KB

Gives 0 of the 12 instructions most automation workflows skills give in 301 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

Write conventional commit messagesin 36 of 745, across 35 files
Delete branches after mergein 30 of 745, across 21 files
Make atomic commitsin 25 of 745, across 15 files
Write minimal code to pass testsin 22 of 745, across 10 files
Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
Use try-catch for error handlingin 20 of 745, across 8 files
Run tests before committingin 20 of 745, across 12 files
Write tests before implementationin 20 of 745, across 8 files
Configure branch protection rulesin 19 of 745, across 5 files
Explain the why in commit messagesin 19 of 745, across 9 files
Refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

understand critical workflow behavior before replacing
separate workflow host, logic, persistence, and integration concerns
define explicit equivalence for triggers, compensation, persistence, and audit
stabilize current behavior with tests before changing designer artifacts
validate with representative long-running and failure scenarios

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.