PDCA / CAPD Compass Card

PDCA / CAPD Compass Card

Use this skill to transform a problem into a Chinese text diagram shaped like a compass: North, East, South, West, four diagonal arrows, and a center ◎ core. The output should feel like a fixed-width visual card, not a prose explanation.

Core Rules

• Use a fenced text code block for the final diagram.
• Prefer Chinese labels and short phrases.
• Use full-width spaces 　 for large horizontal alignment and half-width spaces only for small adjustments.
• Keep the center phrase at 8 Chinese characters or fewer, prefixed with ◎.
• Keep each outer compass phrase at 8 Chinese characters or fewer when the user requests strict eight-character limits.
• Make the diagram readable in a monospaced environment such as Discord, Hermes, terminal, or Markdown preview.
• Avoid over-explaining inside the diagram. Let placement, arrows, and labels carry the structure.

Compass Mapping

• North 北: 【Ｐ｜Plan 計畫】 for goals, options, choices, hypotheses, and intended destination.
• East 東: 【Ｄ｜Do 執行】 for concrete measures, steps,现场 action, and use of methods.
• South 南: 【Ｃ｜Check 檢查】 for facts, results, confirmation, and next-cycle evidence.
• West 西: 【Ａ｜Action 改善】 for cause discovery, root-cause pursuit, correction, and institutional repair.
• Center 中: 【◎核心】 for the problem essence, incident, contradiction, or decision point.

For CAPD, the cycle begins at Check:

• Check -> Action -> Plan -> Do -> Check
• Use CAPD when the task starts from現況認識, incident confirmation, observation, or evidence.

For PDCA, the cycle begins at Plan:

• Plan -> Do -> Check -> Action -> Plan
• Use PDCA when the task starts from a goal, plan, proposal, or project improvement loop.

Arrow Rules

Use 45-degree Unicode arrows at the four corners:

• ↗ means Action -> Plan: root causes become better plans.
• ↘ means Plan -> Do: plans become concrete execution.
• ↙ means Do -> Check: execution produces results to inspect.
• ↖ means Check -> Action: inspection returns to root-cause improvement.