User Input
$ARGUMENTS
Outline
- Read
docs/skills/catalog.md#create-feature-or-module. - Read the relevant framework gates for three-layer separation, naming, feature identity, provider decomposition, and unit tests.
- Identify owning domain, dependency envelope,
.Core/helper/implementation shape, and whether Speckit planning is required first. - Plan feature registration tests, implementation tests, docs, and
EXTENSION_POINTS.mdupdates before coding. - 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.