1. IF previous task was "Idea Mockup":
   → Extract mockup path from previous task's task_output_links
   → Set Mockup List = extracted path

2. ELSE IF human provides explicit Mockup List:
   → Use human-provided value

3. ELSE IF idea-summary-vN.md exists in related idea folder:
   → Check for "Mockups & Prototypes" section
   → Extract mockup paths
   → Set Mockup List = extracted paths

4. ELSE:
   → Set Mockup List = N/A

Output:
  category: feature-stage
  status: completed | blocked
  next_task_type: task-type-technical-design
  require_human_review: Yes
  auto_proceed: {from input Auto Proceed}
  mockup_list: {updated with copied paths if mockups were copied}
  task_output_links: [x-ipe-docs/requirements/FEATURE-XXX/specification.md]
  feature_id: FEATURE-XXX
  feature_title: {title}
  feature_version: {version}
  feature_phase: Feature Refinement
  
  # Mockup-related attributes (if applicable)
  linked_mockups:
    - mockup_name: "Description of mockup function"
      mockup_path: "x-ipe-docs/requirements/FEATURE-XXX/mockups/mockup-name.html"

CALL feature-stage+feature-board-management skill:
  operation: query_feature
  feature_id: {feature_id from task_data}

RECEIVE Feature Data Model:
  feature_id: FEATURE-XXX
  title: {Feature Title}
  version: v1.0
  status: Planned
  description: {description}
  dependencies: [...]
  created: MM-DD-YYYY
  last_updated: MM-DD-YYYY HH:MM:SS

1. IF x-ipe-docs/requirements/requirement-details.md exists:
   READ requirement-details.md to understand:
     - Overall requirement context
     - Related features
     - Business goals

2. IF feature has dependencies:
   FOR EACH dependency in Feature Data Model:
     CHECK if dependency specification exists
     READ to understand integration points

3. IF feature has architecture implications:
   CHECK x-ipe-docs/architecture/ for relevant designs

IF Mockup List != N/A:
  1. OPEN and analyze the Mockup List file(s)
  2. EXTRACT UI/UX requirements from mockup:
     - Layout structure and component hierarchy
     - User interaction patterns (clicks, hovers, inputs)
     - Visual design elements (colors, spacing, typography)
     - Form fields, validation rules, error states
     - Navigation flows and page transitions
     - Responsive behavior hints
  3. DOCUMENT extracted requirements:
     - Add to "UI/UX Requirements" section in specification
     - Create acceptance criteria for UI elements
     - Note any UI-specific edge cases
  4. IDENTIFY gaps between mockup and requirements:
     - Missing interactions not shown in mockup
     - Backend data requirements for UI elements
     - Loading states, empty states, error states
  5. ASK human about mockup ambiguities if needed

ELSE IF Mockup List == N/A:
  - Check if idea-summary has mockup references
  - If frontend feature, note that mockup may be needed
  - Focus on functional requirements

BEFORE proceeding to Step 3:

1. CHECK if feature folder has mockups:
   - Path: x-ipe-docs/requirements/{FEATURE-ID}/mockups/
   - IF mockups folder exists AND contains files → Skip to Step 3
   
2. IF mockups NOT in feature folder:
   a. Check if feature came from an Idea (look for idea folder reference in requirement-details.md)
   b. IF idea folder exists:
      - Scan: x-ipe-docs/ideas/{idea-folder}/mockups/
      - IF mockups found:
        → Create mockups folder: x-ipe-docs/requirements/{FEATURE-ID}/mockups/
        → Copy ALL mockup files from idea folder to feature folder
        → Update Mockup List attribute with copied file paths
        → Notify: "Found {N} mockups in idea folder, copied to feature folder"
   
3. IF Mockup List is provided (input attribute) AND NOT yet copied:
   a. Create mockups folder if not exists: x-ipe-docs/requirements/{FEATURE-ID}/mockups/
   b. FOR EACH mockup in Mockup List:
      - Copy mockup file from source path
      - Save to: x-ipe-docs/requirements/{FEATURE-ID}/mockups/{filename}
   c. Update Mockup List with new paths
   
4. IF no mockups found after auto-detection:
   - Log: "No mockups found - proceeding without mockups"
   - Proceed to Step 3

# Example: Auto-detected from idea folder
Source: x-ipe-docs/ideas/004. Change Request to Workplace/mockups/
        - dashboard-v1.html
        - settings-panel.html

Target: x-ipe-docs/requirements/FEATURE-008/mockups/
        - dashboard-v1.html
        - settings-panel.html

# Example: From Mockup List input
Source (Mockup List): x-ipe-docs/ideas/Draft Idea - 01232026/mockups/home-page-v1.html
Target: x-ipe-docs/requirements/FEATURE-012/mockups/home-page-v1.html

## Version History

| Version | Date | Description |
|---------|------|-------------|
| v2.0 | 01-22-2026 | Major upgrade: xterm.js, session persistence, split-pane |
| v1.0 | 01-18-2026 | Initial specification |

# Feature Specification: {Feature Title}

> Feature ID: FEATURE-XXX  
> Version: v1.0  
> Status: Refined  
> Last Updated: MM-DD-YYYY

## Linked Mockups

| Mockup | Type | Path | Description |
|--------|------|------|-------------|
| {Mockup Name} | HTML | [path/to/mockup.html](path/to/mockup.html) | {Brief description} |

> **Note:** UI/UX requirements below are derived from these mockups.

## Overview

[2-3 paragraph detailed description of what this feature does, why it's needed, and who will use it]

## User Stories

As a [user type], I want to [action/goal], so that [benefit/value].

**Examples:**
- As a **customer**, I want to **save items to my cart**, so that **I can purchase them later**.
- As an **admin**, I want to **view all user orders**, so that **I can track sales and resolve issues**.

## Acceptance Criteria

- [ ] Criterion 1: [Specific, measurable condition]
- [ ] Criterion 2: [Specific, measurable condition]
- [ ] Criterion 3: [Specific, measurable condition]
- [ ] Criterion 4: [Specific, measurable condition]
- [ ] Criterion 5: [Specific, measurable condition]

## Functional Requirements

### FR-1: [Requirement Name]

**Description:** [What the system must do]

**Details:**
- Input: [What data is provided]
- Process: [What happens]
- Output: [What result is produced]

### FR-2: [Requirement Name]
[Repeat for each functional requirement]

## Non-Functional Requirements

### NFR-1: Performance

- Response time: [X seconds/milliseconds]
- Throughput: [X requests per second]
- Concurrent users: [X users]

### NFR-2: Security

- Authentication required: [Yes/No]
- Authorization level: [Role/permission required]
- Data encryption: [What data, how encrypted]

### NFR-3: Scalability

- Expected growth: [User/data growth projections]
- Scaling strategy: [Horizontal/vertical]

## UI/UX Requirements

[If applicable]

**Wireframes/Mockups:** [Link or embed]

**User Flows:**
1. User navigates to [page/screen]
2. User performs [action]
3. System displays [result]

**UI Elements:**
- Button: [Label, action]
- Form fields: [List with validation rules]
- Error messages: [List with conditions]

## Dependencies

### Internal Dependencies

- **FEATURE-XXX:** [Why this feature is needed, what it provides]
- **FEATURE-YYY:** [Why this feature is needed, what it provides]

### External Dependencies

- **Library/Service Name:** [Purpose, version if known]
- **Third-party API:** [What functionality it provides]

## Business Rules

### BR-1: [Rule Name]

**Rule:** [Clear statement of business rule]

**Example:** 
- Only authenticated users can add items to cart
- Prices must be positive numbers
- Discounts cannot exceed 90%

### BR-2: [Rule Name]
[Repeat for each business rule]

## Edge Cases & Constraints

### Edge Case 1: [Scenario]

**Scenario:** [Describe unusual or boundary condition]  
**Expected Behavior:** [How system should respond]

**Examples:**
- User session expires during checkout → Redirect to login, preserve cart
- Database connection lost → Show error, queue for retry
- Invalid input format → Return validation error with details

## Out of Scope

- [Explicitly list what this feature does NOT include]
- [Helps prevent scope creep]

**Examples:**
- Social media login (only email/password for v1.0)
- Multi-factor authentication (planned for v2.0)
- Mobile app support (web only for v1.0)

## Technical Considerations

[Hints for technical design - not detailed design, just considerations]

- Suggested technology/framework
- Known performance requirements
- Security considerations
- Integration points

## Open Questions

- [ ] Question 1: [What needs clarification]
- [ ] Question 2: [What needs decision]
- [ ] Question 3: [What needs stakeholder input]

---

1. Open and thoroughly analyze mockup file(s)
2. Extract all visible UI elements and interactions
3. Create UI/UX Requirements section with:
   - Component inventory from mockup
   - User interaction flows
   - Form validation rules
   - Error/empty/loading states
4. Add "Linked Mockups" section at top of specification
5. Cross-reference acceptance criteria to mockup elements
6. Note any functionality implied by mockup not in requirements

1. Query feature board for context
2. Read requirement-details.md
3. Create specification with standard sections
4. Request human review

1. Read dependent feature specifications first
2. Identify integration points
3. Document assumptions about dependencies
4. Note blocking vs non-blocking dependencies

1. Research domain best practices (web search)
2. Document compliance requirements
3. Include domain glossary in specification
4. Ask human for domain-specific clarifications