skills/writing-strategy/references/index.md

# Writing Strategy Index

Use this index to shortlist strategies before loading detailed reference files. Prefer distinctive narrative, case, debate, trend, inquiry, field, or insight structures over generic problem-solution frames unless the user's material clearly calls for a direct fix.

| Reference | English name | Korean name | Category | Best fit | Selection caution |
| --- | --- | --- | --- | --- | --- |
| [3_key_points.md](3_key_points.md) | 3 Key Points | 핵심 3가지 포인트 강조 | synthesis | Use when the draft needs three balanced pillars, principles, or claims. | Avoid when the material is mainly causal, chronological, or conflict-driven. |
| [5_whys_analysis.md](5_whys_analysis.md) | 5 Whys Analysis | 5 WHY 분석 | analysis | Use when the central task is root-cause discovery through repeated why questions. | Avoid when the answer is already known and the draft only needs persuasion. |
| [analogy_comparison_takeaway.md](analogy_comparison_takeaway.md) | Analogy → Comparison → Takeaway | 유사 사례 → 비교 분석 → 시사점 | explanation | Use when an unfamiliar idea can become clear through a familiar analogy and comparison. | Avoid weak analogies that only decorate the topic. |
| [attention_interest_desire_action_aida.md](attention_interest_desire_action_aida.md) | Attention → Interest → Desire → Action (AIDA) | 주목 → 관심 → 욕구 → 행동 | persuasion | Use for marketing, campaign, launch, or advocacy writing that must move readers toward action. | Avoid when the piece needs balanced analysis rather than conversion. |
| [before_after.md](before_after.md) | Before → After | 변화 전 → 변화 후 구조 | change | Use when the strongest story is a clear before-and-after transformation. | Avoid when the middle process matters more than the contrast. |
| [before_after_next_challenge.md](before_after_next_challenge.md) | Before → After → Next Challenge | 변화 전 → 변화 후 → 다음 과제 | change | Use when a transformation is complete enough to show results but still opens a next agenda. | Avoid when the ending should feel fully resolved. |
| [before_journey_after.md](before_journey_after.md) | Before → Journey → After | 여정 기반 구조 | narrative | Use when the process, struggle, or learning journey is as important as the before/after contrast. | Avoid when the journey lacks concrete events. |
| [case_analysis_implication.md](case_analysis_implication.md) | Case → Analysis → Implication | 사례 → 분석 → 시사점 | case | Use when a concrete case can carry the argument and lead to broader implications. | Avoid when there is no specific case or evidence to inspect. |
| [cause_effect.md](cause_effect.md) | Cause → Effect | 원인 → 결과 구조 | analysis | Use when the topic depends on explaining why something happened and what followed. | Avoid when causality is speculative or unproven. |
| [challenge_strategy_result.md](challenge_strategy_result.md) | Challenge → Strategy → Result | 도전 → 전략 → 성과 | achievement | Use for project, team, or organization stories where strategy converted a challenge into results. | Avoid when results are not yet visible. |
| [character_driven_story.md](character_driven_story.md) | Character-Driven Story | 인물 중심 이야기 | narrative | Use when a person, founder, customer, worker, or fictional character should carry the meaning. | Avoid when the subject is impersonal data or policy mechanics. |
| [compare_decide.md](compare_decide.md) | Compare → Decide | 비교 → 선택 구조 | decision | Use when readers must choose among options using explicit criteria. | Avoid when there is only one serious option. |
| [competitor_comparison_own_strength.md](competitor_comparison_own_strength.md) | Competitor Comparison → Own Strength | 경쟁사 비교 → 자사 강점 | business | Use when differentiating a product, company, or proposal against competitors. | Avoid if competitor facts are thin or unverifiable. |
| [concept_expression_tips.md](concept_expression_tips.md) | Concept → Expression → Tips | 컨셉 → 표현 사례 → 적용 팁 | craft | Use when explaining an abstract concept and turning it into expression rules or practical writing tips. | Avoid when the reader needs a business decision rather than craft guidance. |
| [concept_features_use_case.md](concept_features_use_case.md) | Concept → Features → Use Case | 컨셉 소개 → 기능 설명 → 사용 예시 | explanation | Use when introducing a product, service, method, or idea through concept, features, and concrete use. | Avoid when feature lists would overwhelm the reader. |
| [controversy_analysis_proposal.md](controversy_analysis_proposal.md) | Controversy → Analysis → Proposal | 논란 → 다각도 분석 → 제안 | debate | Use when the topic is contested and requires balanced analysis before a proposal. | Avoid when the writer has no room for opposing views. |
| [customer_centric_story.md](customer_centric_story.md) | Customer-Centric Story | 고객 이야기 중심 | case | Use when a customer or user scenario should make the value concrete and empathetic. | Avoid when the customer story would be invented without enough realism. |
| [dissatisfaction_alternative_transformation.md](dissatisfaction_alternative_transformation.md) | Dissatisfaction → Alternative → Transformation | 불만 → 대안 → 변화 | persuasion | Use when reader dissatisfaction can be voiced, answered by an alternative, then shown as change. | Avoid when the pain point is mild or unclear. |
| [expectation_break_new_perspective.md](expectation_break_new_perspective.md) | Expectation Break → New Perspective | 반전 구조 (예상 깨기 → 새로운 관점) | insight | Use when a counterintuitive opening can replace a common assumption with a sharper view. | Avoid forced twists that undermine trust. |
| [experience_lesson_application.md](experience_lesson_application.md) | Experience → Lesson → Application | 경험 → 교훈 → 적용 | reflection | Use for personal, team, or field experience that should yield a lesson and practical application. | Avoid when experience is anecdotal but no transferable lesson exists. |
| [fact_insight_action.md](fact_insight_action.md) | Fact → Insight → Action | 사실 → 인사이트 → 실행 구조 | analysis | Use when facts or data should lead to insight and a concrete next step. | Avoid when the material is mostly emotional or character-led. |
| [fact_interpretation_commentary.md](fact_interpretation_commentary.md) | Fact → Interpretation → Commentary | 사실 → 해석 → 논평 | commentary | Use for opinion columns or analysis pieces that interpret a fact, event, or trend. | Avoid when the user needs a neutral report. |
| [failure_overcome_success.md](failure_overcome_success.md) | Failure → Overcome → Success | 실패 → 극복 → 성공 사례 | narrative | Use when failure, recovery, and success form the emotional core. | Avoid when failure cannot be described honestly. |
| [feature_advantage_benefit_fab.md](feature_advantage_benefit_fab.md) | Feature → Advantage → Benefit (FAB) | 특징 → 장점 → 혜택 구조 | persuasion | Use for product, service, or policy writing that must translate features into reader benefits. | Avoid when the topic is not feature-driven. |
| [goal_obstacle_solution.md](goal_obstacle_solution.md) | Goal → Obstacle → Solution | 목표 → 장애물 → 극복 방안 | planning | Use when a goal is clear and the draft needs to show obstacles and how to overcome them. | Avoid as a default solution frame when a more distinctive narrative fits. Treat as a fallback, not a default. |
| [headline_supporting_points.md](headline_supporting_points.md) | Headline → Supporting Points | 한 줄 메시지 → 근거 나열 | synthesis | Use when one strong headline or thesis can organize several supporting points. | Avoid when the topic is exploratory and the thesis is not settled. |
| [hook_message_call_to_action.md](hook_message_call_to_action.md) | Hook → Message → Call-to-Action | 주목 → 메시지 → 행동 요청 | persuasion | Use for short persuasive writing where attention and action matter more than deep explanation. | Avoid for long-form analytical drafts. |
| [introduction_body_conclusion.md](introduction_body_conclusion.md) | Introduction → Body → Conclusion | 서론 → 본론 → 결론 | general | Use only as a fallback for simple explanatory writing or when the user explicitly wants a standard essay. | Avoid as the default because it hides more specific narrative choices. Treat as a fallback, not a default. |
| [issue_debate_conclusion.md](issue_debate_conclusion.md) | Issue → Debate → Conclusion | 이슈 → 쟁점 → 결론 | debate | Use when a topic has identifiable issues and opposing arguments that need a reasoned conclusion. | Avoid if the piece should remain open-ended. |
| [keywords_meaning.md](keywords_meaning.md) | Keywords → Meaning | 키워드 나열 → 의미 부여 | explanation | Use when several keywords should anchor the article and each needs meaning or interpretation. | Avoid when the sequence of events matters more than terms. |
| [market_opportunity_execution.md](market_opportunity_execution.md) | Market → Opportunity → Execution | 시장 분석 → 기회 포착 → 실행 계획 | business | Use for market analysis that must move from market conditions to opportunity and execution. | Avoid when market evidence is missing. |
| [misunderstanding_truth_conviction.md](misunderstanding_truth_conviction.md) | Misunderstanding → Truth → Conviction | 오해 → 진실 → 확신 | myth | Use when the reader likely holds a misconception that the draft should correct persuasively. | Avoid when the misconception is not common or would sound patronizing. |
| [need_solution_satisfaction.md](need_solution_satisfaction.md) | Need → Solution → Satisfaction | 니즈 → 솔루션 → 만족 구조 | persuasion | Use when the reader's need can be connected to a solution and a satisfying result. | Avoid as a generic problem-solution substitute unless the need is vivid. Treat as a fallback, not a default. |
| [observation_pattern_insight.md](observation_pattern_insight.md) | Observation → Pattern → Insight | 관찰 → 패턴 → 인사이트 | insight | Use when scattered observations reveal a pattern and a deeper insight. | Avoid when there are too few observations to form a pattern. |
| [pain_claim_gain.md](pain_claim_gain.md) | Pain → Claim → Gain | 고통 → 제안 → 기대 효과 | persuasion | Use when a sharp pain point should lead to a claim and a tangible gain. | Avoid when the tone should be gentle or exploratory. |
| [past_present_future.md](past_present_future.md) | Past → Present → Future | 과거 → 현재 → 미래 구조 | time | Use when historical change or evolution is the best organizing principle. | Avoid when the topic is not time-dependent. |
| [phenomenon_insight_proposal.md](phenomenon_insight_proposal.md) | Phenomenon → Insight → Proposal | 현상 → 인사이트 → 대안 제시 | insight | Use when a visible phenomenon should be interpreted and turned into a proposal. | Avoid when the phenomenon is only a symptom of a simpler problem. |
| [problem_analysis_solution_outcome.md](problem_analysis_solution_outcome.md) | Problem → Analysis → Solution → Outcome | 문제 → 분석 → 해결책 → 기대 효과 | analysis | Use for diagnostic proposals where the problem needs careful analysis before solution and outcome. | Avoid as a reflexive structure for every improvement topic. Treat as a fallback, not a default. |
| [problem_solution.md](problem_solution.md) | Problem → Solution | 문제 → 해결 구조 | general | Use only when the user asks for a direct fix or the material is truly simple. | Avoid as the default; check more specific strategies first. Treat as a fallback, not a default. |
| [question_experiment_conclusion.md](question_experiment_conclusion.md) | Question → Experiment → Conclusion | 의문 → 실험 → 결론 | inquiry | Use when the article can be framed as a question tested through experiment or evidence. | Avoid when no test, trial, or comparison exists. |
| [question_exploration_discovery.md](question_exploration_discovery.md) | Question → Exploration → Discovery | 질문 → 탐색 → 발견 | inquiry | Use for reflective or investigative writing that should invite readers into a search. | Avoid when the conclusion must be stated immediately. |
| [question_imagination_resolution.md](question_imagination_resolution.md) | Question → Imagination → Resolution | 반응 유도형 (질문 → 상상 → 정리) | creative | Use when a speculative question or what-if scenario can open the reader's imagination. | Avoid when the topic requires strict factual reporting. |
| [quote_interpretation_application.md](quote_interpretation_application.md) | Quote → Interpretation → Application | 인용 → 해석 → 적용 | reflection | Use when a quote, sentence, or external voice should become the interpretive anchor. | Avoid when the quote is decorative rather than central. |
| [status_problem_solution.md](status_problem_solution.md) | Status → Problem → Solution | 현황 → 문제점 → 해결책 | general | Use for status reports that must move from current state to issue and response. | Avoid as the default for broader essays or stories. Treat as a fallback, not a default. |
| [swot_strategy_execution.md](swot_strategy_execution.md) | SWOT → Strategy → Execution | SWOT → 전략 → 실행 | business | Use for strategic assessment where strengths, weaknesses, opportunities, and threats matter. | Avoid when SWOT would become a checklist without a decision. |
| [tension_relief_resolution.md](tension_relief_resolution.md) | Tension → Relief → Resolution | 긴장 → 이완 → 결론 | narrative | Use when suspense, conflict, or emotional tension should pull the reader through the piece. | Avoid when the tone must stay strictly neutral. |
| [time_based_narrative.md](time_based_narrative.md) | Time-Based Narrative | 시간 흐름 기반 전개 | time | Use when chronology, milestones, or process order should structure the writing. | Avoid if time order is incidental. |
| [trend_example_action_tea.md](trend_example_action_tea.md) | Trend → Example → Action (TEA) | 트렌드 → 사례 → 실행 | trend | Use when a trend should be made credible through examples and translated into action. | Avoid when no timely examples are available. |
| [trend_opportunity_strategy.md](trend_opportunity_strategy.md) | Trend → Opportunity → Strategy | 트렌드 → 기회 → 대응 전략 | trend | Use when a trend creates a concrete opportunity that calls for strategic response. | Avoid when the trend is vague or not yet relevant. |
| [viewpoint_evidence_persuasion.md](viewpoint_evidence_persuasion.md) | Viewpoint → Evidence → Persuasion | 관점 제시 → 근거 제시 → 설득 | argument | Use when a clear viewpoint must be supported by evidence and persuasion. | Avoid when the piece should present multiple views evenly. |
| [vision_plan_action.md](vision_plan_action.md) | Vision → Plan → Action | 비전 → 계획 → 실행 | planning | Use when a future vision should be made credible through plan and action. | Avoid when the vision is not yet defined. |
| [voice_from_field_insight.md](voice_from_field_insight.md) | Voice from Field → Insight | 현장 목소리 → 인사이트 | field | Use when frontline voices, interviews, or field notes should reveal insight. | Avoid when there is no concrete voice from the field. |
| [voice_of_customer_empathy_proposal.md](voice_of_customer_empathy_proposal.md) | Voice of Customer → Empathy → Proposal | 고객의 말 → 공감 → 제안 | field | Use when customer words should lead to empathy and a practical proposal. | Avoid when customer quotes are unavailable or too generic. |
| [why_what_how.md](why_what_how.md) | Why → What → How | 왜 → 무엇 → 어떻게 | explanation | Use when readers need the rationale, the object, and the method in that order. | Avoid when the piece needs tension, case depth, or controversy. |