5.5万 件 ・ 関連度順
Agile boards, sprints, relatórios de tempo, anexos e operações em lote no YouTrack via REST API direta — o que o MCP oficial não cobre. Use quando o usuário disser "board", "quadro", "sprint", "sprint atual", "mover para o sprint", "horas registradas", "relatório de tempo", "anexar arquivo", "aplicar comando em várias issues". Requer YOUTRACK_BASE_URL e token.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to change an existing PRD — 'refinar o PRD', 'adicionar requisito', 'atualizar escopo do PRD', 'update the PRD' — through targeted questions, bumping the version and re-opening approval. Do NOT use to create a PRD (prd-create).
日本語の概要は準備中です。原文の説明を表示しています。
Plan explicitly authorized read-only production observations and trace evidence-backed causes into preventive regression coverage without external effects.
日本語の概要は準備中です。原文の説明を表示しています。
Execute explicitly authorized tests and record traceable expected, observed, evidence-bound results.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to evolve the features of a PRD roadmap with user stories — 'refinar as histórias da feature', 'escrever histórias de usuário', 'critérios de aceite', 'regras de negócio da feature', 'deixar a feature pronta', 'user stories for FT01' — one feature at a time, interviewing the human until each story meets the Definition of Ready: persona, value, INVEST, CA (Gherkin, happy and error paths) and RN from the PRD. Do NOT use to create the roadmap (prd-roadmap) or to change requirements without stories (prd-refine).
日本語の概要は準備中です。原文の説明を表示しています。
Record a reproducible defect, independent triage, immutable attempts, and evidence-backed retest state.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize or inspect project-local PWDEV QA context without overwriting existing state or installing tools.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze product risk and propose traceable QA coverage, priorities, environments, data, and explicit coverage gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable Web and browser checks with explicit browser coverage, observed interactions, isolated sessions, and evidence limitations.
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable data checks for reconciliation, integrity, transactions, and atomicity with separate observable oracles.
日本語の概要は準備中です。原文の説明を表示しています。
Extrai o brand kit do Figma — tokens de cor, tipografia, grid, logo e componentes — e grava na seção 3 do contexto. Use quando o usuário disser "extrair a marca", "pegar os tokens", "quais as cores", "design system", "importar do Figma", "montar brand kit", ou quando a seção 3 estiver vazia. Lê do Figma; não inventa paleta.
日本語の概要は準備中です。原文の説明を表示しています。
Aumenta resolução e qualidade de imagem via Freepik/Magnific, ou orienta o processo manual quando não há chave. Use quando o usuário disser "upscale", "melhorar a resolução", "a imagem está pixelada", "Magnific", "Freepik", "aumentar a imagem", "imagem pequena demais". Gasta crédito — exige confirmação.
日本語の概要は準備中です。原文の説明を表示しています。
Define auditable QA metrics with explicit numerators, denominators, populations, windows, and treatment of every result state.
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable accessibility checks that combine scanners with observable keyboard, focus, semantic, and assistive-technology behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Assess requirement clarity, testability, completeness, consistency, and traceability without inventing missing acceptance criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Assess release readiness from applicable criteria, all current defects, risks, limitations, and recorded human decisions without approving release.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an approved plan needs executing task by task in this session, with a fresh implementer per task and review between tasks
日本語の概要は準備中です。原文の説明を表示しています。
Design an approval-gated feature specification from approved requirements. Use when PWDEV Flow discovery is complete and the user needs architecture decisions, component boundaries, quality constraints, and a definition of done.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a full feature action plan (backend + frontend + tests) with the PWDEVIA 7-question method before any code is written — 'planejar a feature X', 'criar plano de feature', 'plan the user CRUD'. Interviews the human (max 2 rounds) and writes .planning/feat/features/{slug}/plan.md. Do NOT use to write code (feat-exec), for small 1–3 file changes (feat-quick), backend-only or UI-only scope (feat-backend / feat-frontend), tests for existing code (feat-test) or code review (feat-review).
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose repository and PWDEV Flow health without changing the project. Use when the user asks for a health check, workspace consistency check, dependency assessment, readiness report, or evidence-based scorecard.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarially verify an implementation against its objective, acceptance criteria, definition of done, and prohibitions using fresh evidence. Use for completion gates, release readiness, or independent verification after implementation and review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants the existing codebase analyzed for planning — 'mapear o código', 'analisar o projeto', 'atualizar o contexto', 'map codebase' — or when a planning skill reports a missing or stale map. Runs a deterministic read-only evidence scan and writes codebase.md plus the architecture, conventions, testing and concerns context documents under .planning/feat/. Do NOT use for code review (feat-review), architecture decisions, or writing the project instructions file (feat-setup).
日本語の概要は準備中です。原文の説明を表示しています。
Use when approved phases should run in parallel — visually in a cmux panel or unattended — when fleet status is requested, or when a fleet member must be stopped or merged
日本語の概要は準備中です。原文の説明を表示しています。