「ticket」の検索結果

This skill should be used when analyzing bug ticket data to identify quality trends, assess software quality status, and provide improvement recommendations. Use when a user provides bug lists (CSV, Excel, JSON, or Markdown format) and needs comprehensive quality analysis from a QA manager perspective. Generates statistical analysis, identifies quality hotspots, provides actionable recommendations, and produces professional Markdown reports suitable for project managers and executive leadership. Ideal for IT system development, migration, and implementation projects.

日本語の概要は準備中です。原文の説明を表示しています。

Generic helpdesk first-response skill for creating KB-based response drafts. Use when handling support tickets, creating response templates, or building a structured helpdesk workflow. Supports error code detection, keyword matching, confidence scoring, multi-language templates, and escalation workflows. Customize by providing your own KB articles and configuration.

日本語の概要は準備中です。原文の説明を表示しています。

Mine a codebase for breakthrough, evidence-backed opportunities — features, additions, refactors, simplifications, DX, UX, reliability, performance, or architecture cleanup. Researches project reality first, then forces two escalation gates (reject the merely-adequate idea; expand ambition 10x then collapse to the smallest proof-bearing artifact). Outputs ranked opportunities, an escalation ledger, and one plan seed. Does not implement or create tickets.

日本語の概要は準備中です。原文の説明を表示しています。

Product-discovery coach for Fishbowl engineers — inspired by Marty Cagan's work (never impersonates him). Stage-routes between opportunity brief, research, PRD, ticket drafting, and outcome review. Triggers on "product coach", "help me with product", "I need to write a PRD", "I want to do discovery", "opportunity assessment", "who is this for", "why are we building this", or when an engineer is starting, resuming, or post-mortem-ing product-adjacent work. Invoke with a short description of what you want to do, or invoke bare to be surveyed and routed.

日本語の概要は準備中です。原文の説明を表示しています。

Split user stories into smaller, independently deliverable slices using the SPIDR method (Spike, Path, Interface, Data, Rules). Use this skill whenever the user asks to split a story, break down work, slice a story, asks "can this be split", mentions "SPIDR", says "story splitting", or wants to decompose a large ticket into smaller pieces. Also trigger when a user presents a story that seems too large for a single sprint and asks for help sizing or scoping it.

日本語の概要は準備中です。原文の説明を表示しています。

Extrem kurzes, substantielles Ausgabe-FORMAT fuer EINE Entscheidung oder Entscheidungsgruppe, wenn die dahinterstehende Analyse bereits existiert (im Chat entstanden, aus `decide`, aus `decision-briefing`, aus einem Ticket oder Dokument): Kontext in 2-3 Zeilen, Pro/Contra je Option als Stichpunkte im paveman/caveman-reduzierten Stil, Talking Points, eine begruendete Empfehlung, und ein Pfad/Link zur Vollanalyse zum Komplett-Nachlesen. Nutze diesen Skill bei "gib mir das kurz mit Pro Contra und Empfehlung", "executive summary zur Entscheidung", "kurzkontext zu <Thema>", "fass die Entscheidung X in einer Kurzform zusammen", /decision-shot, oder wenn ein Ergebnis an jemanden weitergereicht werden soll, der nur die Essenz braucht, nicht die volle Herleitung. NICHT nutzen, um viele offene Entscheidungen zu SAMMELN und per Buchstabe abzufragen -- das macht decision-briefing; NICHT nutzen, um eine Entscheidung erst zu ANALYSIEREN -- das macht decide. decision-shot setzt eine fertige Analyse voraus und komprimiert nur deren Praesentation.

日本語の概要は準備中です。原文の説明を表示しています。

Abbruchbedingung für autonome Loops: So weit wie möglich selbständig weiterarbeiten UND einen Loop erst beenden, wenn belegt ist, dass keine autonom ausführbare Aufgabe mehr vorliegt. Der bloße Eindruck "nichts mehr zu tun" reicht NICHT — er löst eine vierstufige Prüfkette aus (think/decide, _CONTROL/_DECISIONS, Gardener/USMC, decision-avatar/BYUM), die zuerst neue Aufgaben GEWINNEN muss, bevor der Loop enden darf. Jeder Kettenschritt meldet found/empty/unavailable statt eines binären Ergebnisses — "exhausted" gilt nur, wenn ALLE Quellen tatsächlich befragbar waren; ist mindestens eine Quelle unavailable, meldet der Skill "blind" statt "exhausted" und behauptet nichts Ungeprüftes. Nutze diesen Skill bei /work-autonomous, /waafap, "arbeite autonom weiter bis nichts mehr zu tun ist", als Goal-Bedingung innerhalb eines /loop, oder wenn geprüft werden soll, ob wirklich keine autonome Arbeit mehr übrig ist, bevor ein Loop/eine Session beendet wird.

日本語の概要は準備中です。原文の説明を表示しています。

Baut und prüft neue Agentenrollen im ellmos-Ökosystem: native Claude-Code- Subagenten (dauerhafte Rollendefinition) und Companion-Worker (SendMessage- wiederverwendete Instanz für eine Ticket-/Aufgabenserie). Formalisiert das bislang unformalisierte eigene Wissen aus dem laufenden Bau von Agentenrollen (ati-agent, bueroassistent, versicherungs-agent u. a.) zu einem wiederverwendbaren Scaffold-plus-Verify-Ablauf. Nutze diesen Skill, wenn eine neue Rolle entstehen soll ("neue Agentenrolle bauen", "Subagent anlegen", "Companion-Worker starten") oder eine bestehende gegen die Haus-Konventionen geprüft werden soll ("ist dieser Agent richtig aufgesetzt?").

日本語の概要は準備中です。原文の説明を表示しています。

Einmaliger Tasksolver+Writer+Maintainer-Durchlauf fuer den Projektordner, in dem die Session gerade sowieso gearbeitet hat (inkl. Unterordner) — kein systemweiter Sweep. Loest offene triviale/autonome Register-Punkte, aktualisiert Dokumentation auf den gemessenen Ist-Stand (im Projekt UND in der Root der Pipeline, in der das Projekt liegt) und raeumt Strays/Temp- Dateien nach dem Papierkorb-Prinzip weg. Nutze diesen Skill bei /tidy-up, "raeum das Projekt auf", "mach hier sauber bevor wir weitermachen", am Ende einer Arbeitssitzung an einem Projekt, oder als faellige autonome Aufgabe innerhalb von /work-autonomous + /goal.

日本語の概要は準備中です。原文の説明を表示しています。

Produces a DRAFT product requirements document from the discovery notes, interview summaries, support themes, analytics notes and stakeholder messages the user provides: problem statement, target users, goals with measures as stated, numbered requirements each with a testable acceptance criterion, non-goals, constraints, dependencies and open questions, with every statement tagged evidenced, assumed or UNKNOWN so each assumption is visible for the product owner to confirm. Use when the user asks to "write a PRD", "draft the product requirements", "turn these discovery notes into requirements", "document what this feature needs to do" or "build the requirements doc for this epic". Do not use for supplier-facing requirements in a tender, use rfp-requirements-pack instead; for a technical design decision, use architecture-decision-record; for the change ticket that ships the work, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts an architecture or design decision record (ADR) from the discussion notes, design review minutes, chat threads and diagram descriptions the user provides: context, decision drivers, options considered with arguments as stated, the decision as the group worded it, consequences and a review date, with every factual claim tagged evidenced, asserted or UNKNOWN so unsupported claims are marked for the author to substantiate. Use when the user asks to "write an ADR", "document the architecture decision", "record why we chose this design", "turn these design review notes into a decision record" or "draft the design decision log entry". Do not use for a business or governance decision with no technical design, use decision-memo-builder instead; for the change ticket that implements the decision, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Turns reported data problems (messages, tickets, meeting notes, complaints) into one DRAFT issue log: one row per issue with the symptom as reported, dataset and fields named, reproduction steps, affected reports, first seen date, reporters, a suggested owner, and blank severity, root cause and status cells for the owner. Never asserts a root cause, severity or fix. Use when the user asks to "log these data issues", "turn these complaints about the numbers into an issue list", "build the data quality backlog", "which reports are hit by this data problem" or "write up the reproduction steps for this data bug". Do not use for exploring or profiling a dataset, use dataset-insight-pack instead; for an IT incident write-up, use incident-postmortem-drafter; for tracking fix actions once assigned, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Sorts a personal inbox backlog into five buckets (needs-reply-today, needs-reply-this-week, waiting-on-others, FYI, noise), writes DRAFT reply text for the messages that need an answer (up to 10 per run), and returns a dated triage report as one Markdown document. Lists moves or archives only as proposals for the user to perform, and only where a rule the user supplied says so; the agent changes nothing in the mailbox. Use when the user asks to "triage my inbox", "sort my mail", "clean up my inbox", "catch up after leave" or "what needs a reply today or this week". Do not use for a shared support queue or helpdesk export, use ticket-triage-pack instead; for what the user promised or is owed, use commitment-catcher; for one named thread, answer directly. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Manage the NV oOS Pro Toolkit CRM — leads, deals, companies, contacts, customers, activities, and support tickets. Covers the complete sales pipeline from lead capture through qualification, deal management, and post-conversion customer tracking with BANT/MEDDIC scoring, activity logging, and workflow automation. Use when working with CRM records, managing pipeline stages, qualifying leads, creating company profiles, logging calls/emails/meetings, or troubleshooting CRM data issues.

日本語の概要は準備中です。原文の説明を表示しています。

Create a HubSpot Real-Time capture using flowctl to stream CRM data into Estuary collections. Use when setting up a HubSpot source for contacts, companies, deals, tickets, or other HubSpot resources. Use when user says "capture HubSpot", "stream from HubSpot", "HubSpot CDC", or "connect HubSpot to Estuary".

日本語の概要は準備中です。原文の説明を表示しています。

Create a HubSpot materialization to write Estuary collections back into HubSpot CRM objects (Contacts, Companies, Deals, Tickets, etc). Use when setting up HubSpot as a destination for captured data. Use when user says "send to HubSpot", "materialize to HubSpot", "write back to HubSpot", or "HubSpot destination".

日本語の概要は準備中です。原文の説明を表示しています。

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a project follows a structured operating model with: two work lanes (Domain, System), unresolved work tracked as Epic, bounded execution tracked as Ticket, role-based behavior (architect, runner), helper-backed SQLite workflow tables, inbox and outbox files as task and result bodies.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", ...

日本語の概要は準備中です。原文の説明を表示しています。

An unpaid ticket picks up $10 at 30 days, another $20 at 60, and another $30 at 90, then turns into

日本語の概要は準備中です。原文の説明を表示しています。

X (Twitter) Scraper API and X API Alternative instructions for Xquik scraping and connected X account action planning. Also use for Xquik Radar or Xquik support tickets only when the user names that feature. Do not load or use this Skill for official X developer setup unless the user compares it with Xquik. Trigger when an X or Twitter task asks about posts, replies, likes, follows, messages, search, users, timelines, followers, exports, giveaways, draws, monitors, Xquik webhooks, MCP setup, SDKs, or API comparisons. Start read-only. Require confirmation for write plans, private reads, monitors, webhooks, support access, and metered bulk jobs. Not affiliated with X Corp.

日本語の概要は準備中です。原文の説明を表示しています。

Activate for any ticket that adds or changes a Supabase migration, environment variable, edge function deployment, or runtime configuration. Ensures infrastructure is live in the target QA environment before state:ready-for-qa.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: a general codebase assessment, pre-migration/pre-rewrite review, or explicit security-focused request needs a structured, repeatable security audit pass covering hardcoded secrets, injection-prone constructs, auth/debug backdoors, and insecure config defaults. Complements (does not replace) the built-in /security-review command. Not a mandatory gate on every ticket.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: investigating a legacy, inherited, third-party-built, or otherwise newly-unfamiliar codebase before scoping a migration or major refactor. Formalizes a repeatable five-step investigation pass — entry-point census, business-rule classification, side-effect/idempotency cataloging, implicit-contract discovery, semantic-duplication detection — plus a canonical per-project Open Questions document. Requires checkable signals: ticket keywords or prior documentation gaps. Not a mandatory gate;

日本語の概要は準備中です。原文の説明を表示しています。