Menu
Use to analyze the backlog, break down tasks from requirements, and automate Issue/Sprint management using gh CLI.
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
| name | product-manager |
| description | Use to analyze the backlog, break down tasks from requirements, and automate Issue/Sprint management using gh CLI. |
Acts as a PM assistant to the Indie Hacker to automate Agile workflows on GitHub.
docs/backend-business-logic-vi.md.internal/module/ implementation.Draft issues in Vietnamese as requested for clarity in the board:
Example Issue Title: [inventory] Triển khai quy tắc BR-K03 Bảo toàn diện tích
Example Issue Body:
## Tóm tắt
Hiện tại module Inventory chưa kiểm tra ràng buộc diện tích khi báo cáo kết quả cắt. Cần implement logic check BR-K03.
## Quy tắc nghiệp vụ (Business Rules)
- BR-K03: Tổng diện tích thành phẩm + diện tích tấm lẻ + diện tích phế liệu <= diện tích tấm gốc.
## Định nghĩa hoàn thành (DoD)
- [ ] Cập nhật service.go hàm RecordCut để kiểm tra tổng diện tích.
- [ ] Trả về lỗi ErrAreaConservation (422) nếu vi phạm.
- [ ] Thêm unit test cho trường hợp vi phạm diện tích.
When approved, use the tool:
gh issue create --title "[inventory] Triển khai quy tắc BR-K03 Bảo toàn diện tích" --body "..."
Agent Tip: Always check current gh issue list before proposing new tasks to avoid duplicates.
Use to verify if the code/logic aligns with the Vietnamese business spec. Mandatory cross-referencing with BR-* rules before implementation.
Use when the user asks to deploy, dockerize, set up CI/CD, configure environments, or prepare for go-live. Covers Docker Compose, GitHub Actions, health checks, environment configuration, database backup, and production readiness checklist. Trigger words: "deploy", "docker", "CI", "CD", "go live", "production", "staging", "health check", "backup", "monitoring".
Use to ensure alignment between Backend and Frontend, guarding the Modular Monolith and API contracts.
Use to analyze the backlog, break down tasks from requirements, and automate Issue/Sprint management using GitLab API.
Use to audit and enforce role-based access control (RBAC) across all API endpoints. Scans handler routes, maps required roles from the business spec, generates RequireRole middleware guards, and reports orphan (unprotected) endpoints. Trigger words: "rbac", "phân quyền", "role", "access control", "security audit", "guard endpoints", "protect routes".
Use when starting ANY non-trivial issue or feature on the Go backend — covers the full Senior Engineer workflow: requirements clarification -> technical design -> task breakdown -> implement + test -> self-QA -> PR. ALWAYS trigger this skill when the user says "implement", "add feature", "fix issue", "build", "create endpoint", or pastes a GitHub issue/ticket. Do NOT skip phases — especially Phase 5 (Self-QA) which is the most commonly forgotten step before submitting code.