┌─────────────────────────────────────────────────────────────┐
│                      Insight Sources                        │
├─────────────────────────────────────────────────────────────┤
│  🎨 UI/UX Review     │ Interface issues, interaction optimization, visual improvements            │
├─────────────────────────────────────────────────────────────┤
│  📄 Document Research       │ Technical solutions, design patterns, architecture references            │
├─────────────────────────────────────────────────────────────┤
│  🔍 External Reference       │ Competitor analysis, industry best practices, open source projects        │
├─────────────────────────────────────────────────────────────┤
│  💡 Internal Feedback       │ User feedback, team suggestions, performance monitoring            │
└─────────────────────────────────────────────────────────────┘

Insight Sources                Confirmation Stage                 Output Stage
    │                      │                        │
    ▼                      ▼                        ▼
┌─────────┐          ┌─────────┐            ┌─────────────┐
│ Collect │    →     │ User    │      →     │ Append to    │
│ Suggestions │          │ Confirmation │            │ Requirements Doc │
└─────────┘          └─────────┘            └─────────────┘
                          │
                          ▼
                    Partial Confirmation / Full Confirmation / Reject

1. Identify Insight Sources
   │
   ▼
2. Collect/Organize Suggestions
   ├── UI/UX Review Results
   ├── Document Research Findings
   ├── External Reference Insights
   └── Internal Feedback Summary
   │
   ▼
3. Structured Suggestion List
   ├── Categorize and Organize
   ├── Evaluate Impact Scope
   └── Prioritize Suggestions
   │
   ▼
4. User Confirmation (AskUserQuestion)
   ├── Confirm Item by Item
   ├── Batch Confirmation
   └── Adjust Priorities
   │
   ▼
5. Convert to Requirements
   ├── Generate Feature Points (F-XXX)
   ├── Generate Acceptance Criteria (AC-XXX)
   └── Append to 01-requirements.md
   │
   ▼
6. Post-Suggestion Process
   └── Run /devdocs-system-design or /devdocs-dev-tasks

undefined

undefined

undefined

undefined

**Input**:
- Screenshots/prototypes provided by user
- User describes interaction issues
- Results from running /ui-orchestrator review

**Focus Areas**:
- Usability issues
- Visual consistency
- Accessibility
- Responsive adaptation
- Interaction fluency

**Example Suggestions**:
- INS-001: Insufficient button contrast affects readability
- INS-002: Form lacks loading state feedback
- INS-003: Mobile navigation menu is hard to click

**Input**:
- Technical document links
- Design scheme documents
- Best practice guides

**Focus Areas**:
- Referenceable architecture patterns
- Optimal implementation solutions
- Performance optimization techniques
- Security hardening measures

**Example Suggestions**:
- INS-004: Replace manual state management with React Query
- INS-005: Introduce optimistic updates to enhance user experience
- INS-006: Use Zod for runtime type validation

**Input**:
- Competitor links/screenshots
- Open source project references
- Industry reports

**Focus Areas**:
- Competitor advantage features
- Industry common patterns
- Align with user expectations

**Example Suggestions**:
- INS-007: Reference Notion's drag-and-drop sorting interaction
- INS-008: Adopt Linear's shortcut key system
- INS-009: Implement real-time collaboration similar to Figma

**Input**:
- User feedback records
- Team discussion results
- Performance monitoring data

**Focus Areas**:
- High-frequency user pain points
- Team consensus issues
- Performance bottlenecks

**Example Suggestions**:
- INS-010: List loading is slow, needs pagination or virtual scrolling
- INS-011: Search function lacks advanced filtering
- INS-012: Export function needs to support more formats

Suggestion INS-001: Insufficient button contrast affects readability

Source: 🎨 UI/UX Review
Priority: P1
Impact Scope: Global button components

Confirm conversion to requirement?
- Confirm (convert to F-XXX)
- Confirm after adjusting priority
- Reject (please explain reason)
- Decide later

The following suggestions are pending confirmation:

| ID | Title | Priority |
|------|------|--------|
| INS-001 | Insufficient button contrast | P1 |
| INS-002 | Missing loading state | P1 |
| INS-003 | Mobile navigation issues | P2 |

Please select:
- Confirm All
- Selective Confirmation (Enter IDs, e.g.: 1,2)
- Reject All
- Review Item by Item

undefined

undefined

User: I just reviewed the login page and found several issues to optimize

Agent: Sure, let me help you collect these optimization suggestions. Please describe the issues you found:

User:
1. Password input box has no show/hide toggle
2. Forgot password link is not prominent enough
3. Third-party login button styles are inconsistent

Agent: The following suggestions have been organized:

| ID | Title | Priority | Status |
|------|------|--------|------|
| INS-001 | Add password visibility toggle | P1 | ⏳ |
| INS-002 | Highlight forgot password link | P2 | ⏳ |
| INS-003 | Unify third-party login button styles | P2 | ⏳ |

Please confirm the suggestions to convert to requirements (Enter IDs, e.g. 1,2,3 or "All"):

User: 1,3

Agent:
✅ Confirmed INS-001, INS-003
Appended to 01-requirements.md:
- F-015: Password Visibility Toggle [Optimization] (Source: INS-001)
- F-016: Unify Third-Party Login Buttons [Optimization] (Source: INS-003)

Would you like to continue running /devdocs-dev-tasks to split into development tasks?

User: I read this article https://example.com/react-patterns and want to reference some patterns

Agent: Let me analyze this article and extract referenceable insights...

[WebFetch retrieves content]

Based on the article content, the following reference suggestions have been organized:

| ID | Title | Reference Section | Priority |
|------|------|----------|--------|
| INS-001 | Adopt Compound Components Pattern | Section 3 | P1 |
| INS-002 | Use Render Props instead of HOC | Section 5 | P2 |
| INS-003 | Introduce Custom Hooks for logic reuse | Section 7 | P1 |

Please confirm the suggestions you want to adopt:

undefined

undefined

Confirmed Improvement Suggestions
      │
      ▼
Evaluate if Architectural Changes are Involved
      │
      ├── No Architectural Changes (Simple Improvements)
      │   ├── UI tweaks, configuration changes, small features
      │   └── → /devdocs-dev-tasks Directly split into tasks
      │
      └── With Architectural Changes (Complex Improvements)
          ├── New APIs, data model changes, new modules
          └── → /devdocs-feature Full Process
                  └── system-design → test-cases → dev-tasks

X improvement suggestions have been confirmed and converted into requirements.

The following situations have been detected:
- INS-001: UI button style adjustment → No architectural changes
- INS-003: New export API added → Involves architectural changes

Recommended Paths:
- INS-001 → /devdocs-dev-tasks (Directly split into tasks)
- INS-003 → /devdocs-feature (Full process)

Execute as suggested? [Yes/Adjust]