---
description: Transform rough feature ideas into comprehensive implementation specifications
argument-hint: [feature idea]
---

# FeatureForge - Feature Specification Builder

Transform rough feature ideas into comprehensive, ready-to-implement specifications.

## Input

**Feature Idea:**
```
$ARGUMENTS
```

## Steps

1. **Understand the Feature**
   - Identify core functionality and business value
   - Determine complexity level (Simple/Medium/Complex)
   - Choose appropriate detail level based on complexity

2. **Gather Context** (Ask 3-5 clarifying questions)
   - What problem does this solve for users?
   - Who will use this feature and when?
   - What's the main user flow or interaction?
   - Any technical constraints or integrations needed?
   - How will you measure success?

3. **Build Specification**
   - Use template below based on complexity
   - Focus on clarity and actionable details
   - Include acceptance criteria that are testable

4. **Output for Next Steps**
   - Format as complete specification ready for `/cci` command
   - Wrap in code block for easy copying

## Output Format

### For Simple Features

```markdown
# Feature: [Feature Name]

## Problem
[What user problem does this solve?]

## Solution
[How will this feature work?]

## User Story
As a [user type], I want to [action] so that [benefit].

## Acceptance Criteria
- [ ] [Testable criterion 1]
- [ ] [Testable criterion 2]
- [ ] [Testable criterion 3]

## Technical Notes
- [Key implementation detail]
- [Dependencies or constraints]

**Priority**: Medium | **Effort**: Small
```

### For Medium/Complex Features

```markdown
# Feature: [Feature Name]

## Problem Statement
[Detailed description of the problem and user impact]

## Proposed Solution
[Comprehensive description of how the feature works]

## User Stories
1. As a [user type], I want to [action] so that [benefit]
2. As a [user type], I want to [action] so that [benefit]

## Functional Requirements
- [Requirement 1 with details]
- [Requirement 2 with details]
- [Requirement 3 with details]

## Acceptance Criteria
- [ ] [Detailed testable criterion 1]
- [ ] [Detailed testable criterion 2]
- [ ] [Detailed testable criterion 3]
- [ ] [Detailed testable criterion 4]

## Technical Specifications

### Data Model
[What data needs to be stored/processed?]

### API/Integration Points
[New endpoints or external integrations needed]

### UI/UX Considerations
[Key user interface elements and flows]

## Edge Cases & Error Handling
- **[Edge case 1]**: [How to handle]
- **[Error scenario]**: [Expected behavior]

## Success Metrics
- [Metric 1]: [Target value]
- [Metric 2]: [Target value]

## Dependencies
- [External system or prerequisite feature]

**Priority**: High | **Effort**: Large | **Timeline**: 4-6 weeks
```

## Example Commands

**Simple:**
```
/featureforge Add a dark mode toggle in settings
```

**Complex:**
```
/featureforge Build a customer referral system with reward tracking, email notifications, and analytics dashboard
```

## Usage Flow

1. Run `/featureforge [your feature idea]`
2. Answer clarifying questions
3. Receive formatted specification
4. Copy the output
5. Use with `/cci` to create GitHub issue: `/cci [paste specification here]`

## Notes

- **Keep it actionable** - Focus on what to build, not how to build it
- **Be specific** - Vague requirements lead to unclear implementations
- **Think user-first** - Start with the problem, not the solution
- **Include metrics** - Define what success looks like
- For coding standards and patterns, refer to CLAUDE.md