القائمة
Use for QA evidence, release readiness, rollback review, and close-out decisions.
التثبيت باستخدام 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 build completion evidence, code review readiness, and ready-for-QA checks.
Use for delivery planning, handoff, task source of truth, and engineering sequencing.
| name | pmo-quality-release |
| description | Use for QA evidence, release readiness, rollback review, and close-out decisions. |
Verify release readiness, QA evidence, rollback planning, blocker status, and human release approval.
Use for QA review, UAT/release gate, rollback review, or close-out summary.
PROJECT.md, configured task source of truth, release notes if present, and any conditional artifacts required by pmo-config/context-map.json and pmo-config/artifact-policy.json.
Use QA/release context only. Read source docs only when evidence conflicts with requirements.
Use pmo-config/artifact-policy.json for mode/gate artifact requirements and pmo-config/policy.json for approval gates and roles. Lite release requires PROJECT.md and DELIVERY.md (a prose "work item" mention is not parseable evidence); RELEASE.md stays optional unless the configured artifact policy or a real release/UAT trigger requires it. Never auto-create RTM.json or RELEASE.md for Lite without a trigger.
RELEASE.md exists.Return pass/fail summary, open blockers, release approval status, rollback status, and next action.
AI must not approve production release, mark Release Approved for a human, deploy, tag, or push. Human Release Approved evidence is mandatory when required by the configured gate policy.
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/validate-project.ps1 -ProjectPath <project> -Mode <mode> -Gate Release
Do not release with missing human approval, unresolved blockers, missing configured guardrails, unverified rollback, or Lite artifacts created only to satisfy a hardcoded checklist.
Release gate passes with zero failures and required human approval evidence is present.