Module 3: Advanced Use Cases — Reference Materials

1. Complete Use Case Overview

Summary Matrix

#Use CaseBusiness AreaFrequencyImpactDifficulty
1Structuring meeting notesGeneralDaily-Weekly★★★★☆☆
2Auto-converting standard reportsGeneralWeekly-Monthly★★★★☆☆
3Data cleansingData managementAs needed★★★★★☆
4KPI/OKR dashboard data preparationCorporate planningMonthly★★★★★☆
5Process flow diagrams & manualsProcess improvementAs needed★★★★☆☆
6Internal knowledge base constructionGeneralAs needed (large initial effort)★★★★★☆
7RFP draft creationProcurement / ITPer project★★☆★★☆
8Contract risk check assistanceLegal / AdminPer project★★☆★★★
9Multilingual content localizationMarketing / PRAs needed★★☆★★☆
10Business plan scenario simulationCorporate planningQuarterly-Annual★★★★★★
11Grant & subsidy application supportCorporate planning / AdminA few times/year★★★★★★

Legend

  • Impact: Effect on business efficiency (3 stars = highest)
  • Difficulty: Level of Claude Code proficiency required (3 stars = most advanced)
  • Frequency: Typical frequency of use
Phase 1 (Week 1)    : Use Cases 1, 2     <- Start here
Phase 2 (Weeks 2-3) : Use Cases 3, 5     <- Once you are comfortable
Phase 3 (Month 1)   : Use Cases 4, 6     <- Integrate into monthly tasks
Phase 4 (As needed) : Use Cases 7-11     <- As the need arises

2. Prompt Template Collection

Copy the templates below and replace the content in [brackets] with your own information.


Template 1: Structuring Meeting Notes

Read [meeting notes file path] and structure the meeting minutes in the following format.

## Output Format
1. Meeting Minutes (Markdown format)
   - Meeting name, date, attendees
   - Summary by topic
   - Decisions (numbered list)
   - Action items (table with owner, task, deadline)

2. Action Item List (separate file)
   - Grouped by owner
   - Each item in GitHub Issue format (title, body, suggested labels)

Output:
- [output path]-structured.md (structured minutes)
- [output path]-actions.md (action items)

## Additional Notes
- For items without an explicit deadline, write "Deadline TBD"
- If it is unclear whether something is a decision or still under discussion, add a "needs confirmation" note
- [Add any other instructions here]

Template 2: Auto-Converting Standard Reports

Read [detailed report file path] and generate the following versions.

## Summary Version ([output path]-summary.md)
- Target audience: [reader's role/department]
- Length: [approximately one page / 10 bullet points or fewer / etc.]
- Include: [items to include, comma-separated]
- Exclude: [items to exclude, comma-separated]
- Tone: [concise & fact-based / strategic / collaborative / positive / etc.]

## Additional Versions (add sections as needed)
(Same format as above)

## Notes
- Transfer numbers accurately from the original
- Always include [specific information]
- Never include [specific information]

Template 3: Data Cleansing

Read [data file path] and perform data cleansing according to the following rules.

## Cleansing Rules

### [Column 1] Normalization
- [Describe conversion rules]

### [Column 2] Normalization
- [Describe conversion rules]

### Duplicate Detection
- [Describe duplicate detection criteria (e.g., similar company name + contact name)]
- Do not auto-merge; generate a report for human review

## Output
1. [output path]-cleaned.csv (cleansed data)
2. [output path]-report.md (change report)

## Notes
- Do not overwrite the original data
- Flag ambiguous changes as "needs confirmation"
- [Other rules]

Template 4: KPI/OKR Dashboard Data Preparation

Read the files under [data directory path] and create unified KPI dashboard data.

## Data Sources
- [File 1]: [description]
- [File 2]: [description]
- [File 3]: [description]

## Unified Format Specification

### File: [output path]/kpi-summary.csv
Columns:
- Category
- KPI Name
- Target Value
- Actual Value
- Achievement Rate (%)
- Month-over-Month (%)
- Status (Achieved/On Track/At Risk/Below Target)

Status criteria:
- Achieved: Achievement rate >= 100%
- On Track: Achievement rate >= [threshold]%
- At Risk: Achievement rate >= [threshold]%
- Below Target: Achievement rate < [threshold]%

### File: [output path]/kpi-commentary.md
One-line summary per KPI plus recommended actions for at-risk items

Template 5: Process Flow Diagrams & Manuals

Read [interview notes file path] and create the following deliverables.

## 1. Flowchart (Mermaid format)
- Include [main flow / sub-flows]
- Branching conditions: [describe conditions]
- Output: [output path]-flow.md

## 2. Procedure Manual
- Target audience: [new employees / team members / managers]
- Include "owner," "tools used," and "estimated time" for each step
- Include tips on common mistakes and things to watch out for
- Output: [output path]-manual.md

## 3. Open Questions List
- Organize unclear points as a question list
- Output: [output path]-questions.md

Template 6: Internal Knowledge Base Construction

Read all files under [document directory path] and propose a structure
for the internal knowledge base.

## Requirements
- Target audience: [all employees / specific department / new hires]
- Propose a categorization scheme
- Create an article template
- Consolidate overlapping content
- Flag content that may be outdated

## Output
1. [output path]/README.md (table of contents and usage guide)
2. [output path]/template.md (article template)
3. [output path]/structure-proposal.md (proposed structure)

Template 7: RFP Draft Creation

Create an RFP (Request for Proposal) draft based on the following requirements notes.

## Requirements Notes
- Purpose: [what to procure/replace/build]
- Current system: [current state and issues]
- Budget: [budget range]
- Go-live target: [target date]
- Number of users: [expected user count]
- Must-have requirements: [essential features/conditions]
- Nice-to-have: [desirable features/conditions]

## RFP Structure
1. Company overview and project background
2. Current system overview and issues
3. Requirements (functional and non-functional)
4. Items to include in proposals
5. Evaluation criteria (with scoring rubric)
6. Schedule
7. Proposal submission process
8. Contract terms

Output: [output path]

## Notes
- Assign priority levels (Must-have / Should-have / Nice-to-have) to each requirement
- Mark unclear items with a [TBD] tag

Template 8: Contract Risk Check Assistance

Read [contract file path] and perform a risk check using the following checklist.

## Checklist
### Basic Terms
- [ ] Full legal names of contracting parties
- [ ] Contract period and renewal conditions
- [ ] Termination clause (notice period, penalties)

### Fees & Payment Terms
- [ ] Clarity of pricing structure
- [ ] Payment terms
- [ ] Price increase provisions

### Liability & Risk
- [ ] Cap on damages
- [ ] Confidentiality clause
- [ ] Personal data handling
- [ ] Intellectual property ownership

### Other
- [ ] Anti-corruption clause
- [ ] Force majeure clause
- [ ] Governing law and jurisdiction

## Output Format
For each item: relevant clause, risk level (High/Medium/Low), concerns, recommended action

Output: [output path]

* This check is a first-pass screening. Final decisions are made by the legal department.

Template 9: Multilingual Content Localization

Localize the following file into [target language].

Source: [source file path]
Output: [output path]

## Translation Rules
1. Refer to the glossary ([glossary file path]) and use standardized terms
2. Use a [formal/casual/technical] tone appropriate for [content type]
3. Do not translate proper nouns (product names, company names)
4. Date and currency format: [specify format]
5. [Other translation rules]

## Additional Output
If there are terms to add to the glossary, output them as [path]

Template 10: Scenario Simulation

Perform a profit/loss simulation for [number] scenarios based on the following assumptions.

## Business Overview
- Business: [description]
- Revenue model: [monthly subscription / one-time / usage-based / etc.]
- Current scale: [revenue / customers / etc.]

## Scenario Parameters

| Parameter | [Scenario 1 name] | [Scenario 2 name] | [Scenario 3 name] |
|-----------|-------------------|-------------------|-------------------|
| [Parameter 1] | [value] | [value] | [value] |
| [Parameter 2] | [value] | [value] | [value] |
| [Parameter 3] | [value] | [value] | [value] |

## Fixed Conditions (All Scenarios)
- [Fixed cost breakdown]

## Output
1. [output path]/scenario-comparison.csv -- Monthly P/L
2. [output path]/scenario-summary.md -- Annual summary
3. [output path]/sensitivity-analysis.md -- Sensitivity analysis
4. [output path]/break-even-analysis.md -- Break-even analysis

## Notes
- Show your calculations
- Note any assumptions explicitly

Template 11: Grant & Subsidy Application Support

Read the following grant's call for proposals and help prepare the application.

## Target
Grant name: [grant name]
Guidelines file: [file path]

## Task 1: Requirements Summary
Organize eligibility, eligible expenses, subsidy rate/cap, schedule, required documents,
and evaluation criteria.
Output: [output path]-requirements.md

## Task 2: Eligibility Check
Our company:
- Industry: [industry]
- Employees: [count]
- Capitalization: [amount]
- Location: [location]
- Planned investment: [target equipment/tool/project]

Output: [output path]-eligibility.md

## Task 3: Application Draft
Create an application draft following the guidelines.
Mark sections needing company-specific information with [TO BE COMPLETED].
Output: [output path]-draft.md

3. Use Case Selection Flowchart

“Finding the right use case for you”

Follow the flow below to find the best use case to start with.

flowchart TD
    Start([What do you want to streamline<br/>with Claude Code?]) --> Q1{Do you have recurring<br/>tasks every week?}

    Q1 -->|Yes| Q2{What kind of tasks?}
    Q1 -->|No| Q5{Do you have large<br/>project-based tasks?}

    Q2 -->|Meetings & minutes| UC1[Use Case 1<br/>Structuring Meeting Notes]
    Q2 -->|Reports| UC2[Use Case 2<br/>Auto-Converting Reports]
    Q2 -->|Data cleanup| Q3{What type of data?}
    Q2 -->|Document management| UC6[Use Case 6<br/>Knowledge Base Construction]

    Q3 -->|Master data like customer lists| UC3[Use Case 3<br/>Data Cleansing]
    Q3 -->|KPI / performance data| UC4[Use Case 4<br/>KPI Data Preparation]

    Q5 -->|Yes| Q6{What kind of project?}
    Q5 -->|No| Q7{Do you have strategic<br/>planning work?}

    Q6 -->|Vendor selection / procurement| UC7[Use Case 7<br/>RFP Draft Creation]
    Q6 -->|Contracts / legal| UC8[Use Case 8<br/>Contract Risk Check]
    Q6 -->|International / translation| UC9[Use Case 9<br/>Multilingual Localization]
    Q6 -->|Process improvement| UC5[Use Case 5<br/>Flow Diagrams & Manuals]

    Q7 -->|Yes| Q8{What specifically?}
    Q7 -->|No| Restart([Review the textbook<br/>for inspiration])

    Q8 -->|Business planning / budgeting| UC10[Use Case 10<br/>Scenario Simulation]
    Q8 -->|Funding| UC11[Use Case 11<br/>Grant Application Support]

    style UC1 fill:#e1f5fe
    style UC2 fill:#e1f5fe
    style UC3 fill:#e1f5fe
    style UC4 fill:#fff3e0
    style UC5 fill:#fff3e0
    style UC6 fill:#fff3e0
    style UC7 fill:#f3e5f5
    style UC8 fill:#f3e5f5
    style UC9 fill:#f3e5f5
    style UC10 fill:#fce4ec
    style UC11 fill:#fce4ec

Text Version of the Flowchart

For environments where Mermaid is not supported:

Which of the following best describes your situation?

A) I repeat similar tasks every week
   -> Meeting-related       -> Use Case 1 (Structuring Meeting Notes)
   -> Report-related        -> Use Case 2 (Auto-Converting Reports)
   -> Data cleanup          -> Use Case 3 (Data Cleansing)
                              or Use Case 4 (KPI Data Preparation)
   -> Document management   -> Use Case 6 (Knowledge Base Construction)

B) I have large project-based tasks
   -> Vendor selection      -> Use Case 7 (RFP Draft Creation)
   -> Contracts / legal     -> Use Case 8 (Contract Risk Check)
   -> International         -> Use Case 9 (Multilingual Localization)
   -> Process improvement   -> Use Case 5 (Flow Diagrams & Manuals)

C) I am working on strategic planning
   -> Business planning     -> Use Case 10 (Scenario Simulation)
   -> Funding               -> Use Case 11 (Grant Application Support)

4. Important Notes & Considerations

Security & Privacy

CategoryNoteApplicable Use Cases
Personal dataMask or anonymize customer names, contact details, and addresses per your organization’s policy before processing1, 3, 4, 6
Confidential informationBe careful with financial figures, unreleased business plans, and contract terms2, 7, 8, 10, 11
CredentialsNever include API keys, passwords, or access tokens in prompts or filesAll
Third-party informationDo not include non-public information about partners or competitors7, 8, 9

Data Accuracy

CategoryNoteApplicable Use Cases
Verify numbersAlways cross-check dollar amounts, percentages, and dates against the original source2, 3, 4, 10
Verify calculationsSpot-check simulation results by hand10, 11
Fact-checkConfirm that “facts” stated by Claude Code actually exist in the source dataAll
HallucinationsClaude Code may “infer” information not present in the source data. Pay special attention to proper nounsAll
CategoryNoteApplicable Use Cases
Legal validityAI-generated contracts, RFPs, and applications have no legal standing. Always have them reviewed by a specialist7, 8, 11
DisclaimerLegal assessments (e.g., contract risk evaluation) from AI are advisory; final decisions must be made by humans8
TruthfulnessGrant application content must be factual. Do not submit AI-generated text as-is11
Intellectual propertyVerify copyright and licensing for content being translated9

Operational Notes

CategoryNoteApplicable Use Cases
BackupsBack up original data before cleansing or transformation3, 4, 6
Incremental approachFor large datasets, verify quality on a sample before processing the full set3, 4, 9
Version controlUse Git for documents that will be continuously updated (manuals, knowledge base)5, 6
Regular reviewsPeriodically review and update reusable templates and promptsAll
Human reviewAlways have a human review AI output before final use, especially for externally shared documentsAll

The Most Important Principle: AI Output Is a “Draft”

The single most important principle across all use cases is that Claude Code’s output is always a “draft,” never the final version.

  • Meeting minutes -> Have attendees verify
  • Reports -> Cross-check numbers against the original
  • Data cleansing -> Visually review the change report
  • Flow diagrams -> Have the actual process owners review
  • RFPs & contracts -> Have legal/specialists review
  • Simulations -> Verify assumptions and calculations
  • Applications -> Fact-check and have specialists review

By viewing AI not as a “perfect assistant” but as a “talented drafter whose work needs verification,” you can use it safely and effectively.