# 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.

- Skill: `elsa-workflows/elsa-create-feature` (Agent Skill)
- Install (CLI): `npx skillmds@latest add elsa-workflows/elsa-create-feature`
- Raw SKILL.md: https://api.skillmd.com/api/skills/elsa-workflows/elsa-create-feature/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: elsa-workflows (https://skillmd.com/u/elsa-workflows)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/elsa-workflows/elsa-create-feature

---


## User Input

```text
$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.