elsa-workflows

Draft and publish verified Elsa release announcements on Discord, LinkedIn, and X, including safe recovery and publication receipts. Use after Elsa releases or when explicitly asked to announce a release.

Refresh the Elsa roadmap from current evidence. Use when Codex needs to update ROADMAP.md or the public roadmap issue by researching elsa-core (which now contains the Studio and Extensions source) source code, specs, releases, commits, issues, pull requests,…

Release Elsa Core, Studio, Extensions, Templates, and configured Apps container images in dependency order, including validation, package/image verification, post-release website/documentation refresh, recovery, and community announcements. Use for requests…

Initialize a Git repository with an initial commit

Validate current branch follows feature branch naming conventions

Create or update the feature specification from a natural language feature description.

Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review, and…

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

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…

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.

Execute the implementation planning workflow using the plan template to generate design artifacts.

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…

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,…

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…

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…

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.

Execute the implementation planning workflow using the plan template to generate design artifacts.

Create or update the feature specification from a natural language feature description.

Draft, queue, schedule, or publish social media posts and community updates for Elsa blog posts, links, launches, and announcements. Use when asked to share something via Buffer, Discord, or social/community channels; create platform-specific social copy;…

Give a concise architecture tour of elsa-foundation-designer (the Next.js Elsa Studio). Use when a user asks what the repo is, how to orient, where to start, or how the shell, modules, routing, API and auth fit together.