Loading the repository README…
Showing 40 of 40 collected skills.
Run one pass of the weekly product scout: mine feature requests, discussions and workarounds in elsa-core, elsa-studio and elsa-foundation, the UX QA ledger, deferred specs and Elsa 3 parity gaps, check what already exists, then file at most two…
Run one pass of the recurring UX QA routine: build and start the Workbench and Studio from main, walk the golden path, explore one rotating area through one user lens in a real browser, have each finding refuted by a fresh agent, then file at most three…
Execute the implementation planning workflow using the plan template to generate design artifacts.
Review a branch or pull request to convergence with independent reviewers and adversarial verification, then merge only on a fully green gate with evidence posted as a PR comment. Use when a branch or PR is ready for review, when review fixes need…
Create or update an Elsa local agent preference. Use when a user states a stable personal workflow preference, asks agents to remember how they want sessions handled, or wants a preference recorded like the Git operating model without turning it into shared…
Bootstrap Elsa local agent preferences. Use when .agent-prefs has no preference files other than .gitkeep, or when a user asks to set up repository-local agent preferences for Git workflow, session execution model, or other personal workflow choices.
Review whether Elsa-brain work is drifting from the shared program-goal planner or current program-goal state. Use when a user asks whether work is drifting, a thread reaches a third consecutive related work unit, recent work keeps deepening one local area,…
Refresh or plan refreshes for generated Elsa maps. Use when map inputs changed, map freshness is uncertain, extension-point catalogs changed, project/package references changed, specs changed, or another skill needs current navigation facts.
Find and rank the next Elsa-brain work unit from unfinished work, reports, specs, and source markers. Use when a user asks what is next, what is unfinished, what is unratified, what is weakly implemented, or which unit should be planned next in…
Turn Elsa-brain findings into an architecture-first or Speckit-ready work-unit plan. Use when a report finding, deferred decision, weak implementation, docs/maps/skills gap, or user-selected next unit needs scope, success criteria, source-of-truth layer, and…
Execute the implementation planning workflow using the plan template to generate design artifacts.
Run one pass of the recurring quality fixer: check for a reverted auto-merge, service open auto-fix PRs, then claim one ready issue, fix it on a claude/auto-fix branch, open a ready PR with evidence, and auto-merge only small simplify/docs/tests changes…
Run one pass of the recurring quality reviewer: one rotating lens and area, at most three needs-triage + auto-review issues with kind and size labels, duplicate check first, and no filing while 15 or more await triage. Use when the reviewer routine fires or a…
Plan and add Elsa unit tests required by the constitution. Use when a feature class, service registration, logic-bearing implementation, failure path, infrastructure exception wrapper, or branch behavior is created or changed; also use implicitly after…
Plan or implement a new Elsa feature/module shape using the modular framework rules. Use when adding, porting, splitting, or scaffolding a feature/module, including package placement, dependency envelope, feature registration, tests, docs, and extension-point…
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
Execute the implementation plan by processing and executing all tasks defined in tasks.md
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
Execute the implementation plan by processing and executing all tasks defined in tasks.md
Execute the implementation planning workflow using the plan template to generate design artifacts.
Give a concise architecture tour of elsa-foundation-studio (the ASP.NET Core/CShells host and React/Vite Elsa Studio). Use when a user asks what the repository is, how to orient, where to start, or how the shell, modules, routing, API, and authentication fit…
Plan or scaffold a new Elsa Studio (designer) module: manifest, registry + route-manifest registration, routes, i18n, and the Settings toggle. Use when adding, porting, or scaffolding a studio module/feature in elsa-foundation-designer.
Extend an existing Elsa Studio (designer) module: add a sub-page, relabel, change icon/colour, add an owned route, wire new data, or change required/default. Use when modifying a module already registered in elsa-foundation-designer.
Locate the right extension point in elsa-foundation-designer: where to plug in nav, routes, the module gate, API/data hooks, i18n, or shared UI. Use when a user asks 'where do I add/change X?' in the studio.
Define an elsa-foundation-designer project term (module, manifest, registry, route manifest, owned path, tint, engine, resource hook, …). Use when a user asks what a studio-specific term means.
Port a feature from the original Blazor Elsa Studio (elsa-workflows/elsa-studio) into a module in elsa-foundation-designer. Use when migrating, porting, or rebuilding an existing Elsa Studio feature here — behaviour parity, not MudBlazor markup.
Verify a change to elsa-foundation-designer is sound: typecheck, lint, build (which catches module registry/route-manifest drift), and a runtime sanity check for module work. Use before handing off or pushing studio changes.
Critically review Elsa or framework constitution sections for enforceable gates, ambiguity, contradictions, missing exceptions, ratification readiness, and source-of-truth drift. Use when a user asks to question, revise, finalize, ratify, or challenge…
Plan or implement Elsa event contributions and independent event subscribers using the AI-provider-neutral event/contribution workflow. Use when adding fan-in contributors, Source/Contributor/PreProcessor/PostProcessor implementations, action-named…
Plan or implement an Elsa bridge or adapter between seams, phase-owned contracts, or external/heavy dependencies. Use when code must connect two domains without making either own the other, isolate an external dependency, or translate design/runtime contracts.
Plan an Elsa replacement-contract implementation before coding. Use when exactly one implementation should be active per app/runtime context, when adding or replacing a single-implementation service, or when checking conflict detection for replacement…
Give a concise Elsa foundation architecture tour. Use when a user asks what the repo is, how to orient in elsa-foundation, where to start, or how core architecture systems fit together without reading the full constitutions.
Plan or generate CShells/Nuplane appsettings JSON from selected Elsa features. Use after feature composition inputs are known, or when evaluating blockers around feature identifiers, appsettings schema, dependencies, and optional features.
Plan an Elsa feature-inheritance extension before implementation. Use when one feature must extend, decorate, specialize, or override another feature's registration pipeline, including inherited feature classes, virtual ConfigureServices behavior, service…
Plan and apply Elsa extension-point catalog updates. Use when a project exposes, implements, or changes events, contributor interfaces, replacement contracts, feature inheritance points, bridges, handlers, or other extension surfaces; also use implicitly…
Explore Elsa feature composition for an API, shell, or runnable feature set. Use when selecting features, dependencies, provider modules, or compatibility inputs before generating CShells/Nuplane appsettings.
Build or analyze Elsa feature, project, package, external NuGet, or dependency maps. Use when a user asks about feature dependencies, project references, external package versions, compatibility signals, dependency envelopes, or generated map/report updates.
Look up Elsa or modular-framework terminology from the canonical glossary. Use when a term's meaning is needed before continuing, when avoiding duplicated concept explanations, or when deciding whether content belongs in glossary, reference docs,…
Audit Elsa-brain source-of-truth placement. Use when docs, constitution text, glossary terms, reports, maps, skills, specs, or code may duplicate responsibilities; when thinning constitution material; or when deciding where new knowledge/workflow/rules should…
Verify the Elsa codebase against selected constitution gates by inspecting references, extension-point catalogs, packages, tests, docs, stubs, and generated maps. Use when a user asks whether code complies with the constitution or wants a verification report.
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/elsa-workflows/elsa-foundation.The repository README could not be loaded. You can still explore its Skills below.