Elsa Workflows
Official@elsa-workflows
A set of workflow libraries, engines & designers
Agent Skills by Elsa Workflows
Showing 31 vetted skills indexed across 1 GitHub repositories.
elsa-workflowselsa-release-announcements
Draft and publish Elsa release announcements for Discord, LinkedIn, and X.
elsa-workflowselsa-release
Create GitHub releases from Git tags with curated release notes for Elsa repositories.
elsa-workflowselsa-roadmap-refresh
Updates the Elsa product roadmap from source code and GitHub evidence.
elsa-workflowsspeckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
elsa-workflowsspeckit-git-validate
Validates that the current Git branch follows spec-kit feature branch naming conventions.
elsa-workflowsspeckit-git-initialize
Initializes a Git repository with an initial commit in spec-kit projects.
elsa-workflowsspeckit-constitution
Create or update the project constitution and sync dependent spec-kit templates.
elsa-workflowsspeckit-implement
Executes implementation tasks defined in tasks.md following the spec-kit project workflow.
elsa-workflowsspeckit-taskstoissues
Convert spec-kit tasks into dependency-ordered GitHub issues via the GitHub MCP server.
elsa-workflowsspeckit-clarify
Detects underspecified areas in feature specs and records targeted clarification answers.
elsa-workflowsspeckit-plan
Generates implementation plans and design artifacts from feature specifications using spec-kit templates.
elsa-workflowsspeckit-git-feature
Creates a numbered git feature branch for a spec-kit specification.
elsa-workflowsspeckit-analyze
Analyzes spec.md, plan.md, and tasks.md for cross-artifact consistency and coverage gaps.
elsa-workflowsspeckit-git-commit
Automatically stages and commits changes after Spec Kit commands complete.
elsa-workflowsspeckit-specify
Generates a feature specification from a natural language description using the spec-kit workflow.
elsa-workflowsspeckit-tasks
Generates dependency-ordered tasks.md checklists from spec-kit design artifacts.
elsa-workflowsspeckit-checklist
Generate requirements validation checklists for clarity, completeness, and consistency.
elsa-workflowsspeckit-git-remote
Detect the Git remote URL in a repository.
elsa-workflowsspeckit-git-validate
Validate Git branch naming conventions and verify associated spec directories.
elsa-workflowsspeckit-git-initialize
Initialize Git repositories and create first commits via Bash or PowerShell.
elsa-workflowsspeckit-constitution
Automates project constitution updates from user input and repository context.
elsa-workflowsspeckit-implement
Executes implementation plans by processing tasks.md dependencies and configuration files.
elsa-workflowsspeckit-taskstoissues
Convert project tasks into dependency-ordered GitHub issues.
elsa-workflowsspeckit-clarify
Analyze feature specifications to identify ambiguities and generate clarification questions.
Frequently Asked Questions About Elsa Workflows
FAQPage SchemaWhat specific project management tasks are enabled by these capabilities?▼
These capabilities enable the conversion of natural language specifications into structured task lists, the generation of requirements validation checklists, and the transformation of project tasks into dependency-ordered GitHub issues. It ensures project consistency by analyzing documentation for ambiguities and gaps before implementation begins.
Which personas benefit most from integrating these technical processes?▼
Software engineers, technical leads, and project managers benefit from these capabilities. They are designed for teams requiring strict adherence to Git branch naming conventions, standardized repository initialization, and rigorous validation of implementation plans against project specifications and configuration files.
What are the primary prerequisites for deploying these repository management functions?▼
Deployment requires a Git-based version control environment and access to project documentation in structured formats. Users must maintain YAML configuration files for commit staging and ensure that project dependencies are clearly defined within tasks.md files to enable proper issue ordering.