Trợ lý Project Manager toàn diện, tích hợp Jira & Confluence qua Atlassian MCP. Gồm 3 nhóm chức năng: [Lập kế hoạch & Tài liệu] Sprint Planning (capacity, Sprint Goal) — Roadmap (quý/năm, milestone) — PRD (goals, scope, requirements) — User Story (chuẩn INVEST, tạo Jira issue) — Meeting Notes (action items, push Jira task) — Risk Register (nhận diện, đánh giá, ứng phó) — Resource Planning (phân bổ, over-allocation) — Cost Management (ngân sách, CPI/SPI) — Timeline (milestone, critical path). [Giám sát & Cảnh báo] Sprint Health Check (6 chỉ số 🟢🟡🔴) — Daily Health Check (báo cáo standup tự động) — Cảnh báo quá hạn (theo mức nghiêm trọng) — Cảnh báo thiếu thông tin (completeness score). [Agile / Scrum / XP] Scrum Ceremonies (Planning, Daily, Review, Retro 4 formats, Grooming) — Estimation (Planning Poker, T-Shirt, MoSCoW, WSJF) — XP (TDD, Pair Programming, Simple Design) — Kanban (WIP, cycle time, bottleneck) — Anti-pattern detection — Tạo slide từ Confluence thành file .pptx.
Angular 17+ development guide covering Standalone Components, Signals-based state, NgRx, RxJS patterns, and integration with .NET/C# backends. Use when user asks to "create Angular component", "implement signal store", "setup NgRx", "write Angular service", "call .NET API from Angular", "handle HTTP in Angular", "fix RxJS subscription leak", "create Angular feature module", "implement lazy routing", "setup interceptor", or needs Angular architecture advice. Always use this skill for any Angular coding task, even if the user doesn't say "Angular" explicitly but the context is clearly frontend + .NET backend integration.
BDD test quality analyzer - detects flaky patterns, coverage gaps, and maintainability issues in Playwright-BDD/Cucumber tests
Generate Playwright E2E test step definitions from Cucumber feature files. Use when user provides a .feature file and wants to implement step definitions, create Page Object classes, or generate test code. Triggers include requests to implement steps, generate E2E tests from Gherkin scenarios, create POM classes for pages, or convert feature files to Playwright tests. Supports interactive selector discovery via Playwright MCP tools or manual user input.
Angular TDD workflow with codebase exploration and Figma design integration. Guides the Explore-Plan-Test-Implement-Refactor-Review cycle for Angular applications. Use when implementing Angular features test-first, "TDD", "Red-Green-Refactor", developing UI components from Figma designs, or when user says "write tests first". Do NOT use for Angular architecture setup (use angular-hexagonal), BDD/Gherkin scenarios (use bdd-practices), or E2E tests (use playwright-* skills).
Systematic code review for quality, correctness, and maintainability. Use when reviewing pull requests, code changes, diffs, or when asked to review/critique code. Also use when user says review this, check my code, any issues with this, PR review, code review, or provides code and asks for feedback. Covers functionality, architecture, performance, security, testing, and documentation with structured feedback using priority prefixes BLOCKING, SUGGESTION, QUESTION, NIT. Do NOT use when user wants to write new code from scratch or needs help debugging runtime errors.
Conventional Commits 1.0.0 format for consistent, parseable git commit messages. Use when committing changes, writing commit messages, or when the user mentions commit, save, git commit, or wants to persist work. Covers type selection, scope rules, description format, breaking changes, and multi-line commit workflow.
Angular 17+ component patterns with signal-based I/O, OnPush change detection, native control flow (@if/@for/@switch), and inject() function. Use when creating, modifying, or reviewing Angular components. ALWAYS use when writing .component.ts files, editing @Component decorators, or configuring component imports.