「pe」の検索結果

Analyze product risk and propose traceable QA coverage, priorities, environments, data, and explicit coverage gaps.

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

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).

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

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).

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

Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.

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

Design traceable data checks for reconciliation, integrity, transactions, and atomicity with separate observable oracles.

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

Assess requirement clarity, testability, completeness, consistency, and traceability without inventing missing acceptance criteria.

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

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.

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

Use when the user hands over a GitHub issue to be delivered end to end — 'resolver a issue #42', 'loop na issue 42', 'deliver issue https://github.com/o/r/issues/42' — or when an Orca worker preamble dispatches `feat-loop #N`. Turns the issue into a plan, executes it, reviews the result and runs at most 2 fix cycles until APPROVED, then opens a pull request that closes the issue. Never merges. Do NOT use without an issue (feat-feature / feat-quick), to only plan (feat-feature), to only review (feat-review) or to execute an existing plan (feat-exec).

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

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 quando o usuário quiser configurar o pwdev-github — 'configurar github', 'setup do github project', 'init github' — verificando gh, autenticação e o scope project e gravando repo e Project padrão em .planning/github.json. Não use para criar um Project (github-project).

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

Cria, atualiza, comenta, fecha e reabre issues do GitHub e gerencia as tarefas de um GitHub Project — mover Status, editar campos, sub-issues e dependências "blocked by", inclusive em lote. Use quando o usuário disser "criar issue", "abrir uma issue", "fechar a issue #12", "reabrir", "comentar na issue", "atribuir para", "mover para Em andamento", "marcar como concluída", "bloqueada por", "sub-issue", "o que está bloqueando", "tarefas do project", "fechar as tasks da feature", ou citar #123 num repo GitHub. Não use para criar um Project novo (skill github-project) nem para publicar um roadmap inteiro (skill github-publish).

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

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).

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

Leitura, escrita e edição estruturada de notas, busca, tags, arquivo ativo e comandos da paleta no Obsidian via MCP (plugin Local REST API). Use quando o usuário disser "Obsidian", "vault", "nota", "anotação", "criar nota", "buscar nota", "tag", "daily note", "frontmatter", "abrir arquivo no Obsidian", ou pedir para ler/editar/organizar conteúdo do vault.

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

Use when an approved plan needs executing task by task in this session, with a fresh implementer per task and review between tasks

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

Use when implementation is complete, tests pass, and the work needs integrating - merging, opening a pull request, or being left in place

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

Review a code diff or explicit file set through independent correctness and QA lenses. Use when the user asks for a code review, test-coverage assessment, pre-merge audit, or review gate in a PWDEV Flow workflow.

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

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.

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

Use quando o usuário quiser criar um GitHub Project — 'criar um project no github', 'novo board', 'project a partir de template', 'copiar project modelo' — a partir de um preset (roadmap-produto, kanban, scrum) apresentado e personalizável antes de criar, ou copiando um Project-modelo. Não use para publicar um roadmap (github-publish) nem para mexer em issues (github-issues).

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

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

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

Initialize, inspect, resume, or migrate portable PWDEV Flow project state. Use when the user asks to set up PWDEV Flow, adopt an existing repository or legacy PWDEV Code workspace, resume its workflow, or diagnose its current state.

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

Use when the user wants a code review of an explicit range or set of files — correctness, security, performance, conventions, tests — with stable findings (CR-nnn, BLOCKER..INFO) and rule citations — 'revisar os últimos commits', 'code review da feature X', 'review base..HEAD'. Plans a REPORT-mode review (no code changes, no commit). Do NOT use to fix code (feat-feature / feat-quick), to write tests (feat-test) or for UI/UX design critique.

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

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 encountering any bug, test failure, or unexpected behavior, before proposing any fix

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

Discover and approve feature requirements through focused interviewing and repository research. Use when the user has a feature idea, unclear scope, conflicting requirements, or needs Flow context artifacts before design.

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