aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging,…
@managedcodeInstall SkillDevelopment
Skill
/workflow-foundation
Maintain or assess Workflow Foundation-based solutions on .NET Framework, especially where long-lived process logic or legacy designer artifacts still matter. USE FOR: WF activities and workflows; designer-backed process logic; long-lived workflow state and persistence; keep,
Claude Code
$ npx -y skills add managedcode/dotnet-skills --skill workflow-foundation --agent claude-code
Codex
$ npx skills add managedcode/dotnet-skills --skill workflow-foundation -a codex -y
Cursor
$ npx skills add managedcode/dotnet-skills --skill workflow-foundation -a cursor -y
Gemini CLI
$ npx skills add managedcode/dotnet-skills --skill workflow-foundation -a gemini-cli -y
GitHub Copilot
$ npx skills add managedcode/dotnet-skills --skill workflow-foundation -a github-copilot -y
OpenCode
$ npx skills add managedcode/dotnet-skills --skill workflow-foundation -a opencode -y
Windsurf
$ npx skills add managedcode/dotnet-skills --skill workflow-foundation -a windsurf -y
SKILL.md
workflow-foundation.SKILL.mdname: workflow-foundation
description: "Maintain or assess Workflow Foundation-based solutions on .NET Framework, especially where long-lived process logic or legacy designer artifacts still matter. USE FOR: WF activities and workflows; designer-backed process logic; long-lived workflow state and persistence; keep, isolate, or replace decisions. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."
compatibility: "Requires WF or a migration plan away from 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
1. Treat WF as legacy infrastructure and start by understanding what workflow behavior is still business-critical before proposing replacement. 2. Separate workflow host concerns, activity logic, persistence, and integration points so risk is visible. 3. Avoid half-migrations that leave workflow state and business rules split across two orchestration systems without ownership. 4. If replacement is needed, define explicit equivalence for triggers, compensation, persistence, and audit expectations. 5. Stabilize current behavior with targeted tests or scenario captures before changing designer-driven artifacts. 6. 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](references/migration.md) - decision framework for keeping, replacing, or isolating WF; migration targets and steps; common pitfalls
- [Maintenance Patterns](references/patterns.md) - host management, persistence, activity design, testing, and operational patterns for WF systems
Read more
name: workflow-foundation description: "Maintain or assess Workflow Foundation-based solutions on .NET Framework, especially where long-lived process logic or legacy designer artifacts still matter. USE FOR: WF activities and workflows; designer-backed process logic; long-lived workflow state and persistence; keep, isolate, or replace decisions. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made." compatibility: "Requires WF or a migration plan away from 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
1. Treat WF as legacy infrastructure and start by understanding what workflow behavior is still business-critical before proposing replacement. 2. Separate workflow host concerns, activity logic, persistence, and integration points so risk is visible. 3. Avoid half-migrations that leave workflow state and business rules split across two orchestration systems without ownership. 4. If replacement is needed, define explicit equivalence for triggers, compensation, persistence, and audit expectations. 5. Stabilize current behavior with targeted tests or scenario captures before changing designer-driven artifacts. 6. 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](references/migration.md) - decision framework for keeping, replacing, or isolating WF; migration targets and steps; common pitfalls
- [Maintenance Patterns](references/patterns.md) - host management, persistence, activity design, testing, and operational patterns for WF systems
Stats
515
Stars
41
Forks
Active
Maintenance
C#
Language
MIT
License
Last commit
Created
Ships withdotnet-skills
Stop explaining .NET to your AI. Start building. We've all been there: asking Claude to use Entity Framework, only to get EF6 patterns in a .NET 8 project. Explaining to Copilot that Blazor Server and Blazor WebAssembly aren't the same thing.
499200 skills17 agents
Stars on GitHub
Momentum
- stars in total
- 499
Other skills on dotnet-skills.
@managedcodeInstall Skillaspire
Build, upgrade, and operate Aspire 13.5.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults,…
@managedcodeInstall Skillavalonia
Build and debug Avalonia 11/12 .NET applications with XAML, compiled bindings, MVVM, custom controls, desktop lifetimes, and…
@managedcodeInstall Skillazure-functions
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable…
@managedcodeInstall Skillblazor
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design,…
@managedcodeInstall Skillentity-framework6
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is…
@managedcodeInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about workflow-foundation.
- Which coding agents can use workflow-foundation?
- workflow-foundation installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.