tlm-claude-plugins

BA/Product Owner ticket writer — turn a requirement or defect described in chat into ONE well-formed ClickUp ticket that follows the team's task/bug template. Fills the business sections (user story, description, reproduce steps, test scenarios); leaves the technical sections as headed placeholders for the developer. Never invents subtasks — the ticket it creates is the single source of truth. TRIGGER when the user describes a requirement, change request, or bug and asks to create/log a ticket — "tạo ticket", "tạo task trên ClickUp", "log bug", "viết ticket", "create a ticket for this", "raise a bug".

Generate a release/deployment checklist for any project. Compares the current branch against a chosen base, discovers all ticket IDs in scope, enriches each from the project's ticket-management tool (ClickUp / Jira / Linear / Azure DevOps / GitHub — resolved dynamically), reconciles against the deployment ticket's release notes, then lists the services to deploy and DB migrations to run based on code changes. TRIGGER whenever the user says "release check", "check release", "deployment check", "deployment checklist", "release checklist", "kiểm tra release", "check deploy", or asks to prepare/verify a release before deploying to production.

House conventions for ALL frontend work — Next.js (App Router or Page Router), React Native (Expo Router or CLI), and Next.js API route handlers with Prisma. Detects the project's stack, applies the shared _modules architecture, component hierarchy, Link-only navigation, function minimalism, Tailwind/StyleSheet styling, TypeScript and Zod/React-Hook-Form rules, then layers the stack-specific hard rules on top. Reads .claude/ecosystem-map.md before assuming any contract that lives in another repo of the system (backend API, shared package, web/mobile twin) instead of guessing it. Use whenever creating or editing a component, screen, page, layout, hook, API client, route handler, form, or navigation in any frontend project — including in app/, pages/, _layout.tsx, route.ts, 'use server' actions, expo-router imports, or useQuery hooks.

Build a screen or component from a Figma design — fetches the design via the Framelink Figma MCP, confirms what it sees, plans placement, then implements it in the project's actual stack (Next.js App/Page Router or React Native) following the house conventions, wiring real APIs from a curl command or scaffolding mock data when no API exists yet. TRIGGER when the user pastes a figma.com link, or says "build from figma", "implement this design", "vibe code", "code màn hình này từ figma", "làm UI từ design".

Build a release note for a MOBILE app build (React Native, Expo, or Flutter) from a range of git commits — reads the diffs for root cause, pulls the linked tickets for the user-reported symptoms, writes numbered plain-language items for testers and end users, collects the iOS/Android build numbers and install link, then posts it as a DRAFT to the release chat channel. Mobile only. TRIGGER when the user gives a commit hash or range and asks for release notes for a build, or says "release notes", "changelog", "what's new", "build notes", "summarize changes for testers", "tổng hợp changes", "tóm tắt thay đổi cho build", "note bản build".

When the user corrects code with a reason — "do it this way instead, because…", "don't use X, use Y", "sao lại viết vậy, phải làm thế này" — classify whether that feedback is a NEW house rule, a gap in the existing rules, a correction that contradicts a current rule, or a one-off, then ask whether to persist it before applying the change. Runs BEFORE the edit, so the rule and the code land together. TRIGGER on any corrective feedback about code style, structure, naming, or approach, and after implementing something the user then pushes back on.

Run a feature spec-first using OpenSpec — agree on the spec before writing code. Bootstraps OpenSpec into the repo (npx openspec init --tools claude), then drives its propose → apply → archive loop, enriching each change's design.md to map onto this plugin's _modules/ architecture and unifying the change id with the ticket tracker. TRIGGER when the user says "spec-driven", "openspec", "propose a change", "write a spec first", "spec trước khi code", "làm theo spec", "opsx", pastes an /opsx:* command, or asks to set up OpenSpec in a project. When the SessionStart hook detects an openspec/ directory, offer OpenSpec per ticket/feature — apply it only if the user agrees, otherwise run the normal rules skills — and announce each CLI command it triggers so the user stays aware.

Work a ticket end-to-end from any tracker (ClickUp, Jira, Linear, Azure DevOps, GitHub Issues) — fetch it, move it to in-progress, cut a branch, write a plan file, implement, then sync a non-technical summary back and move it to review. Optionally attaches QA evidence (screenshots, self-test videos). TRIGGER when the user gives a ticket id like TLM-1234 / ABC-567, pastes a ticket URL, or says "work on task", "pick up ticket", "start task", "làm task", "nhận task", "xử lý ticket".