القائمة
Use for flow, UX, wireframe, and design-ready acceptance criteria tied to scoped requirements.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Pre/Post execution validation + Phase Gate enforcement — ป้องกันการข้าม step, auto-validate output, ให้คะแนน quality score
สแกน code ใน Scaffold/ ด้วย 53 security rules (6 หมวด) — secrets, permissions, injection, AI-specific, config, dependencies — ก่อน deploy หรือหลัง Dev report
Coordinate PM/Dev/QA agents แบบ Pipeline Pattern — auto-route งานตาม role, ส่งต่ออัตโนมัติเมื่อ status เปลี่ยน, track progress ทุก handoff
Create color-coded teaching scripts / presenter talking-point documents (.md) that serve as a "live reading book" for speakers. The output is a markdown file where each color tells the presenter what to do: blue = speak this line, red = pronunciation guide, dark blue = slide header, black = stage direction & audience engagement, yellow box = terminology. Use this skill whenever the user mentions: teaching script, talking points, presenter script, key talking point, speaker notes, lecture script, training script, presentation script, สคริปต์การสอน, สคริปต์วิทยากร, คำพูดที่ต้องอ่าน, หนังสือสำหรับพูด, or any request to create a document that guides a speaker through a slide deck with exact words to say, pronunciation help, and stage directions. Also trigger when the user uploads a PowerPoint (.pptx) and asks to write a script, narration, or talking points for it.
Use for QA evidence, release readiness, rollback review, and close-out decisions.
Use for build completion evidence, code review readiness, and ready-for-QA checks.
| name | pmo-design |
| description | Use for flow, UX, wireframe, and design-ready acceptance criteria tied to scoped requirements. |
Turn scoped requirements into flow, wireframe, and design-ready decisions.
Use when UI, workflow, user journey, integration flow, or acceptance wording needs design clarification.
PROJECT.md, applicable DESIGN/**, requirements with source references, and the context/artifact contract in pmo-config/context-map.json and pmo-config/artifact-policy.json.
Read only requirement rows and design files relevant to the requested flow. Avoid loading delivery or release docs unless checking impact.
Use pmo-config/policy.json for mode, sentinel, evidence, and approval values, and pmo-config/artifact-policy.json for when design artifacts are required. Lite design is conditional and can use not_required only where the configured sentinel policy allows it. Standard and Strict design expectations follow the configured artifact and reference contracts.
DESIGN/FLOW.puml and DESIGN/WIREFRAME.md only when the configured artifact contract or confirmed design impact requires them.Return design files changed, requirement coverage, assumptions, and unresolved design questions.
Design Ready is human-owned and follows the configured artifact and approval contracts for the active mode and gate.
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/validate-project.ps1 -ProjectPath <project> -Mode <mode> -Gate Design
Do not expand scope, remove source references, hardcode artifact matrices, or mark design approval without human evidence.
Each design-affecting work item has a design reference or an intentional not_required sentinel where allowed.