features:add

Command /feature-list:add

Add a new feature file to the specified phase.

Instructions

Step 1: Validate Phase

Ensure phase is one of:

• core
• workflow
• lifecycle
• analytics
• integration
• ui

If invalid, show error:

❌ Invalid phase: `{phase}`

Valid phases:
- `core` — Fundamental entities
- `workflow` — Business processes
- `lifecycle` — State transitions
- `analytics` — Reporting
- `integration` — External services
- `ui` — User interface

Step 2: Determine Next Number

Use Glob to find existing features in the phase:

docs/technical-requirements/features/{phase}-*.md

Parse filenames to find the highest number, then increment:

• If core-01-user.md and core-02-product.md exist
• Next number is 03

Step 3: Generate Domain Code

Derive 3-letter domain code from the feature name:

Name	Domain Code
user-management	USR
product-catalog	PRD
order-processing	ORD
payment-gateway	PAY
email-service	EML
notifications	NTF

If unclear, ask user:

questions:
  - question: "What 3-letter domain code should be used for {name}?"
    header: "Domain"
    options:
      - label: "{suggested1}"
        description: "Based on feature name"
      - label: "{suggested2}"
        description: "Alternative"

Step 4: Gather Feature Details

Use AskUserQuestion:

questions:
  - question: "What is the priority of this feature?"
    header: "Priority"
    options:
      - label: "Critical"
        description: "Must have for MVP"
      - label: "High"
        description: "Important, implement early"
      - label: "Medium"
        description: "Standard priority"
      - label: "Low"
        description: "Nice to have"

Step 5: Check Directory Exists

Use Glob to verify docs/technical-requirements/features/ exists.

If not, run init first:

⚠️ Feature directory not found.

Running `/feature-list:init` first...