আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
This skill MUST be used when the user asks to "create sprint", "start sprint", "end sprint", "complete sprint", "close sprint", "new sprint", "begin sprint", "finish sprint", "update sprint", "rename sprint", or otherwise wants to create or change sprint state/details.
OpenSpec駆動の垂直TDDスケルトン戦略。提案作成・技術検証・設計・実装・アーカイブの全ライフサイクルをサポート。 使用タイミング: (1) OpenSpecスラッシュコマンド実行時（`OpenSpec: Propose`, `OpenSpec: Apply`, `OpenSpec: Archive`） (2) 新機能開発の開始時（「新機能を追加」「〜を実装」リクエスト、OpenSpec提案がまだ存在しない場合） (3) 提案の修正・継続（openspec/changes/配下にファイルが存在、「提案を修正」「設計を見直し」リクエスト） (4) 実装の再開（tasks.mdに未完了タスクがある、「実装を続ける」「次のステップ」リクエスト） (5) 技術検証が必要（design.md作成前、複数技術選択肢がある、「技術検証」「ライブラリ調査」リクエスト） 使用しない場合: バグ修正、タイポ修正、ドキュメント更新のみ、設定ファイル変更のみ
Manages Zoho Mail integrations, newsletter campaigns, and automated outreach. Use when handling email sending, subscriber lists, or newsletter logic.
Review and score engineering specs against a startup-focused quality rubric. Penalize over-engineering and reward simplicity.
CLI for managing the Cortex email automation pipeline. Use this skill when the user wants to query emails, check queue status, trigger backfills, view classifications, or manage the email triage system. Triggers on keywords like "cortex", "email pipeline", "queue status", "classification", "backfill", "triage".
This skill MUST be used instead of Atlassian MCP tools when the user asks to "get Jira issue", "fetch Jira ticket", "look up issue", "show me ticket", "what's the status of PROJ-123", "get issue details", "find Jira issue", or mentions a Jira issue key pattern like "PROJ-123", "ABC-456". ALWAYS use this skill for Jira issue retrieval - never use mcp__atlassian__getJiraIssue directly.
Creates ATS-optimized, personalized resumes tailored to specific job postings. Outputs both Markdown and PDF formats using StoryBrand framework.
Fetches calendar events from all accounts (M365 Prisma/Personal/Family/DataBusiness + Google) and populates schedule sections in daily briefing. Triggers on "Get my calendar events for today", "Populate the calendar sections", "Update calendars in briefing entry [id]". Called by briefing-generator after create-briefing-entry. Calculates meeting count and deep work hours. Transitions Phase from 1-Email to 2-Calendar.
Interactive callable tool that creates BMAD planning documents (requirements, architecture, epics) in main repository on contrib branch. Three-persona Q&A system generates comprehensive planning before feature development. Use when: On contrib branch, planning phase, need requirements/architecture Triggers: plan feature, requirements, architecture, BMAD
Converts a decision-complete PRD into a concise, roadmap-ready list of features with explicit dependencies and Markdown output including a Mermaid dependency diagram.
Find and safely claim the next Beads task with conflict checking. Use when looking for work, when finishing a task and need the next one, when the user mentions "next task" or "what should I work on", or when coordinating with other agents on task ownership.
Guide for creating sprint definitions in SPRINT.yaml. This skill should be used when users want to create sprint, new sprint planning, sprint definition best practices, or define steps for autonomous execution. Triggers on "create sprint", "new sprint", "sprint definition", "define steps".
Creates or updates pull requests by analyzing code changes, creating branches, committing, pushing, and managing PRs with the project template. Use when creating a new PR, updating an existing PR, opening a PR, editing PR details, or preparing code for review. (project)
Create comprehensive Product Requirements Documents (PRD) that define what to build and why, focusing on goals, scope, user stories, and success criteria without implementation details. Use this skill when: - User asks to "write a PRD", "create PRD", "write requirements document" - User mentions "requirements document", "product requirements", "product spec" - Running /pm.plan command to create version planning document - Starting a new product, major feature, or initiative that needs formal requirements - Need to document goals, scope, user stories, functional requirements, and success criteria Output: ALWAYS write PRD files to docs/reference/pm/versions/{version-name}.md
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.
Go language consultant providing guidance on best practices, testing with testify, concurrency patterns, error handling, and technology stack recommendations. Use when answering Go questions, reviewing Go code, or advising on Go implementation approaches.
Coordinates multi-component releases, feature flags, versioning, and rollback strategies. Trigger terms: release management, release planning, release coordination, feature flags, canary deployment, progressive rollout, release notes, rollback strategy, release train, deployment coordination, versioning, changelog, release approval, deployment checklist. Manages complex release workflows: - Multi-component release coordination - Feature flag strategy and management - Versioning and changelog generation - Canary and blue-green deployments - Progressive rollout strategies - Rollback procedures - Release approval workflows - Post-release verification Use when: planning releases, coordinating multi-service deployments, managing feature flags, or generating release notes.
Transform PRD or story into complete page/component designs with ASCII layouts, component specs, interaction flows, and frontend implementation prompts. Use this skill when: - User asks to "design the page", "design component", "create page design" - User mentions "page design", "component design", "UI design", "layout design" - Running /frontend.design command - PRD or story is ready and need visual/interaction design before implementation - Need to create design spec that frontend developer can implement from Prerequisites: Design system must exist at docs/reference/frontend/design-system.md Output: ALWAYS write design files to docs/reference/frontend/designs/{name}.md
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
