「claude」の検索結果

Use quando um roadmap pwdev-roadmap/1 (roadmap.json) precisar ir para o GitHub — 'publicar o roadmap', 'criar as issues do roadmap', 'publish roadmap.json' — com issues, sub-issues, milestones, blocked-by e campos do Project, com dry-run, idempotente e retomável. Não use para uma issue avulsa (github-issues).

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

Use when work needs reviewing before it is merged, and when review feedback has arrived and needs acting on

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

Create an approval-gated product requirements document or decompose an approved PRD into a traceable roadmap. Use for product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, or roadmap planning.

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

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 a product requirement, PRD, or executable roadmap is requested, or when an approved requirement needs decomposing into phases, epics, features and tasks

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

Use when a repository has no PWDEV Power workspace yet, when resuming one, when the codebase map needs refreshing, or when the setup should be checked

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

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

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing any fix

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

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.

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

Consultas, inspeção de schema e mutações seguras (DML/DDL com dry-run) no PostgreSQL via MCP (@soarescbm/postgres-mcp). Use quando o usuário disser "postgres", "postgresql", "banco de dados", "tabela", "query", "SELECT", "índice", "schema", "constraint", "foreign key", "coluna", "DDL", "insert", "update", "delete", "criar tabela", ou pedir para consultar/alterar dados de um banco Postgres.

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

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.

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

Use quando o usuário perguntar o estado da integração com o GitHub — 'status do github', 'qual project está configurado', 'o que já foi publicado' — gh, scopes, repo, Project e roadmaps publicados. Somente leitura.

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

Use when the user, inside an Orca terminal, asks Hermes to resolve, dispatch, orchestrate or supervise GitHub issues with Orca workers — 'orquestrar as issues 12, 15 e 18 no Orca', 'despachar as issues com label ready', 'coordenar workers do Orca para estas issues', or to resume such a Run after compaction. Do NOT use for a single unsupervised hand-off to another agent (Orca CLI directly), for working on one issue in this session (pwdev-feat feat-loop), or outside Orca.

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

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 the status, progress, completeness, traceability, or next valid action of a PWDEV Power product roadmap is requested

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

Curate durable PWDEV Flow project decisions, lessons, and conventions. Use when the user asks to capture, list, show, link, supersede, or select project memory, or when an approved workflow decision should persist across phases.

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

Use when a change is small and already understood - at most three files, such as a typo, a config value, a rename, or a one-line bugfix - and a plan file would cost more than the change

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

Use when the user wants to set up pwdev-feat in a project — 'inicializar o pwdev-feat', 'configurar o feat', 'init feat workspace' — choosing language, model profile and the optional audit trail, and creating the .planning/feat/ workspace. Do NOT use to analyze the codebase (feat-map), to write the project instructions file (feat-setup) or to create plans.

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

Tickets, triagem, followups, solução, usuários, grupos, ativos, projetos e base de conhecimento no GLPI via MCP glpi.

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

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

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

Use when an existing skill must be refactored to cut context and ambiguity without losing behavior, safety or fallbacks — 'refatorar a skill', 'reduzir esta SKILL.md', 'revisar skill com métricas' — with before/after metrics, preserved invariants and three review rounds.

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

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 a design or set of requirements exists and work needs decomposing into tasks, before touching any code

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

Decompose an approved PWDEV Flow specification into dependency-aware waves and atomic executable tasks. Use when design is approved and the user needs exact file scope, test-first actions, verification commands, and an execution gate.

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