Menu
Use when turning source material into scoped, source-referenced PMO requirements and intake decisions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-intake |
| description | Use when turning source material into scoped, source-referenced PMO requirements and intake decisions. |
Convert source material into confirmed requirements, assumptions, questions, scope, and mode recommendations.
Use for new source review, requirement extraction, gap analysis, scope clarification, or source conflict triage.
PROJECT.md, relevant source/**, and any user-stated goal. Read only the context set allowed by CONTEXT-ROUTER.md and pmo-config/context-map.json.
Default to PROJECT.md plus the specific source files needed. Do not bulk-load archived skills or every source file unless the task is an impact analysis or conflict review.
Use the mode, strict-trigger, evidence-status, and approval enums from pmo-config/policy.json; do not repeat or extend them inside the skill. Lite captures only essential source, scope, and release approval needs. Standard captures normal requirements and design implications. Strict escalation follows the configured strict triggers.
source_ref.Return confirmed requirements, assumptions, open questions, source references, confidence notes, and mode recommendation.
Scope approval is human-owned. AI may draft rows but must not mark approval as granted without explicit source evidence.
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/validate-project.ps1 -ProjectPath <project> -Mode <mode> -Gate Scope
Do not invent requirements, bulk-load all source by default, silently resolve conflicts, push commits, deploy, or approve release.
Every in-scope requirement has source_ref, evidence status, and either confirmed acceptance or an open question.