Use when Codex should coordinate software project work through a virtual high-standard product and engineering team, including PM, product manager, UI designer, art director, architect, frontend engineer, backend engineer, algorithm engineer, QA engineer, and DevOps engineer. Applies to new projects, existing codebase…
A structured review process used when closing an episode of work. It covers decisions about feedback, routing, promotion of findings into lasting records, and the final status.
A business-analysis assistant that helps turn proposed product changes into clear requirements and plans. It uses visual requirement analysis and supports Chinese-language requests.
Syncs AI agent work with the CodeBoard dashboard via HTTP API (sessionstart, tasklist, taskstart/complete, sessioncomplete, memory sync). Use when working in this repository, when .dashboard/project.yaml exists, or when the user mentions CodeBoard, 看板, session sync, or task reporting.
Bootstrap a repository-level "super harness" for long-running agent and human collaboration, so durable team knowledge, experiment progress, and verification evidence live in the repo rather than individual chat history. Use when initializing or normalizing the harness structure in a new or messy repository…
A same-day summary of coding-agent work, organized by project or repository rather than by time. It combines session records with plans, completed work, commits, and uncommitted changes.
Plan a sprint end-to-end by aligning scope, writing PRDs, creating GitHub issues, and breaking them into tasks. Orchestrates grill-me, prd, to-issue, and to-task skills. Use when planning a sprint, sprint planning, committing work for an iteration, or preparing a milestone in GitHub.
Use when the user asks to manage Azure Boards work items with Azure CLI (az boards), including creating, updating, deleting, linking, querying tasks, bugs, user stories, sprints, Azure DevOps boards, or other Azure Boards operations.
Full read-write access to Plain customer support platform. Create and manage customers, threads, companies, tenants, labels, tiers, help center articles, and more. Designed for workspace setup and demo preparation.
Use when asked to create, file, open, or raise a GitHub issue — including turning a bug report, a feature request, or a just-shipped backend change into a companion issue in another repository.
Plan an OpenSpec change and sync it to the MCP Task Hub as tiered, chunked tasks. Use when the user wants to plan/queue work for the agent drain loop ("hub-plan", "sync tasks to the hub", "queue up this change"). Spec artifacts always come from the official OpenSpec (opsx) tooling — this skill layers reconciliation…
Automate GitHub Projects v2 planning from codebase analysis. Use when: (1) Need to create comprehensive project board with epics and user stories, (2) Converting codebase analysis into GitHub issues, (3) Bulk issue creation with labels and status synchronization, (4) Setting up kanban board with proper organization.…
Manage the lifecycle of a project's planning docs (PLAN.md + TASKS.md + an implementer agent). Detects project state and routes to one of five actions — GRILL the user round-by-round to generate the decision record itself (a design-tree interview; the only action that creates material instead of reshaping it)…
Execute an existing multi-agent plan in this repository: run an execution preflight against docs/tasks.md and the kickoff prompt, then hand them to a fresh orchestrator that spawns development, QA, and independent-review agents until reviewed code is on disk. Use for requests to run the build, kick off or start…
IU work surface — Outlook calendar, Teams chats/channels + curated alerts, Jira tickets/sprint/backlog (read + create/update/comment on Johannes's behalf, always Team=Prometheus), Confluence docs, GitLab MRs + approvals + discussions. Cross-system identity via /m365/team roster. Personal assistant only, never…
A GitHub Issue drafting and publishing workflow that turns a one-line idea into a structured issue after checking the codebase and asking follow-up questions.
A writing skill for creating CUBRID issue reports in JIRA, a tool used to track software work. Reports are written in Korean with English section headings and include a structured triage section.
Iteratively refine beads for ralph-tui execution through 4-6 polishing rounds until convergence, ensuring each bead fits one agent context window, has quality gates appended, uses correct bd CLI syntax, and follows schema-backend-UI dependency ordering. Use when user wants to polish beads for ralph, refine ralph…
The exact commands your tracker uses - list and read tickets, create them with dependencies, claim and release, the board's Status moves, stacked PRs. Use whenever a task touches a ticket, the board, or a stacked PR, so nothing is guessed. This copy implements GitHub Issues with gh; a person on another tracker…
Bidirectional bridge between ClickUp and spec-kitty feature specs. Use when the user mentions ClickUp tasks, CU- IDs, spec-kitty features, creating tasks in ClickUp, importing ClickUp context into specs, or exporting spec-kitty specs to ClickUp. Provides /specup.setup, /specup.new, /specup.import, and /specup.export…
Use this skill when the user needs TeamDynamix ITSM operations through MCP: ticket triage and updates, KB article maintenance, asset/CI relationships, service catalog lookups, project issue/risk workflows, or time entry queries. Always discover IDs first, use read-before-write patterns, and enforce write safety gates.
★not rated 2 yesterdayA70 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: