# iso-24495

Adopt this skill: https://proskills.md/skills/other/danyuchn-iso-24495-skill

Page: https://proskills.md/skills/other/danyuchn-iso-24495-skill
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: SKILL.md
size: 5664
sha: 1efc8ace738875d929e30bf430a23110c745a192
upstream: https://github.com/danyuchn/iso-24495-skill/blob/HEAD/SKILL.md

```text
---
name: iso-24495
description: "Use when text must be easy for its intended reader to find, understand, and act on — reports, emails, documentation, UI text, announcements, explanations, AI output that reads as dense or bureaucratic. Applies ISO 24495-1 plain language principles with dedicated technique layers for English and Traditional Chinese. Triggers: plain language rewrite, apply ISO 24495, make this clearer for readers, de-jargon this, 淺白改寫, 白話改寫, 去公文腔, 讓讀者一次看懂. Not for creative or literary writing."
version: 0.1.0
---

# ISO 24495-1 Plain Language (English + Traditional Chinese)

ISO 24495-1:2023 is the international standard for plain language. It defines
plain language by reader outcome, not by word lists: a document is plain when
its intended readers can get what they need (relevant), find it (findable),
understand it on first reading (understandable), and act on it (usable).

This skill rewrites text so it meets those four outcomes. The principles are
language-independent — ISO states the standard "applies to most, if not all,
written languages" — so this skill ships one shared principle layer and two
language technique layers:

- **English** → apply `references/english-techniques.md`
- **Traditional Chinese（繁體中文）** → apply `references/chinese-techniques.md`

The Chinese layer is not a translation of the English layer. It is a separate
technique set for problems Chinese text actually has (歐化長句、公文腔、
成語堆疊、中英夾雜、被字句濫用). As of this skill's release, no national
standards body has published a Chinese adaptation of ISO 24495-1; this layer
is an original implementation of the principles for Chinese.

## When to Use This Skill

- A reader-facing text (report, email, doc page, UI string, announcement,
  policy, explanation) reads as dense, bureaucratic, hedged, or jargon-heavy.
- AI-generated output is technically correct but hard to read.
- Text must work for non-specialist readers, non-native readers, or busy
  readers who will scan rather than study.
- You want a before/after with the violated principle named per change —
  ask for it; the default output is the rewritten text alone.

Not for creative or literary writing, and not for agent-facing controlled
language — for text a machine must parse without ambiguity, use a controlled
language standard such as ASD-STE100 instead (see Scope Boundary below).

## Procedure

1. **Identify the reader and purpose** (Principle 1 requires it). If the user
   named an audience, use it. Otherwise assume a busy, intelligent,
   non-specialist adult reader and state that assumption in one line only
   when it changes the rewrite materially.
2. **Detect the text language.** English → English techniques file. Chinese →
   Chinese techniques file. Mixed text → the dominant language's file, and
   handle embedded foreign terms per that file's rules. Other languages →
   apply the four principles directly and say the technique layer for that
   language does not exist yet.
3. **Read the whole text for meaning before touching a sentence.**
4. **Rewrite against the four principles**, using the language file's
   techniques. Never drop a fact, condition, number, or scope qualifier.
   If plainness would cost precision, keep the precision and flag the
   trade-off in one line.
5. **Run the language file's self-check list** before returning.

## Output Format

Return the rewritten text alone — no preamble, no principle lecture, no
change summary. Append a one-line `Kept as-is:` note only when something was
deliberately left unsimplified for precision.

When the user asks to "show the diff", "explain the changes", or "which
principles", return a before/after table instead, one row per change, naming
the principle (relevant / findable / understandable / usable) and the
technique applied.

## The Four Principles (working definitions)

| Principle | The reader outcome it protects |
|---|---|
| Relevant | The text contains what this reader needs for this purpose — and nothing else. Cutting is a rewrite tool, not just rearranging. |
| Findable | The reader can locate the part they need without reading everything: informative headings, front-loaded key points, lists for parallel items, one topic per paragraph. |
| Understandable | The reader gets it on first reading: common words, short sentences, active constructions, defined terms, no unexplained jargon. |
| Usable | The reader can act: concrete instructions, explicit actors and deadlines, next steps stated as steps. |

Full interpretation, sources, and copyright boundaries:
`references/principles.md`.

## Scope Boundary: Plain Language vs Controlled Language

ISO 24495-1 optimizes text for **human readers** and permits full natural
language. Controlled-language standards such as ASD-STE100 optimize for
**zero-ambiguity parsing** (originally by maintenance technicians, now also
by AI agents) and restrict vocabulary and grammar hard. If the reader is a
machine or the cost of one misread word is high, use a controlled-language
skill. If the reader is a person who needs to find, understand, and act,
use this one.

## Copyright Note

This is an unofficial project, not affiliated with or endorsed by ISO. The
full ISO 24495-1 text is a licensed document and is not reproduced here. This
skill is built from the standard's publicly documented principles and public
plain-language practice; every quantitative rule in the technique files is
this project's own working proxy, not a clause of the standard. For certified
conformance work, buy and consult the standard itself.
```

## File: README.md
size: 6342
sha: d8e7688cf46862c4981bc06efb65461e00d56cfb
upstream: https://github.com/danyuchn/iso-24495-skill/blob/HEAD/README.md

````text
# ISO 24495 Skill — Plain Language for English and Traditional Chinese

A Claude Code skill that rewrites text into plain language per
[ISO 24495-1:2023](https://www.iso.org/standard/78907.html) — the
international standard that defines plain language by reader outcome: the
intended readers can **find** what they need, **understand** it on first
reading, and **use** it.

Two things make this skill different from a one-line "write plainly" prompt:

1. **It implements the standard's actual structure** — reader-first content
   selection (relevant), document structure (findable), wording
   (understandable), and actionability (usable) — not just shorter sentences.
2. **It ships a real Traditional Chinese technique layer（繁體中文層）.**
   ISO 24495-1 is explicitly language-independent, but as of this release the
   [official translation list](https://www.iplfederation.org/standard-translations/)
   contains no East Asian language at all. The Chinese layer here is an
   original implementation of the four principles for Chinese — targeting the
   problems Chinese text actually has（歐化長句、公文腔、成語堆疊、中英夾雜、
   被字句濫用）, not a translation of the English rules.

## Before / After

| Before | After |
|---|---|
| "It is expected that the reimbursement form should be completed and submitted in a timely manner in order for processing to be initiated." | "Submit your reimbursement form by the 25th. We start processing it the day we receive it." |
| 「相關費用之核銷單據應儘速填妥並繳交，俾利後續作業之進行。」 | 「請在每月 25 日前把核銷單交給財務部的王小姐。我們收到當天就開始處理。」 |
| "The team will make a determination as to whether an implementation of the proposed solution may potentially be feasible in some circumstances." | "The team will decide whether the proposed solution is feasible." |
| 「請先 review 這份 proposal 的 scope，確認 stakeholder 的 alignment 沒問題之後，我們再 kick off 這個 project。」 | 「請先看過這份提案的範圍，確認相關的人都同意了，我們再開始做。」 |

More pairs, each naming the principle applied:
[`examples/before-after-en.md`](examples/before-after-en.md) ·
[`examples/before-after-zh.md`](examples/before-after-zh.md).

## What This Skill Does

1. Identifies the intended reader and purpose — the standard's first
   principle requires it, and every cut/keep decision follows from it.
2. Detects the text language and loads the matching technique layer:
   [`references/english-techniques.md`](references/english-techniques.md) or
   [`references/chinese-techniques.md`](references/chinese-techniques.md).
3. Rewrites against the four principles (relevant → findable →
   understandable → usable) without dropping any fact, number, condition, or
   honest hedge. Where plainness would cost precision, it keeps the
   precision and flags the trade-off.
4. Returns the rewritten text alone — no preamble, no lecture. Ask for
   "show the diff" and it returns a before/after table naming the principle
   behind each change instead.

## Architecture: one shared layer, per-language technique layers

```
SKILL.md                          shared layer (English): principles, procedure, routing
references/principles.md          the four principles, interpretation, sources
references/english-techniques.md  English techniques (in English)
references/chinese-techniques.md  中文手法（以中文撰寫）
```

The shared layer is language-independent, mirroring the standard itself.
Technique layers are written in their own language, because plain language
techniques do not translate: English fights nominalization and passive
voice; Chinese fights Europeanized long sentences and bureaucratic register.
Adding another language = adding one technique file. Contributions welcome.

## Installation

```bash
git clone https://github.com/danyuchn/iso-24495-skill ~/.claude/skills/iso-24495
```

## Usage

```
Rewrite this in plain language
Apply ISO 24495 to this announcement
把這段改成淺白中文
幫我去掉這封信的公文腔
```

You get the rewritten text back and nothing else. Add "show the diff" /
「列出改了什麼」 to see the per-change principle table.

## Scope

Built for: reader-facing text — reports, emails, documentation, UI strings,
announcements, policies, explanations, and AI output that reads as dense or
bureaucratic. Works on English and Traditional Chinese; the principles apply
to other languages but no technique layer exists for them yet.

Not built for: creative or literary writing (voice is the point there), and
not for **agent-facing** text where a machine must parse without ambiguity —
that is controlled-language territory; use the companion skill
[asd-ste100-skill](https://github.com/danyuchn/asd-ste100-skill) instead.
Rule of thumb: reader is a person → this skill; reader is a machine or a
maintenance manual → STE.

## Relationship to the ISO Standard

This is an unofficial project, not affiliated with, endorsed by, or approved
by ISO. The full ISO 24495-1 text is a licensed document and is **not**
reproduced here. The skill is built from the standard's publicly documented
principle framework (ISO's published abstract and scope, and the
International Plain Language Federation's freely published materials). Every
quantitative rule in the technique files is this project's own working
proxy, not a clause of the standard. For certified conformance, buy and
consult the standard.

## Sources

- [ISO 24495-1:2023 — Plain language, Part 1](https://www.iso.org/standard/78907.html)
- [International Plain Language Federation — ISO standard](https://www.iplfederation.org/iso-standard/)
- [IPLF — national adoptions and translations](https://www.iplfederation.org/standard-translations/)
- [AccessibleEU — ISO 24495-1 summary](https://accessible-eu-centre.ec.europa.eu/content-corner/digital-library/iso-24495-12023-plain-language-part-1-governing-principles-and-guidelines_en)
- Companion controlled-language skill: [asd-ste100-skill](https://github.com/danyuchn/asd-ste100-skill)

## License

MIT — see [LICENSE](LICENSE). The license covers this repository's original
text; it grants no rights to any ISO publication.
````

## File: references/chinese-techniques.md
size: 4692
sha: d1e14c825b9dda94e9e68da806d8057993265978
upstream: https://github.com/danyuchn/iso-24495-skill/blob/HEAD/references/chinese-techniques.md

```text
# 中文淺白手法（繁體中文層）

輸入文字是中文時套用本檔。每一條手法都對應四原則之一（相關／找得到／
看得懂／用得上）。所有數字門檻都是本專案自訂的警戒線，不是標準條文——
超過時多看一眼，不是機械硬砍。

中文的淺白問題和英文不同：英文的敵人是名詞化、被動式、罕字；中文的敵人
是歐化長句、公文腔、成語堆疊、中英夾雜、指代不明。本檔針對中文自己的病。

## 相關——內容取捨

- **先認讀者再動筆。** 一句話寫死：「等退款的客戶」「第一次用這套系統的
  同事」。之後每一句留或刪都看這行。
- **刪開場白與客套墊話。**「眾所周知」「在此特別說明」「如前所述」「隨著
  科技的快速發展」——整句刪掉，直接說事。
- **刪讀者用不到的內容。** 讀者已知的背景、內部流程細節、寫給主管看的
  免責鋪陳。拿不準就移到文末，不要留在開頭擋路。

## 找得到——結構

- **結論先行。** 第一句就是結論、決定或要讀者做的事；理由放後面。中文
  公文習慣「鋪陳—轉折—結論」，淺白寫法把這個順序倒過來。
- **標題要說出內容，不是分類。**「退款五到七天入帳」勝過「退款相關說明」。
- **一段一主題；超過五句就檢查是不是混了兩件事。**
- **三項以上的並列改條列**，步驟一律編號；各條句式對齊。
- **要對照的數字進表格**，要講理的進正文。

## 看得懂——用語

- **短句，一句一個意思。** 中文警戒線約 40 字。歐化長句（「作為一個……
  的……的……」、多層「的」字鏈）拆成短句；「的」連用三次即警戒。
- **主動句式，動作者明確。**「我們會退款給你」勝過「款項將被退回」。
  「被」字句只留給真正不知道動作者、或動作者不重要的情況；「進行」
  「加以」這類墊字動詞刪掉（「進行討論」→「討論」）。
- **不中英夾雜。** 有通行中文就用中文。真的沒有中文、或中文反而更難懂的
  專有名詞（如 Excel、Claude、PDF），保留原文但**第一次出現立刻用括號補
  一句白話**：「Bloomberg（金融業查股價和財報的付費系統）」。之後可直接用。
- **不用術語與縮寫。** 能說「表格」就不說「試算表檔案」，能說「先付一部分
  錢」就不說「首期款」。非用不可的術語，第一次出現就定義，之後全文只用
  這一個名字，不換說法。
- **去成語、去文言殘留。** 成語和四字套語（「與時俱進」「不可或缺」「舉足
  輕重」）是壓縮包，讀者要解壓縮才懂；改成直說。「之」「乃」「係」「惟」
  這類文言殘留改白話。
- **指代與量詞明確。**「這個部分」「相關單位」「該項作業」都要問：是哪個？
  能點名就點名。數量寫清楚：「三天內」勝過「儘速」，「每月一次」勝過
  「定期」。
- **保留誠實的不確定。**「可能」「預計」承載真實資訊時不得刪；刪的是
  裝飾性的堆疊（「或許有可能在某些情況下」→「可能」）。

## 用得上——可執行

- **指示寫成動作句：誰、做什麼、期限。**「請在 3 月 31 日前交回同意書」
  勝過「同意書應儘速繳回」。
- **每個義務都有主詞。**「本案應予處理」不合格——誰處理？
- **條件放在動作前面**（「如果 X，就做 Y」），讓不適用的讀者早點離開。
- **結尾給下一步。** 讀者看完該做什麼，最後一句直接說。

## 解釋性文體的加強手法

對象是「要把一件事講懂」的文字（說明、教學、公告的背景段）時，加用：

- **比喻與生活例子。** 抽象機制先給一個日常對照（「這就像……」），再講
  正式版。
- **先講對讀者的意義**（好消息還是壞消息、要不要做事、會不會花錢），
  再講細節。
- **寧可少講、講清楚。** 看不懂的根因通常是講太多，不是講太少。

## 自查清單（回傳前逐條掃）

1. 指定的讀者讀完一遍，能不能用自己的話複述重點？
2. 結論是不是在前兩行？
3. 有沒有一句話塞兩個意思？一段塞兩個主題？
4. 有沒有沒括號解釋的外文詞、沒定義的術語、換過名字的同一個東西？
5. 有沒有哪句話要先懂另一個術語才看得懂？有就拆開先解釋。
6. 事實、數字、條件、誠實的「可能」是不是全部都還在？
```

## File: references/english-techniques.md
size: 3340
sha: 09c8c5fe2e6120a2e06023182e360ace9c63d7df
upstream: https://github.com/danyuchn/iso-24495-skill/blob/HEAD/references/english-techniques.md

```text
# English Techniques

Apply these when the input text is English. Each technique serves one of the
four principles. Numeric targets are this project's working proxies, not
clauses of the standard: treat them as tripwires for a second look, not as
hard caps.

## Relevant — content selection

- **Name the reader before editing.** One line, e.g. "customers waiting for
  a refund" or "engineers on call". Every cut and keep decision follows it.
- **Cut throat-clearing.** Openers like "It is important to note that",
  "In today's fast-paced world", "As previously mentioned" carry no reader
  value. Delete them; keep the clause they were delaying.
- **Cut what this reader will not use.** Background the reader already has,
  internal process detail, defensive caveats aimed at the author's boss.
  When unsure, move it to the end rather than deleting.

## Findable — structure

- **Front-load the point.** Conclusion, decision, or required action in the
  first sentence or a bolded first line. Reasons after.
- **Informative headings.** A heading states the content's message ("Refunds
  take 5–7 days"), not its category ("Refund information") when the message
  fits.
- **One topic per paragraph; ~5 sentences as a tripwire.**
- **Lists for 3+ parallel items** — steps, options, conditions. Keep list
  items grammatically parallel.
- **Tables for lookups**, prose for reasoning. If the reader will compare
  values, it is a table.

## Understandable — wording

- **Sentence length ~20 words as a tripwire.** Longer is allowed when the
  sentence carries one idea cleanly; two ideas in one sentence is the real
  violation.
- **Active constructions with explicit actors.** "We will refund you" not
  "A refund will be issued". Passive is fine when the actor is genuinely
  unknown or irrelevant.
- **Verbs over nominalizations.** "decide" not "make a determination";
  "apply" not "submit an application" (unless the noun is the term of art).
- **Common words.** "use" not "utilize", "help" not "facilitate", "about"
  not "approximately" — unless the rarer word is a defined term.
- **Define terms at first use, then never rotate.** One name per concept
  for the whole document. Synonym variety is a literary virtue and a plain
  language defect.
- **Kill hedge stacks.** "may potentially, in some cases" → "may". Keep one
  honest hedge; delete the decorative ones. Never delete a hedge that
  carries real uncertainty.
- **Expand or gloss abbreviations at first use** unless the audience
  definition makes them safe.

## Usable — actionability

- **Instructions as imperatives with explicit objects and deadlines.**
  "Submit the form by March 31" not "the form should be submitted in a
  timely manner".
- **State who does what.** Every obligation names its actor.
- **Put conditions before the instruction** ("If X, do Y"), so readers can
  bail out early.
- **End reader-facing messages with the next step**, if one exists.

## Self-Check (run before returning)

1. Can the named reader say, after one reading, what this text wants them
   to know or do?
2. Is the main point in the first two lines?
3. Any sentence carrying two ideas? Any paragraph carrying two topics?
4. Any term used under two names, or any jargon left undefined?
5. Did every fact, number, condition, and honest hedge survive the rewrite?
```

## File: references/principles.md
size: 4307
sha: 46ae901a6753c870969278e723fd990bc3c32e3c
upstream: https://github.com/danyuchn/iso-24495-skill/blob/HEAD/references/principles.md

```text
# ISO 24495-1 — Principles, Interpretation, and Sources

This file summarizes the publicly documented content of ISO 24495-1:2023
(*Plain language — Part 1: Governing principles and guidelines*) and states
how this skill interprets it. It paraphrases principles; it does not
reproduce the standard's text.

## What ISO 24495-1 Is

Published June 2023 by ISO Technical Committee 37, developed with the
International Plain Language Federation (IPLF). It is the first international
standard that defines plain language, and it defines it as a **reader
outcome**, not a style: language is plain when its wording, structure, and
design let the intended readers easily find what they need, understand it,
and use it.

Two properties matter for this skill:

1. **Language-independent.** ISO's own abstract: the document "applies to
   most, if not all, written languages, but provides examples only in
   English." The principles govern any language; the techniques must be
   built per language. That is exactly the split this skill implements.
2. **Principles-based, not rules-based.** The standard gives four governing
   principles with guidelines on how to interpret and apply them. It contains
   no approved-word dictionary and no hard numeric limits. Every numeric
   threshold in this repo's technique files (sentence length targets, list
   thresholds, paragraph limits) is this project's own proxy.

The series continues: Part 2 (2025) covers legal communication, Part 3
covers science writing. This skill implements Part 1 only.

## The Four Principles, As This Skill Applies Them

**1. Relevant — readers get what they need.**
Identify the reader and purpose first; the same text can be plain for one
audience and opaque for another. Select content for that reader; cut what
does not serve them. In rewriting practice: deleting a paragraph the reader
does not need is a legitimate and often the single most effective edit.

**2. Findable — readers can easily find what they need.**
Order content by the reader's priority, not the author's chronology. Put
conclusions and required actions first. Use informative headings (a heading
should answer, not tease), one topic per paragraph, and lists for parallel
items so the eye can index the page.

**3. Understandable — readers understand on first reading.**
Common words over rare ones. Short sentences carrying one idea each.
Explicit actors. Terms defined at first use, then used consistently — never
rotated with synonyms. No unexplained jargon, no stacked hedges, no
nominalized actions where a verb is available.

**4. Usable — readers can use the information.**
If the reader must do something, write it as a doable step with an explicit
actor, object, and deadline. "The form should be submitted by applicants in
a timely manner" fails; "Submit the form by March 31" passes.

The principles are ordered: relevance decisions come first (what to say),
findability next (where to put it), then understandability and usability
(how to word it). A rewrite that only polishes sentences while keeping an
author-centric structure has applied half the standard.

## Copyright Boundary

The full standard is a paid, licensed document. This project does not quote
it and has been built from the publicly available principle framework (ISO's
published abstract and scope, and the IPLF's freely published definition and
framework). This mirrors the approach of the companion skill
[asd-ste100-skill](https://github.com/danyuchn/asd-ste100-skill), which
encodes rule categories without reproducing ASD's licensed dictionary.

## Sources

- ISO 24495-1:2023 catalog page — https://www.iso.org/standard/78907.html
- ISO 24495-2:2025 (legal communication) — https://www.iso.org/standard/85774.html
- International Plain Language Federation, plain language definition —
  https://www.iplfederation.org/plain-language/
- IPLF, ISO standard overview — https://www.iplfederation.org/iso-standard/
- IPLF, national adoptions and translations —
  https://www.iplfederation.org/standard-translations/ (as of 2026-08:
  12 languages, no East Asian language among them)
- AccessibleEU summary —
  https://accessible-eu-centre.ec.europa.eu/content-corner/digital-library/iso-24495-12023-plain-language-part-1-governing-principles-and-guidelines_en
```

## File: examples/before-after-en.md
size: 2059
sha: 9a7f5632fff300c91b126f68cc32ad143bfe7f96
upstream: https://github.com/danyuchn/iso-24495-skill/blob/HEAD/examples/before-after-en.md

```text
# Before / After — English

Each pair names the principle that drove the rewrite.

## 1. Front-load the point (Findable)

**Before**
> In light of recent changes to our internal processes, and after careful
> consideration of the various options available to us, we have made the
> decision that, effective from the beginning of next month, the weekly
> status meeting will be moved from Monday morning to Wednesday afternoon.

**After**
> From next month, the weekly status meeting moves to Wednesday afternoon
> (was: Monday morning).

## 2. Actors and deadlines (Usable)

**Before**
> It is expected that the reimbursement form should be completed and
> submitted in a timely manner in order for processing to be initiated.

**After**
> Submit your reimbursement form by the 25th. We start processing it the
> day we receive it.

## 3. Nominalization and hedge stacks (Understandable)

**Before**
> The team will make a determination as to whether an implementation of the
> proposed solution may potentially be feasible in some circumstances.

**After**
> The team will decide whether the proposed solution is feasible.

Kept as-is: the decision itself is still open — "whether" carries that.

## 4. Cut what the reader does not need (Relevant)

**Before**
> Our company was founded in 2011 with a mission to revolutionize customer
> communication. We take every piece of feedback seriously and are committed
> to continuous improvement. Regarding your report: the sync error you saw
> is fixed in version 2.4.1.

**After**
> The sync error you reported is fixed in version 2.4.1. Update your app to
> get the fix.

## 5. One idea per sentence (Understandable)

**Before**
> If the export fails, which can happen when the file exceeds the size limit
> that was configured by your administrator, an error will be shown and the
> partial file that was created during the attempt will be removed.

**After**
> The export fails if the file exceeds your administrator's size limit.
> You get an error message. The tool deletes the partial file it created.
```

## File: examples/before-after-zh.md
size: 2033
sha: 10ad0477aa2339165c1f116f15a90638d804ee28
upstream: https://github.com/danyuchn/iso-24495-skill/blob/HEAD/examples/before-after-zh.md

```text
# 改寫前後對照——中文

每一組都標出主要動用的原則。

## 一、結論先行（找得到）

**改寫前**
> 鑑於近期內部作業流程有所調整，經多方評估與審慎考量後，本公司決定自下月
> 一日起，將原訂於每週一上午舉行之週會，調整至每週三下午辦理，尚祈配合。

**改寫後**
> 下個月起，週會改到週三下午開（原本是週一上午）。

## 二、動作者與期限（用得上）

**改寫前**
> 相關費用之核銷單據應儘速填妥並繳交，俾利後續作業之進行。

**改寫後**
> 請在每月 25 日前把核銷單交給財務部的王小姐。我們收到當天就開始處理。

## 三、去公文腔與墊字（看得懂）

**改寫前**
> 本案將由專案小組針對所提方案之可行性進行評估，並加以研議後做成決定。

**改寫後**
> 專案小組會評估這個方案可不可行，然後做決定。

## 四、刪讀者不需要的內容（相關）

**改寫前**
> 本公司自創立以來，始終秉持顧客至上之精神，致力於提供最優質之服務。
> 有關您日前反映之同步錯誤問題，該問題已於 2.4.1 版修復。

**改寫後**
> 你回報的同步錯誤已經在 2.4.1 版修好了。把程式更新到這個版本就行。

## 五、中英夾雜與術語（看得懂）

**改寫前**
> 請先 review 這份 proposal 的 scope，確認 stakeholder 的 alignment 沒問題
> 之後，我們再 kick off 這個 project。

**改寫後**
> 請先看過這份提案的範圍，確認相關的人都同意了，我們再開始做。

## 六、歐化長句拆解（看得懂）

**改寫前**
> 作為一個以提升使用者體驗為核心目標的、由多個跨部門成員所組成的團隊，
> 我們對於任何可能影響到產品穩定性的變更都會採取相對保守的態度。

**改寫後**
> 我們是跨部門團隊，目標是把使用者體驗做好。所以只要變更可能影響產品
> 穩定，我們就會保守處理。
```

## File: LICENSE
size: 1075
sha: cf3b9052d36f05227a3e3c364910b9f96c86cc5f
upstream: https://github.com/danyuchn/iso-24495-skill/blob/HEAD/LICENSE

```text
MIT License

Copyright (c) 2026 Dustin Yuchen Teng

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
```
