task-breakdownlisted

# PMO Skill: Task Breakdown > **Related Skills:** > - Load `pmo-workflow-architect` ก่อน ถ้าต้องการ map flow ก่อนแตก task > - Load `references/gantt-plantuml.md` for PlantUML Gantt syntax > - Load `references/gantt-mermaid.md` for Mermaid Gantt syntax (Lark Docs) > - Load `references/realistic-scope-guide.md` สำหรับแนวทางตั้ง scope สมจริง + acceptance criteria --- ## Purpose Task Breakdown is used for: - **Discussing with client and PM** about timeline overview - **Track progress** at high-level (no sub-task detail needed) - **Copy to Lark Docs** as native table or Markdown > **Lark Docs note:** Lark Docs **does not support** Markdown table syntax (`| col |`) - pasted Markdown tables show as plain text. Use `/table` or `+` icon to insert tables instead. We keep Task Breakdown as `.md` in repo for source of truth and version control. --- ## Pre-requisite: Ask Timeline First (MANDATORY) **Before creating Task Breakdown, must ask user:** - **Timeline scope** - how long total? (e.g., 3 months, 6 months, 1 year) - **Start date** - when does project start? (or planned start date) - **Milestone / Deadline** - any key deadlines? (e.g., UAT must complete by date X) - **Phases** - already divided? (e.g., Phase 1 = Core features, Phase 2 = Nice-to-have) --- ## Markdown Table Template ```markdown # Task Breakdown: {Project Name} > **Timeline:** {Start} - {End} ({N} weeks) > **Ref:** MOM#X, MOM#Y | # | Phase / Task | Duration | Start | End | Owner | Status | |---|------------