Menü
Use for build completion evidence, code review readiness, and ready-for-QA checks.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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 delivery planning, handoff, task source of truth, and engineering sequencing.
| name | pmo-build-review |
| description | Use for build completion evidence, code review readiness, and ready-for-QA checks. |
Confirm that implementation evidence is ready for review or QA.
Use after build work, before review/test, or when checking a PR or patch against requirements.
Task source of truth, changed-file summary, relevant requirement/design references, test evidence, and configured contracts from pmo-config/context-map.json, pmo-config/policy.json, and pmo-config/reference-types.json.
Read only work items and code/design artifacts relevant to the change. Use source docs only for disputed requirements.
Use pmo-config/policy.json for valid statuses, review stages, evidence statuses, and strict triggers. Use pmo-config/reference-types.json for reference shape; do not accept free-text evidence where a configured reference is required.
Return review findings, missing tests, risk flags, and ready/not-ready status.
AI can recommend ready-for-review but cannot approve production release.
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/validate-project.ps1 -ProjectPath <project> -Mode <mode> -Gate Design
Do not hide failing checks, skip risk escalation, hardcode release requirements, or mutate git state without human approval.
Work items are traceable, review stage is valid, and unresolved issues are documented.
