payment-integration
Enterprise payment processing with Stripe, PayPal, and LemonSqueezy including subscriptions, webhooks, and PCI compliance
Enterprise payment processing with Stripe, PayPal, and LemonSqueezy including subscriptions, webhooks, and PCI compliance
Validates JIRA tickets have required fields and sufficient information for development. Activates when users ask about ticket quality, readiness, or completeness, or when reviewing tickets before sprint planning.
研究專案的建立、切換、設定管理。 LOAD THIS SKILL WHEN: 新專案、切換專案、專案設定、paper type、start exploration、convert exploration CAPABILITIES: create_project, list_projects, switch_project, get_current_project, setup_project_interactive, start_exploration, convert_exploration_to_project
Plan implementation skill. Executes approved technical plans phase by phase with verification checkpoints.
Use when an agent needs to write user stories for a project
Faster on-call handoffs and better postmortems with triage SOPs
Create well-structured user stories with clear acceptance criteria in 'As a/I want/So that' format for team communication
Use when creating implementation plans to generate properly structured plans with phases, success criteria, and project references.
This skill should be used when creating or updating PROJECT.md files, planning sprints, defining project goals, or managing project scope. It provides templates and best practices for PROJECT.md-first development.
This skill should be used when the user asks to "document discussion", "save meeting notes", "record conversation", "capture meeting", or mentions needing to document team discussions with participants, decisions, and action items.
Use when starting any feature, project, or design work. Guides collaborative design refinement through incremental questioning before any code is written.
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
Structured retrospective for incidents and mistakes. Transforms problems into systematic improvements.
Break down GitHub issues into official GitHub sub-issues by parsing task lists from parent issue descriptions. Use this skill when a user wants to convert a parent issue with tasks into linked sub-issues, when managing complex features that need hierarchical breakdown. Accepts issue number as parameter or prompts user if not provided.
撰写或更新 Project Guardrails/工程规范(前端/后端/API/数据/安全/运维/发布)。用于新项目启动、技术栈变更、多团队协作、事故复盘或持续漂移出现时建立统一约束与最低标准。
Create detailed implementation plans before coding (saves tokens later)
Guidelines for writing effective user stories with clear acceptance criteria. Use when creating issues from discovery findings.
This skill should be used when the user asks to "analyze slide quality", "review slide", "check slide design", "optimize slide", "improve slide content", "assess slide clarity", or needs evidence-based quality evaluation using the 12-point checklist for presentation slides.
Read project session context from .sessions/index.md to understand ongoing work, previous decisions, blockers, and history. Use when the user asks about project context, previous sessions, what was worked on before, architectural decisions, blockers, or when they reference "last time", "previously", "the session", or "what we decided".
Discovery questions, checklists, and techniques for gathering requirements. Use during discovery to ensure thorough understanding before creating issues.
Auto-update status metrics across governance documents - scans MCP issues/specs to calculate current counts and percentages, updates README files and NEXT_STEPS with accurate data
Fetch unresolved PR review comments from GitHub. Use when working with pull request reviews, addressing review feedback, or checking outstanding review comments on a PR. Triggers on requests like "get PR reviews", "fetch review comments", "show unresolved comments", or "what feedback is pending on this PR".