863 件 ・ 関連度順
概要と使いどころ
Explores ambiguous product or engineering intent before implementation, clarifies users, constraints, alternatives, risks, and acceptance criteria, and turns the result into an approved design direction. Use for a new feature, subsystem, creative UI, architecture change, or unclear request. Not for an already-scoped bug fix, an existing implementation plan, or a narrow code review.
日本語の概要は準備中です。原文の説明を表示しています。
Designs risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, choosing test layers, or establishing release criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Runtime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA", "does it work", exploratory checks, or post-review runtime verification. Not static code review.
日本語の概要は準備中です。原文の説明を表示しています。
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is story X ready to implement'.
日本語の概要は準備中です。原文の説明を表示しています。
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
日本語の概要は準備中です。原文の説明を表示しています。
Before writing any implementation code, define the acceptance criteria and test cases that the code must satisfy. Agents then write code to pass these tests — not to match a vague description. Eliminates "it works on my machine" and "I think this is what you wanted" outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision, L1 Requirements, L2 Team Detail, L3 Acceptance Criteria). Use for cross-team specs.
日本語の概要は準備中です。原文の説明を表示しています。
Authoring standalone and cross-team specifications: PRD/SRS/HLD/LLD, staged L0-L4 unified packages, BDD acceptance criteria, and traceability. Use for technical or multi-audience documentation; not implementation or architecture decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrating multi-specialist task chains and scope-adaptive product delivery: classifies intent, selects and executes the minimum viable chain, aggregates results, and verifies acceptance criteria. For multi-domain tasks, build-first delivery, and product lifecycle execution.
日本語の概要は準備中です。原文の説明を表示しています。
Generate tests for a completed phase based on UAT criteria and implementation
日本語の概要は準備中です。原文の説明を表示しています。
Design a project-based learning brief with a driving question, milestones, and assessment criteria. Use when planning PBL units, inquiry projects, or extended investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Tags harness-decomposed curriculum items (KUDs, LTs, criteria) with a school's developmental band metadata while preserving source voice and labels. Supply the band schema; the skill derives mapping rules from it.
日本語の概要は準備中です。原文の説明を表示しています。
Analyse student work against criteria to identify specific gaps between current performance and learning objectives. Use when reviewing submissions, planning feedback, or diagnosing learning needs.
日本語の概要は準備中です。原文の説明を表示しています。
Routes between five assessment pathways — formative, rubric/criteria, authentic/performance, peer/self, and diagnostic — with validity and equity checks. Use when a teacher needs help choosing how to assess.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a criterion-referenced rubric with descriptive performance levels for a task or objective. Use for marking guides and general curriculum contexts. For Manning programmes where Competent = success, use coherent-rubric-logic-builder instead.
日本語の概要は準備中です。原文の説明を表示しています。
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Search and analyze TikTok video data, filter videos by region, creator, product, category, views, duration, publish time, selling/ad/AI video flags, and return views, likes, comments, shares, favorites, video sales and GMV metrics across 16 TikTok Shop sites. Trigger when users mention TikTok video search, TikTok video list, TikTok promotional videos, TikTok video data, TikTok video views, TikTok video sales, TikTok video analytics, Nexscope video, TikTok video search, TikTok video list, TikTok video analytics, TikTok promotional videos, TikTok video views, TikTok video engagement. Even if the user does not explicitly mention "Nexscope" or "TikTok", trigger this skill whenever their need involves searching or analyzing TikTok video performance metrics by criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Amazon reverse product selection: filter Amazon niches and keywords by 30+ business dimensions (market size & growth, price tiers & share, competition density & top concentration, demographics such as age/gender/income, review highlights & pain points) from a metrics pool aggregated from historical business insight reports. Trigger when users mention reverse product selection, metrics filtering, niche reverse lookup, blue ocean niche discovery, low-competition niche, newcomer-friendly niche, brand-fragmented market, pain-point entry, feature reverse lookup, pricing tier opportunity, demographic-based selection, or similar terms. Even if the user does not explicitly say "reverse product selection," trigger this skill whenever the request involves filtering Amazon niches that match specific business criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Use Nexscope market list capability to filter Amazon niche markets by category dimensions, supporting market size, competition, top concentration, seller structure, new product share, price/rating/margin ranges, and many other criteria for discovering viable markets and evaluating product selection directions. Trigger when the user mentions Amazon market research, niche category research, market opportunity screening, market concentration analysis, new product opportunities, market selection, Nexscope market research, category market research. Even if the user does not explicitly mention "Nexscope", if the need is to screen and evaluate Amazon markets by category dimensions, this skill should also be triggered.
日本語の概要は準備中です。原文の説明を表示しています。
Use Nexscope data to search and filter Amazon products, supporting multi-dimensional criteria including price, monthly sales, BSR ranking, gross margin, ratings, fulfillment method, badges, seller origin, and more across multiple Amazon marketplaces. Trigger when the user mentions Amazon product selection research, product filtering, sales filtering, product discovery, BSR analysis, niche product discovery, competitor analysis, market opportunity assessment, product-level market size estimation, gross margin screening, Nexscope product selection, Amazon product selection, sales filtering, BSR analysis, profit screening, market analysis, product selection tool. Even if the user does not explicitly mention "Nexscope", if their need involves filtering and analyzing Amazon product-level data for product selection, this skill should also be triggered.
日本語の概要は準備中です。原文の説明を表示しています。
Nexscope Product Database multi-condition filtering. Filter Amazon products by category, price, sales volume, revenue, reviews, rating, weight, BSR rank, LQS, seller type, and more across 10 marketplaces. Trigger when users mention Amazon product selection, product database filtering, BSR rank filtering, category-based product discovery, high-rating low-competition products, FBA product search, Amazon product discovery, or similar terms. Even if the user does not explicitly mention "Nexscope" or "product database," trigger this skill whenever the request involves filtering Amazon products by multiple criteria or discovering potential products.
日本語の概要は準備中です。原文の説明を表示しています。
Convert a vague mini-program idea, feature request, or partially documented product into an evidence-calibrated product specification with target users, core problem, version-one scope, main and exception flows, page responsibilities, state matrices, and testable acceptance criteria. Use when users ask to define an MVP, clarify requirements, organize product flows, specify page behavior, resolve ambiguous product states, or prepare a stable handoff before architecture or implementation. Separates facts, user decisions, assumptions, unknowns, and future ideas; never invents product logic merely to complete a screen or technical plan.
日本語の概要は準備中です。原文の説明を表示しています。
Builds measurable validation criteria when no existing standards apply. Invoked by team agents during review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or formatting an ADR document using the MADR template, applying Definition of Done (E.C.A.D.R.) criteria, or verifying ADR completeness. Triggers on "write the ADR", "format as MADR", "check ADR quality", "mark gaps in ADR". Also triggers when a decision has been extracted and needs to become a document. Does NOT extract decisions from conversations (use adr-decision-extraction) or orchestrate the full extract-confirm-write workflow (use write-adr).
日本語の概要は準備中です。原文の説明を表示しています。