Elsa Create Feature

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 catalog updates.

elsa-workflows Updated 7.9k repo stars
Elsa 4, a modern .NET workflow engine, illustrated with branching activity paths, a modular runtime and layered checkpoints

File contents

User Input

$ARGUMENTS

Outline

  1. Read docs/skills/catalog.md#create-feature-or-module.
  2. Read the relevant framework gates for three-layer separation, naming, feature identity, provider decomposition, and unit tests.
  3. Identify owning domain, dependency envelope, .Core/helper/implementation shape, and whether Speckit planning is required first.
  4. Plan feature registration tests, implementation tests, docs, and EXTENSION_POINTS.md updates before coding.
  5. Preserve official Speckit flow for feature/work-unit development unless the user explicitly chooses a different path.

If the user has not explicitly approved implementation, stop with a plan and exact file list. After the user approves the feature/module plan, complete required tests, extension-point catalog updates, generated-map refreshes, and small docs follow-through as part of the approved work.

elsa-workflows/elsa-foundation commit 368b2d4649

Frequently asked questions

npx get-skill add elsa-workflows/elsa-create-feature