features:init

Command /feature-list:init

Initialize the feature documentation directory structure.

Instructions

Step 1: Determine Target Path

Use the provided path argument or default to docs/technical-requirements/features.

Step 2: Check for Existing Directory

Use Glob to check if the directory already exists:

{path}/*.md

If files exist, inform the user:

⚠️ Feature directory already exists at `{path}`.

Found {count} feature files:
- {file1}
- {file2}
...

Use `/feature-list:analyze` to update from codebase or `/feature-list:add` to add new features.

Step 3: Create Directory Structure

If the directory doesn't exist, create it:

mkdir -p {path}

Step 4: Copy Templates

Read templates from the plugin and write them to the target directory:

1. Read ${CLAUDE_PLUGIN_ROOT}/templates/00-template.md

2. Write to {path}/00-template.md

3. Read ${CLAUDE_PLUGIN_ROOT}/templates/readme-template.md

4. Write to {path}/README.md

Step 5: Confirm Completion

✅ Feature directory initialized at `{path}`

Created files:
- `{path}/README.md` — Feature index with dependency graph
- `{path}/00-template.md` — Template for new features

## Next Steps

1. **Analyze existing codebase**: `/feature-list:analyze`
2. **Design new features**: `/feature-list:design`
3. **Add a feature manually**: `/feature-list:add core user-management`

Response Format

## Feature Directory Initialized

📁 Created `{path}/`

### Files Created

| File | Purpose |
|------|---------|
| `README.md` | Feature index with dependency graph |
| `00-template.md` | Template for new features |

### Next Steps

- Run `/feature-list:analyze` to extract features from existing code
- Run `/feature-list:design` for interactive feature design
- Run `/feature-list:add <phase> <name>` to add a single feature

Edge Cases

Directory Exists but Empty

If the directory exists but has no .md files, proceed with initialization.