elsa-workflows
- 45 skills
- 0 followers
- 3 hours ago last updated
- ▌
- ▌ Speckit Taskstoissues · elsa-workflowsConvert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
- ▌ Share Via Social · elsa-workflows bundleDraft, 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; schedule, queue, or publish a post; send to a Discord channel or webhook; or prepare safe share text for LinkedIn, X/Twitter, Mastodon, Bluesky, Facebook, Discord, or similar networks.
- ▌ Designer Verify · elsa-workflowsVerify 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.
- ▌ Designer Create Module · elsa-workflowsPlan 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.
- ▌ Designer Extend Module · elsa-workflowsExtend 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.
- ▌ Designer Glossary Lookup · elsa-workflowsDefine 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.
- ▌ Designer Migrate Feature · elsa-workflowsPort 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.
- ▌ Designer Extension Points · elsa-workflowsLocate 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.
- ▌ Designer Architecture Tour · elsa-workflowsGive 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.
- ▌ Studio Architecture Tour · elsa-workflowsGive 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 together.
- ▌ Speckit Tasks · elsa-workflowsGenerate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
- ▌
- ▌ Greploop · elsa-workflows bundleIteratively 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 repeats. Use when the user wants to fully optimize a PR/MR/CL against Greptile's code review standards.
- ▌ Elsa Release · elsa-workflows bundleRelease Elsa Core, Studio, Extensions, and Templates in dependency order, including validation, package verification, post-release website/documentation refresh, recovery, and community announcements. Use for requests such as "release Elsa 3.9.0 stable", a named preview or RC, or resuming an interrupted Elsa release.
- ▌ Speckit Analyze · elsa-workflowsPerform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
- ▌ Speckit Clarify · elsa-workflowsIdentify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
- ▌ Speckit Specify · elsa-workflowsCreate or update the feature specification from a natural language feature description.
- ▌ Speckit Checklist · elsa-workflowsGenerate a custom checklist for the current feature based on user requirements.
- ▌ Elsa Roadmap Refresh · elsa-workflows bundleRefresh the Elsa roadmap from current evidence. Use when Codex needs to update ROADMAP.md or the public roadmap issue by researching elsa-core, elsa-studio, and elsa-extensions source code, specs, releases, commits, issues, pull requests, and discussions; classify shipped foundations, partial/productization work, roadmap candidates, stale items, and recommendations; then update the roadmap checklist and GitHub issue coherently.
- ▌ Speckit Constitution · elsa-workflowsCreate or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
- ▌ Elsa Release Announcements · elsa-workflows bundleDraft 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.
- ▌ Elsa Create Agent Preference · elsa-workflowsCreate 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 repo doctrine.
- ▌ Elsa Extension Point Catalog · elsa-workflowsPlan 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 after code changes that affect EXTENSION_POINTS.md or generated extension-point maps.
- ▌ Elsa Add Replacement Contract · elsa-workflowsPlan 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 contracts.
- ▌ Elsa Program Goal Drift Review · elsa-workflowsReview 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, or a proposed task would change or split a program-goal bucket.
- ▌ Elsa Extend Feature Inheritance · elsa-workflowsPlan 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 additions/replacements, and registration tests.
- ▌ Elsa Critical Constitution Review · elsa-workflowsCritically 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 constitution/architecture rules.
- ▌ Elsa Initialize Agent Preferences · elsa-workflowsBootstrap 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.
- ▌ Speckit Plan · elsa-workflowsExecute the implementation planning workflow using the plan template to generate design artifacts.
- ▌ Elsa Whats Next · elsa-workflowsFind 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 elsa-foundation.
- ▌ Elsa Add Unit Tests · elsa-workflowsPlan 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 implementation work to check whether feature registration or implementation unit tests are required.
- ▌ Elsa Create Feature · elsa-workflowsPlan 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 catalog updates.
- ▌ Elsa Glossary Lookup · elsa-workflowsLook 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, constitution, reports, maps, skills, specs, or code.
- ▌ Elsa Verify Codebase · elsa-workflowsVerify 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.
- ▌ Elsa Architecture Tour · elsa-workflowsGive 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.
- ▌ Elsa Auto Review Merge · elsa-workflowsReview 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 re-reviewing, or when a user asks to review and merge.
- ▌ Elsa Work Unit Planner · elsa-workflowsTurn 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 exact files before implementation.
- ▌ Elsa Add Bridge Adapter · elsa-workflowsPlan 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.
- ▌ Elsa Cshells Appsettings · elsa-workflowsPlan 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.
- ▌ Elsa Feature Composition · elsa-workflowsExplore 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.
- ▌ Elsa Source Of Truth Audit · elsa-workflowsAudit 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 live.
- ▌ Elsa Add Event Contribution · elsa-workflowsPlan 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 contributors, aggregating handlers, or non-fan-in event subscribers.
- ▌ Elsa Feature Dependency Map · elsa-workflowsBuild 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.
- ▌ Elsa Refresh Generated Maps · elsa-workflowsRefresh 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.