원클릭으로 Manus에서 모든 스킬 실행

product-backlog-agent

Orchestrates the full Product Backlog → Sprint Planning → Dev Task Assignment pipeline. Use this skill whenever the user wants to: convert requirements into a product backlog, create user stories from a feature list, plan sprints and assign tasks to developers, break down a project into actionable dev work, or produce sprint planning documents. Triggers on phrases like "สร้าง backlog", "แตก user story", "วางแผน sprint", "จ่ายงาน dev", "product backlog", "sprint planning", "แตกงาน", or any request to turn requirements into structured development tasks. Always use this skill — not just docx/xlsx alone — when the goal is to produce a complete, multi-document dev planning package.

Manus에서 실행

개요

설치 명령

npx skills add https://github.com/ThanabordeeN/gemini-productivity-skills --skill product-backlog-agent

이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요

출처

ThanabordeeN/gemini-productivity-skills

스타0

포크0

업데이트2026년 3월 11일 08:58

파일 탐색기

3 개 파일

SKILL.md

readonly

name

product-backlog-agent

description

Product Backlog Agent

An orchestrator skill that transforms Requirements into a full dev-ready planning package by coordinating the xlsx and docx skills.

What This Skill Produces

Output	Skill Used	Description
`product-backlog.xlsx`	xlsx	Feature list with MoSCoW priority, Story Points, Status
`user-stories.docx`	docx	User Stories with Acceptance Criteria per Epic
`sprint-plan.xlsx`	xlsx	Sprint breakdown with Task → Assignee → Estimate

Step-by-Step Workflow

Step 0 — Understand the Input

Accept any of these input forms:

Free text in chat describing the product/features
Uploaded file (.docx, .pdf, .txt) containing requirements
Existing backlog the user wants to reformat or expand

If input is unclear, ask:

"ช่วยเล่าให้ฟังหน่อยได้ไหมว่าซอฟต์แวร์นี้ทำอะไร และกลุ่มเป้าหมายคือใคร?"

Step 1 — Extract & Structure Requirements

Parse the input and identify:

Epics (กลุ่มใหญ่ของ Feature เช่น Authentication, Dashboard, Payment)
Features (สิ่งที่ระบบต้องทำ)
Users / Roles (ใครใช้ระบบนี้)
Constraints (เวลา, เทคโนโลยี, ข้อจำกัด)

Structure internally as:

Epic → [Feature 1, Feature 2, ...]
Feature → [User Story 1, User Story 2, ...]
User Story → [Task 1, Task 2, ...]

Read reference file for templates: → references/story-format.md

Step 2 — Produce Product Backlog (xlsx)

Read /mnt/skills/public/xlsx/SKILL.md then create product-backlog.xlsx with:

Sheet 1: Backlog

Column	Content
ID	EPIC-001, FEAT-001
Epic	ชื่อ Epic
Feature / Story	ชื่อ Feature หรือ User Story
Type	Epic / Feature / Story / Bug
Priority	Must / Should / Could / Won't (MoSCoW)
Story Points	1, 2, 3, 5, 8, 13 (Fibonacci)
Status	Backlog / In Progress / Done
Sprint	Sprint 1 / Sprint 2 / ...
Assignee	ชื่อ Dev หรือ TBD
Notes	ข้อมูลเพิ่มเติม

Sheet 2: Epic Summary

Epic	# Stories	Total Points	Priority

Apply conditional formatting:

Must = แดง, Should = ส้ม, Could = เหลือง, Won't = เทา

Step 3 — Produce User Stories Document (docx)

Read /mnt/skills/public/docx/SKILL.md then create user-stories.docx with:

Structure per Epic:

# [Epic Name]
## Feature: [Feature Name]
### User Story [ID]: [Story Title]

**As a** [role]
**I want to** [action]
**So that** [benefit]

**Acceptance Criteria:**
- [ ] Given [context], When [action], Then [outcome]
- [ ] ...

**Story Points:** X
**Priority:** Must/Should/Could/Won't
**Dependencies:** [Story ID] or None

Read references/story-format.md for full template and examples.

Step 4 — Produce Sprint Plan (xlsx)

Read /mnt/skills/public/xlsx/SKILL.md then create sprint-plan.xlsx with:

Sheet per Sprint (Sprint 1, Sprint 2, ...):

Column	Content
Task ID	TSK-001
Story ID	Reference to backlog
Task Name	งานย่อยที่ต้องทำ
Type	Frontend / Backend / DB / DevOps / Design
Assignee	ชื่อ Dev หรือ TBD
Estimate (hrs)	จำนวนชั่วโมงประเมิน
Status	To Do / In Progress / Done / Blocked
Due Date	วันที่คาดว่าเสร็จ
Notes	ข้อมูลเพิ่มเติม

Sprint Summary Sheet:

Sprint	# Tasks	Total Hours	Start Date	End Date	Goal

Sprint sizing rule (default):

Sprint = 2 สัปดาห์
ไม่เกิน 40 Story Points ต่อ Sprint (ปรับได้ตามทีม)

Read references/sprint-rules.md for sizing guidelines.

Step 5 — Deliver All Files

After all three files are created, present them together and give a summary:

✅ สร้างเสร็จแล้ว 3 ไฟล์:

📊 product-backlog.xlsx  — X epics, Y stories, Z total points
📝 user-stories.docx    — X user stories พร้อม acceptance criteria
📅 sprint-plan.xlsx     — X sprints, Y tasks, พร้อม assign

Sprint 1 Focus: [สรุปเป้าหมาย Sprint แรก]

Handling Special Cases

ถ้า Input เป็นไฟล์ Requirements: → อ่านไฟล์ก่อน แล้ว Extract Epics/Features ใน Step 1

ถ้าไม่มีรายชื่อ Dev: → ใช้ "Dev 1", "Dev 2" หรือ "TBD" ใน Assignee column แจ้งผู้ใช้ให้เติมเอง

ถ้ามีแค่ Feature list สั้น ๆ (< 5 items): → ถามว่า "มี Feature อื่นอีกไหม?" ก่อนดำเนินการ

ถ้าผู้ใช้ต้องการเฉพาะบางไฟล์: → ผลิตแค่ไฟล์ที่ขอ ไม่ต้องทำครบทั้ง 3

Reference Files

references/story-format.md — Template และตัวอย่าง User Story แบบสมบูรณ์
references/sprint-rules.md — กฎการแบ่ง Sprint, Story Point guidelines, Velocity คำนวณอย่างไร

이 저장소의 다른 Skills

같은 저장소

siyuan-second-memory

ThanabordeeN/gemini-productivity-skills

Use SiYuan Note as a personal second memory and Knowledge Graph. Triggered when the user wants to remember, recall, link, organize, or reason over personal knowledge — including saving insights, creating concept maps, building topic clusters, logging decisions, and retrieving past context. This skill enforces three hard connection rules: every new document must link to at least one existing document (Mandatory Link Prompt), every outgoing link must create a matching backlink on the target (Backlink Enforcement), and orphan documents are tracked in a weekly review queue. Use it when the user says: 'remember this', 'save this idea', 'what do I know about X', 'link this to Y', 'build a concept map', 'add to my second brain', 'log this decision', 'what have I noted about Z', 'review my notes'.

2026-04-110

frontend-design

ThanabordeeN/gemini-productivity-skills

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

2026-03-120

discovery-agent

ThanabordeeN/gemini-productivity-skills

Orchestrates the complete Phase 1: Product Discovery & Analysis pipeline — from raw idea to a structured, dev-ready handoff package. Use this skill whenever the user wants to: explore a product idea, analyze a problem space, gather and structure requirements, define project scope, create feasibility studies, produce BRD/PRD documents, analyze competitors, define MVPs, or prepare any discovery deliverables before development begins. Also triggers on: "วิเคราะห์โปรเจกต์", "สำรวจความต้องการ", "เขียน requirements", "ทำ discovery", "วิเคราะห์ปัญหา", "กำหนด scope", "เตรียมงานให้ dev", "ทำ BRD", "ทำ PRD", "วิเคราะห์ตลาด", "หา MVP", "product discovery", "requirements gathering". ALWAYS use this skill — not just docx/xlsx alone — when the goal is to go from a product idea or problem statement all the way to a structured dev-ready package.

2026-03-110

estimation-agent

ThanabordeeN/gemini-productivity-skills

Produces detailed Cost Estimation and Man Hours breakdown for software projects. Use this skill whenever the user wants to: estimate development cost, calculate man-hours per feature or sprint, produce a project budget, compare team configurations, create cost proposals for clients, or get ROI analysis. Triggers on: "ประเมิน cost", "คำนวณ man hours", "งบประมาณโปรเจกต์", "ค่าใช้จ่ายพัฒนา", "ราคาโปรเจกต์", "estimate", "how much will this cost", "how long will this take", "project budget", "cost breakdown", "resource planning", "เตรียม proposal ราคา". ALWAYS use this skill — not just xlsx/docx alone — when the goal is a complete, justified cost and timeline estimate for a software project.

2026-03-110

pptx

ThanabordeeN/gemini-productivity-skills

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

2026-03-110

document-generator

ThanabordeeN/gemini-productivity-skills

Generate professional business documents (.docx) in Thai with TH Sarabun New font. Supports Quotations, Invoices, Billing Notes, Receipts, and Purchase Orders (PO). Use this skill whenever the user asks to create any of these business documents. It reads details from a JSON file and outputs a cleanly formatted docx.

2026-03-090

출처

ThanabordeeN

ThanabordeeN/gemini-productivity-skills

GitHub 저장소 열기 Creator 저장소 보기

설치 명령

다운로드

Manus에서 실행

유용한 대상SOC

프로젝트 관리 전문가비즈니스 및 금융 운영직13-1082L4

name

product-backlog-agent

description

Product Backlog Agent

An orchestrator skill that transforms Requirements into a full dev-ready planning package by coordinating the xlsx and docx skills.

What This Skill Produces

Output	Skill Used	Description
`product-backlog.xlsx`	xlsx	Feature list with MoSCoW priority, Story Points, Status
`user-stories.docx`	docx	User Stories with Acceptance Criteria per Epic
`sprint-plan.xlsx`	xlsx	Sprint breakdown with Task → Assignee → Estimate

Step-by-Step Workflow

Step 0 — Understand the Input

Accept any of these input forms:

Free text in chat describing the product/features
Uploaded file (.docx, .pdf, .txt) containing requirements
Existing backlog the user wants to reformat or expand

If input is unclear, ask:

"ช่วยเล่าให้ฟังหน่อยได้ไหมว่าซอฟต์แวร์นี้ทำอะไร และกลุ่มเป้าหมายคือใคร?"

Step 1 — Extract & Structure Requirements

Parse the input and identify:

Epics (กลุ่มใหญ่ของ Feature เช่น Authentication, Dashboard, Payment)
Features (สิ่งที่ระบบต้องทำ)
Users / Roles (ใครใช้ระบบนี้)
Constraints (เวลา, เทคโนโลยี, ข้อจำกัด)

Structure internally as:

Epic → [Feature 1, Feature 2, ...]
Feature → [User Story 1, User Story 2, ...]
User Story → [Task 1, Task 2, ...]

Read reference file for templates: → references/story-format.md

Step 2 — Produce Product Backlog (xlsx)

Read /mnt/skills/public/xlsx/SKILL.md then create product-backlog.xlsx with:

Sheet 1: Backlog

Column	Content
ID	EPIC-001, FEAT-001
Epic	ชื่อ Epic
Feature / Story	ชื่อ Feature หรือ User Story
Type	Epic / Feature / Story / Bug
Priority	Must / Should / Could / Won't (MoSCoW)
Story Points	1, 2, 3, 5, 8, 13 (Fibonacci)
Status	Backlog / In Progress / Done
Sprint	Sprint 1 / Sprint 2 / ...
Assignee	ชื่อ Dev หรือ TBD
Notes	ข้อมูลเพิ่มเติม

Sheet 2: Epic Summary

Epic	# Stories	Total Points	Priority

Apply conditional formatting:

Must = แดง, Should = ส้ม, Could = เหลือง, Won't = เทา

Step 3 — Produce User Stories Document (docx)

Read /mnt/skills/public/docx/SKILL.md then create user-stories.docx with:

Structure per Epic:

# [Epic Name]
## Feature: [Feature Name]
### User Story [ID]: [Story Title]

**As a** [role]
**I want to** [action]
**So that** [benefit]

**Acceptance Criteria:**
- [ ] Given [context], When [action], Then [outcome]
- [ ] ...

**Story Points:** X
**Priority:** Must/Should/Could/Won't
**Dependencies:** [Story ID] or None

Read references/story-format.md for full template and examples.

Step 4 — Produce Sprint Plan (xlsx)

Read /mnt/skills/public/xlsx/SKILL.md then create sprint-plan.xlsx with:

Sheet per Sprint (Sprint 1, Sprint 2, ...):

Column	Content
Task ID	TSK-001
Story ID	Reference to backlog
Task Name	งานย่อยที่ต้องทำ
Type	Frontend / Backend / DB / DevOps / Design
Assignee	ชื่อ Dev หรือ TBD
Estimate (hrs)	จำนวนชั่วโมงประเมิน
Status	To Do / In Progress / Done / Blocked
Due Date	วันที่คาดว่าเสร็จ
Notes	ข้อมูลเพิ่มเติม

Sprint Summary Sheet:

Sprint	# Tasks	Total Hours	Start Date	End Date	Goal

Sprint sizing rule (default):

Sprint = 2 สัปดาห์
ไม่เกิน 40 Story Points ต่อ Sprint (ปรับได้ตามทีม)

Read references/sprint-rules.md for sizing guidelines.

Step 5 — Deliver All Files

After all three files are created, present them together and give a summary:

✅ สร้างเสร็จแล้ว 3 ไฟล์:

📊 product-backlog.xlsx  — X epics, Y stories, Z total points
📝 user-stories.docx    — X user stories พร้อม acceptance criteria
📅 sprint-plan.xlsx     — X sprints, Y tasks, พร้อม assign

Sprint 1 Focus: [สรุปเป้าหมาย Sprint แรก]

Handling Special Cases

ถ้า Input เป็นไฟล์ Requirements: → อ่านไฟล์ก่อน แล้ว Extract Epics/Features ใน Step 1

ถ้าไม่มีรายชื่อ Dev: → ใช้ "Dev 1", "Dev 2" หรือ "TBD" ใน Assignee column แจ้งผู้ใช้ให้เติมเอง

ถ้ามีแค่ Feature list สั้น ๆ (< 5 items): → ถามว่า "มี Feature อื่นอีกไหม?" ก่อนดำเนินการ

ถ้าผู้ใช้ต้องการเฉพาะบางไฟล์: → ผลิตแค่ไฟล์ที่ขอ ไม่ต้องทำครบทั้ง 3

Reference Files

references/story-format.md — Template และตัวอย่าง User Story แบบสมบูรณ์
references/sprint-rules.md — กฎการแบ่ง Sprint, Story Point guidelines, Velocity คำนวณอย่างไร