본문으로 건너뛰기
cccskills
무료GitHub에 공개

pdca

Create Chinese monospaced compass-style PDCA or CAPD problem-solving cards using East-West-South-North-Center layout, full-width and half-width spaces, diagonal Unicode arrows, and strict Chinese character limits. Use when Codex needs to turn a problem, incident, decision tradeoff, root-cause analysis, improvement cycle, or CAPD/PDCA workflow into a square text diagram, Hermes/Discord-ready card, or Chinese 方位九宮圖 with center ◎, north Plan, east Do, south Check, west Action, and four diagonal transition arrows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구Discord
설치 방법 보기

포함된 파일(2)

  • SKILL.md6.5 KB
  • agents/openai.yaml266 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 北: 【P|Plan 計畫】 for goals, options, choices, hypotheses, and intended destination.
  • East 東: 【D|Do 執行】 for concrete measures, steps,现场 action, and use of methods.
  • South 南: 【C|Check 檢查】 for facts, results, confirmation, and next-cycle evidence.
  • West 西: 【A|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.

Place arrows between the compass quadrants with enough full-width spacing to preserve the visual loop.

Output Template

Adapt this template. Keep line lengths visually balanced rather than mathematically perfect.

               北
           【P|Plan 計畫】
           方案一:____
           方案二:____
           選 擇:____


       ↗                 ↘
  西【A|Action】     中【◎核心】     東【D|Do】
   原因發現        ◎____      手段活用
   ────────    ────────   ────────
   ____        ____       ____
   ____        ____       ____
   ____        ____       ____


       ↖                 ↙
           【C|Check 檢查】
           事 實:____
           結 果:____
           下一輪:____
               南

Construction Workflow

  1. Extract the center problem as a phrase of 8 Chinese characters or fewer.
  2. Decide whether the loop is CAPD or PDCA from the user's starting point.
  3. Fill the four directions:
    • Plan: options, desired end state, chosen principle.
    • Do: immediate measures and executable steps.
    • Check: confirmed facts, result state, what to inspect next.
    • Action: causes, failures, root-cause questions, recurrence prevention.
  4. Compress each phrase until it fits the requested width.
  5. Render a single text code block with full-width spacing and arrows.
  6. If helpful, add a brief note after the diagram listing the cycle order and any assumptions.

Phrase Compression

When content is too long, compress meaning before widening the diagram:

  • 老虎已經逃出籠子 -> 老虎逃走
  • 人命安全與動物保護之間的取捨 -> 人獸取捨
  • 封鎖現場並避免民眾靠近 -> 封鎖現場
  • 防止同類事件再次發生 -> 防止再發

Prefer four-character and six-character Chinese compounds when possible. Use eight characters only when needed.

Example

               北
           【P|Plan 計畫】
           方案A:人命尊重
           方案B:動物愛護
           選 擇:先保人命


       ↗                 ↘
  西【A|Action】     中【◎核心】     東【D|Do】
   原因發現        ◎老虎逃走      手段活用
   ────────    ────────   ────────
   管理失誤        人獸危險       封鎖現場
   機制失效        取捨判斷       搜尋活捉
   根因追究        安全優先       必要處置


       ↖                 ↙
           【C|Check 檢查】
           事 實:老虎逃出
           結 果:安全控制
           下一輪:防止再發
               南

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use A4 Eight Page Booklet 2.2 to create, write, repair, impose, and validate a printable A4 one-sheet eight-page mini book or zine from text, notes, images, BIRD Graph JSON, iMandalArt/九宮, FIRE, outlines, templates, or PDFs. Use whenever the user says A4八頁小書, 八頁小書, 八頁小冊, 八格小書, A4一張八頁, 八頁在一頁, 8頁在一頁, 八張一頁, 一張紙變八頁, 摺頁書, 折頁小書, 迷你書, 小誌, zine, mini zine, booklet, 做成小書, 印成小書, 單張印出八頁, 幫我拼版, 八頁PDF, 合併八頁, 6-7-8-1/5-4-3-2排列, or asks for eight upright page PDFs, an eight-page reading PDF, an editable DOCX, or a correctly rotated A4 landscape print sheet.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

twhsi/skills2592026년 7월 22일 업데이트

Assign, validate, normalize, and explain Luhmann/Zettelkasten-style project-note codes for Chinese book manuscripts, Obsidian Markdown folders, Mandala-Grid section files, HyperCard Markdown stacks, and project-note JSON to EPUB workflows. Use when Codex needs to scan folders for 部/章/節/項/目 numbering, generate stable card ids, insert branch codes without renumbering existing notes, map letter-coded branches to Obsidian Mandala sections, preserve K### keyword index cards, sanitize private catalogs into public examples, or prepare card IDs for EPUB and HyperCard output.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

twhsi/skills2592026년 7월 22일 업데이트

Create companion Codex workflows from book chapters, reader exercises, prompts, field notes, and teaching material. Use when Codex needs to turn a chapter excerpt, 書籍練習, AI 提示詞, worksheet, or author note into a reusable Skill-style workflow, GitHub-shareable companion artifact, or book link resource for readers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

twhsi/skills2592026년 7월 22일 업데이트

Compress answers to the highest practical information density with minimal wording while preserving essential meaning. Use when the user asks for 言簡意賅, 講重點, Concise, 精簡回答, 簡潔回答, 只講重點, 直接回答, brief, TL;DR, or otherwise requests a concise key-points response.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

twhsi/skills2592026년 7월 22일 업데이트

Convert EPUB card books into Obsidian-ready HyperCard Markdown folders and portable zip files. Use when Codex needs to turn an EPUB with XHTML chapters, table-of-contents cards, keyword index cards, backlinks, Luhmann/Zettelkasten numbers, or cross-links into one Markdown file per card with verified relative links, keyword cards, previous/home/next navigation, and GitHub/shareable zip output.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

twhsi/skills2592026년 7월 22일 업데이트

Create Fantastical calendar events and reminders from Codex on macOS. Use when the user asks Codex to add, schedule, parse, preview, or send a meeting, appointment, task, reminder, time block, daily plan item, 行事曆, 日曆, 會議, 待辦, or 提醒 into Fantastical.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

twhsi/skills2592026년 7월 22일 업데이트

twhsi의 스킬 모두 보기

이 스킬의 문제 신고