Elsa Roadmap Refresh
Purpose
Use this skill to refresh Elsa's roadmap from evidence across the Elsa product surface:
elsa-workflows/elsa-coreelsa-workflows/elsa-studioelsa-workflows/elsa-extensions
The output should be a coherent product roadmap, not a raw issue digest. Ground every substantial change in source code, specs, releases, issues, pull requests, or discussions.
Safety Rules
- Before editing, run
git status --short in elsa-core.
- Never revert unrelated user changes.
- If
ROADMAP.md or README.md already has uncommitted user edits, stop and report the conflict unless the user explicitly asked to work through it.
- Edit only roadmap-related files unless the user asks for more.
- Do not commit, push, or publish unless the user or automation prompt explicitly asks for it.
- If updating GitHub issue
elsa-core#3232, use the final ROADMAP.md body as the issue body.
Evidence Workflow
Read the current roadmap.
ROADMAP.mdREADME.md roadmap link, if relevant- GitHub issue
elsa-workflows/elsa-core#3232
Inspect elsa-core.
- Source modules under
src/modules
- App hosts under
src/apps
- Specs under
specs
- Docs under
doc and design
- Recent releases, commits, open issues, discussions, and open PRs
Inspect elsa-studio.
- Source layout and feature modules
- Designer, diagnostics, auth, localization, embedding, workflow authoring, and instance UX
- Recent releases, commits, open issues, discussions, and open PRs
Inspect elsa-extensions.
- Module families and integration foundations
- Connections, Secrets, Agents, OpenAPI, schedulers, messaging, persistence, data tooling, and package manifests
- Recent releases, commits, open issues, and open PRs
- Discussions if enabled; otherwise state that issue/PR signal is the available source
Use gh for GitHub data when available. Prefer local clones when present; otherwise use temporary clones or gh repo clone into /tmp.
Classification Rules
Use these categories consistently:
[x] shipped foundation: implemented in source or released enough to build on.[~] partially shipped or needs productization: code exists, but docs, Studio UX, integration, tests, release packaging, or operational readiness are incomplete.[ ] roadmap candidate: valuable capability not yet implemented or only represented by issue/PR/proposal.- stale/obsolete: roadmap item is already done, superseded, or no longer matches repository direction.
Be explicit when a conclusion is an inference from evidence rather than a direct source fact.
Roadmap Editing Rules
- Keep
ROADMAP.md product-oriented and exciting, but technically defensible.
- Preserve the main structure unless a better structure is clearly needed:
- North Star
- Capability Checklist
- Current Foundations
- Production Confidence
- Authoring Productivity
- Integrations And Ecosystem
- Observability And Operations
- Security, Identity, And Enterprise Readiness
- AI-Assisted Workflow Engineering
- Recommended Sequencing
- Maintainership Recommendations
- Update
Last refreshed to the current date.
- Keep issue and PR links close to the claims they support.
- Prefer platform tracks over long lists of unrelated features.
- Separate what is already present from what still needs productization.
- Do not overpromise release dates.
High-Value Themes To Re-Evaluate Each Refresh
- Runtime recovery, graceful shutdown, distributed execution, scheduler/message reliability
- Studio designer reliability, state machine authoring, debugging, progress/timeline, embedded components
- Studio diagnostics, structured logs, console logs, OpenTelemetry, workflow incident timelines
- Extension Platform, package manifests, Connections, Secrets, generated activities, connector SDK
- Agents, MCP/tooling, provider matrix, AI-assisted authoring
- OpenAPI activity provider, Azure Functions, Azure DevOps, Microsoft 365 and Google Workspace integrations
- Security, OIDC, tenant/role activity visibility, localization, white-label readiness
- Marketplace/plugin installation path and package maturity states
Recommended GitHub Commands
gh issue view 3232 --repo elsa-workflows/elsa-core --json title,body,updatedAt,url
gh issue list --repo elsa-workflows/elsa-core --state open --limit 200 --json number,title,labels,updatedAt,url
gh issue list --repo elsa-workflows/elsa-studio --state open --limit 200 --json number,title,labels,updatedAt,url
gh issue list --repo elsa-workflows/elsa-extensions --state open --limit 200 --json number,title,labels,updatedAt,url
gh pr list --repo elsa-workflows/elsa-core --state open --limit 100 --json number,title,updatedAt,url
gh pr list --repo elsa-workflows/elsa-studio --state open --limit 100 --json number,title,updatedAt,url
gh pr list --repo elsa-workflows/elsa-extensions --state open --limit 100 --json number,title,updatedAt,url
gh release list --repo elsa-workflows/elsa-core --limit 10
gh release list --repo elsa-workflows/elsa-studio --limit 10
gh release list --repo elsa-workflows/elsa-extensions --limit 10
Publishing
When asked to mirror the roadmap to GitHub:
gh issue edit 3232 --repo elsa-workflows/elsa-core --body-file ROADMAP.md
After publishing, verify:
gh issue view 3232 --repo elsa-workflows/elsa-core --json title,url,updatedAt
Final response should summarize changed themes, whether the GitHub issue was updated, and any files left modified.
1---2name: elsa-roadmap-refresh3description: Refresh 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.4---56# Elsa Roadmap Refresh78## Purpose910Use this skill to refresh Elsa's roadmap from evidence across the Elsa product surface:1112- `elsa-workflows/elsa-core`13- `elsa-workflows/elsa-studio`14- `elsa-workflows/elsa-extensions`1516The output should be a coherent product roadmap, not a raw issue digest. Ground every substantial change in source code, specs, releases, issues, pull requests, or discussions.1718## Safety Rules1920- Before editing, run `git status --short` in `elsa-core`.21- Never revert unrelated user changes.22- If `ROADMAP.md` or `README.md` already has uncommitted user edits, stop and report the conflict unless the user explicitly asked to work through it.23- Edit only roadmap-related files unless the user asks for more.24- Do not commit, push, or publish unless the user or automation prompt explicitly asks for it.25- If updating GitHub issue `elsa-core#3232`, use the final `ROADMAP.md` body as the issue body.2627## Evidence Workflow28291. Read the current roadmap.30 - `ROADMAP.md`31 - `README.md` roadmap link, if relevant32 - GitHub issue `elsa-workflows/elsa-core#3232`33342. Inspect `elsa-core`.35 - Source modules under `src/modules`36 - App hosts under `src/apps`37 - Specs under `specs`38 - Docs under `doc` and `design`39 - Recent releases, commits, open issues, discussions, and open PRs40413. Inspect `elsa-studio`.42 - Source layout and feature modules43 - Designer, diagnostics, auth, localization, embedding, workflow authoring, and instance UX44 - Recent releases, commits, open issues, discussions, and open PRs45464. Inspect `elsa-extensions`.47 - Module families and integration foundations48 - Connections, Secrets, Agents, OpenAPI, schedulers, messaging, persistence, data tooling, and package manifests49 - Recent releases, commits, open issues, and open PRs50 - Discussions if enabled; otherwise state that issue/PR signal is the available source5152Use `gh` for GitHub data when available. Prefer local clones when present; otherwise use temporary clones or `gh repo clone` into `/tmp`.5354## Classification Rules5556Use these categories consistently:5758- `[x]` shipped foundation: implemented in source or released enough to build on.59- `[~]` partially shipped or needs productization: code exists, but docs, Studio UX, integration, tests, release packaging, or operational readiness are incomplete.60- `[ ]` roadmap candidate: valuable capability not yet implemented or only represented by issue/PR/proposal.61- stale/obsolete: roadmap item is already done, superseded, or no longer matches repository direction.6263Be explicit when a conclusion is an inference from evidence rather than a direct source fact.6465## Roadmap Editing Rules6667- Keep `ROADMAP.md` product-oriented and exciting, but technically defensible.68- Preserve the main structure unless a better structure is clearly needed:69 - North Star70 - Capability Checklist71 - Current Foundations72 - Production Confidence73 - Authoring Productivity74 - Integrations And Ecosystem75 - Observability And Operations76 - Security, Identity, And Enterprise Readiness77 - AI-Assisted Workflow Engineering78 - Recommended Sequencing79 - Maintainership Recommendations80- Update `Last refreshed` to the current date.81- Keep issue and PR links close to the claims they support.82- Prefer platform tracks over long lists of unrelated features.83- Separate what is already present from what still needs productization.84- Do not overpromise release dates.8586## High-Value Themes To Re-Evaluate Each Refresh8788- Runtime recovery, graceful shutdown, distributed execution, scheduler/message reliability89- Studio designer reliability, state machine authoring, debugging, progress/timeline, embedded components90- Studio diagnostics, structured logs, console logs, OpenTelemetry, workflow incident timelines91- Extension Platform, package manifests, Connections, Secrets, generated activities, connector SDK92- Agents, MCP/tooling, provider matrix, AI-assisted authoring93- OpenAPI activity provider, Azure Functions, Azure DevOps, Microsoft 365 and Google Workspace integrations94- Security, OIDC, tenant/role activity visibility, localization, white-label readiness95- Marketplace/plugin installation path and package maturity states9697## Recommended GitHub Commands9899```bash100gh issue view 3232 --repo elsa-workflows/elsa-core --json title,body,updatedAt,url101gh issue list --repo elsa-workflows/elsa-core --state open --limit 200 --json number,title,labels,updatedAt,url102gh issue list --repo elsa-workflows/elsa-studio --state open --limit 200 --json number,title,labels,updatedAt,url103gh issue list --repo elsa-workflows/elsa-extensions --state open --limit 200 --json number,title,labels,updatedAt,url104gh pr list --repo elsa-workflows/elsa-core --state open --limit 100 --json number,title,updatedAt,url105gh pr list --repo elsa-workflows/elsa-studio --state open --limit 100 --json number,title,updatedAt,url106gh pr list --repo elsa-workflows/elsa-extensions --state open --limit 100 --json number,title,updatedAt,url107gh release list --repo elsa-workflows/elsa-core --limit 10108gh release list --repo elsa-workflows/elsa-studio --limit 10109gh release list --repo elsa-workflows/elsa-extensions --limit 10110```111112## Publishing113114When asked to mirror the roadmap to GitHub:115116```bash117gh issue edit 3232 --repo elsa-workflows/elsa-core --body-file ROADMAP.md118```119120After publishing, verify:121122```bash123gh issue view 3232 --repo elsa-workflows/elsa-core --json title,url,updatedAt124```125126Final response should summarize changed themes, whether the GitHub issue was updated, and any files left modified.
elsa-workflows