/intent-story
        ↓
┌───────────────────────────────────┐
│  Phase 1: Background Analysis     │
│  - Detect input language          │
│  - Load writing style (if exists) │
│  - Understand user's IDD usage background │
└─────────────┬─────────────────────┘
              ↓
┌───────────────────────────────────┐
│  Phase 2: Structured Interview    │
│  - Adoption experience            │
│  - Key turning points/lessons     │
│  - Specific benefits/data         │
│  - Suggestions and reflections    │
└─────────────┬─────────────────────┘
              ↓
┌───────────────────────────────────┐
│  Phase 3: Confirm Output Requirements │
│  - Article format/style/length     │
│  - Target language versions       │
└─────────────┬─────────────────────┘
              ↓
┌───────────────────────────────────┐
│  Phase 4: Generate Article        │
│  - Complete blog + social media version │
│  - Multi-language versions (as needed) │
│  - Naturally integrate IDD introduction │
└───────────────────────────────────┘

question: "What type of project did you use IDD in?"
header: "Project Type"
options:
  - label: "System Software/Framework"
    description: "Frameworks, libraries, infrastructure, etc."
  - label: "Web Application"
    description: "Frontend or full-stack Web projects"
  - label: "Mobile Application"
    description: "iOS, Android or cross-platform"
  - label: "Other"
    description: "Other types of projects"

"What made you start trying IDD?"
- A) Documentation is always outdated, looking for a better method
- B) AI-assisted development needs better context management
- C) Team collaboration needs clearer design contracts
- D) Other reasons

"During your use of IDD, was there an 'aha' moment that made you think it was worth it?"
[Open-ended, collect stories]

"What's the most obvious change you observed?"
- A) Improved AI code quality (fewer revisions needed)
- B) Clearer architecture boundaries
- C) Documentation no longer becomes outdated
- D) New team members get up to speed faster
- E) Other

"Can you quantify the benefits? (Optional)"
[Open-ended, e.g., "The proportion of usable code generated by AI in one go increased from 30% to 70%"]

"What challenges or detours have you encountered?"
[Open-ended]

"If you started over, what would you do differently?"
[Open-ended]

"What advice do you have for people considering adopting IDD?"
[Open-ended]

question: "What style should this article be?"
header: "Style"
options:
  - label: "Technical Sharing"
    description: "peer-to-peer, engineer's perspective"
  - label: "Experience Summary"
    description: "Retrospective reflection, Founder/Lead perspective"
  - label: "Getting Started Guide"
    description: "Help newcomers understand and get started"
  - label: "Case Study"
    description: "Detailed project case analysis"

question: "Target length?"
header: "Length"
options:
  - label: "Short Article (800-1200 words)"
    description: "Quick read, key points highlighted"
  - label: "Medium Article (1500-2500 words)"
    description: "In-depth sharing"
  - label: "Long Article (3000+ words)"
    description: "Complete and detailed case analysis"

question: "Which language versions need to be generated?"
header: "Language"
multiSelect: true
options:
  - label: "Chinese"
    description: "Simplified Chinese version"
  - label: "English"
    description: "English version"
  - label: "Both"
    description: "Bilingual (Chinese and English)"

# [Title: Engaging IDD Experience Title]

[Opening: Core insight/conclusion to attract readers]

## Background/Origin

[Why you started using IDD]

## Key Discoveries/Turning Points

[Insights and stories from the usage process]

## Practical Benefits

[Specific changes and quantified data]

## Lessons and Advice

[Advice for others]

## Conclusion

[Summary + IDD introduction]

---

## About IDD

[IDD introduction and toolchain, see template below]

---

## About IDD (Intent Driven Development)

IDD is a development methodology centered around Intent:

**Core Concept**: Intent is the new source code. Code review is done by AI, Intent review is done by humans.

**Toolchain**:
- `/intent-assess` - Evaluate if a project is suitable for IDD
- `/intent-init` - Initialize IDD structure
- `/intent-interview` - Create Intent from ideas
- `/intent-check` - Verify consistency between code and Intent

**Get Started**:
```bash
npx add-skill arcblock/idd

### Social Media Version

Also generate a Twitter/X version:

### Writing Style Guide

Follow these principles (from user's writing style):

| Principle | Description |
|-----------|-------------|
| Clear stance | No fence-sitting, have a clear position |
| Authentic cases | Stories come from users, no fabrication |
| Substantial paragraphs | 4-8 sentences per paragraph, complete discussion |
| Concise subheadings | 2-4 subheadings, rich content |
| Introspective expression | Use "I think..." instead of "You should..." |
| Avoid clichés | Each point must be supported by specific insights |
| Disable em dash | Use "-" or "," instead of "—" |

## Output Example

```markdown
# From "Documentation is Always Outdated" to "Intent is Code" - My IDD Practice

Half a year ago, our team faced a classic dilemma: no matter how well we wrote documentation, it would be outdated in three weeks...

[Body...]

---

## About IDD

IDD (Intent Driven Development) is an Intent-centered development methodology...

[Toolchain introduction...]

**Get Started**:
```bash
git clone https://github.com/ArcBlock/idd
claude mcp add-plugin ~/path/to/idd

## Coordination with Other Commands

## Notes

1. **Authenticity**: All cases and data must come from users, cannot be fabricated
2. **Natural Integration**: IDD introduction must be naturally integrated at the end, not a forced advertisement
3. **User Language**: The main language follows user input
4. **Style Consistency**: If user has writing style configuration, prioritize using it