「ds」の検索結果

Adversarial verification of one SDD Composy task in verify_required: reproduce every claim with fresh commands, build the truth table, refute stale evidence, and produce the verdict that gates complete. Use when review is done and the task claims to be finished — 'verificar a TASK-003', 'a task está pronta mesmo?', 'is this task really complete'. Do NOT use for QA, code review, or a general 'verify my work' outside an SDD task.

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

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.

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

Initialize or resume the SDD Composy workspace of a repository: preview missing governance and OKF bundle files, apply only approved absent paths, persist the artifact language, and verify. Use when a project needs SDD set up or resumed — 'inicializar o SDD', 'configurar o workspace SDD', 'run init first', or when any SDD skill returned not_initialized. Do NOT use for generic CLAUDE.md or repository setup outside SDD Composy, or for other plugins' init.

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

Implement exactly one SDD Composy task in the ready state with dependency preflight, TDD RED evidence, allowed paths, real verification commands, and the guarded transition to qa_required. Use when a ready task should be executed — 'executar a TASK-003', 'implementar a próxima tarefa', 'run task 4'. Do NOT use for changes without an approved task (sdd-quick), for autonomous multi-stage correction (sdd-loop), or for QA, review, or verification.

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

Issues, busca, comentários, tags, artigos e registro de trabalho no YouTrack Cloud via MCP oficial. Use quando o usuário disser "YouTrack", "criar issue", "minhas issues", "buscar tarefas", "comentar na issue", "atribuir para", "mudar o estado", "registrar horas", "artigo da knowledge base", ou citar um ID tipo PROJ-123. Boards e sprints são da skill youtrack-rest.

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

Produce a deterministic, read-only evidence map of the repository for SDD Composy (languages, manifests, commands, modules, boundaries, staleness) and publish the context bundle only on request. Use before a PRD or TechSpec, or when the map is stale — 'mapear o repositório', 'atualizar o contexto do código', 'what does this codebase look like for SDD'. Do NOT use for architecture decisions, code review, or repository exploration without an SDD workspace.

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

Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan

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

Export one validated QA manifest as matching HTML and PDF without executing tests or evidence commands.

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

Use when about to claim work is complete, fixed, or passing, and when a finished feature needs adversarial verification before integration

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

Design bounded performance profiles with explicit load authorization, contextual samples, percentiles, and agreed thresholds.

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

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.

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

Use when a design or set of requirements exists and work needs decomposing into tasks, before touching any code

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

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 the user wants to execute an existing pwdev-feat action plan — 'executar o plano user-crud', 'exec latest', 'rodar o plano', 'retomar a execução'. Dispatches the executor (subagent when the runtime has one, inline otherwise) in IMPLEMENT or REPORT mode, handles NEEDS_ADVICE with the advisor, and supports --resume. Do NOT use to create plans (feat-feature, feat-backend, feat-frontend, feat-test, feat-review) or for tasks without a plan (feat-quick).

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

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

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

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 an approved plan needs executing task by task in this session, with a fresh implementer per task and review between tasks

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

Enable, record, query, summarize, or verify the opt-in PWDEV Flow semantic audit trail. Use when the user asks what Flow actions occurred, wants audit integrity checked, or needs a portable JSONL record of workflow gates and artifacts.

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

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

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

Route supported legacy PWDEV Code command intent to canonical PWDEV Flow skills. Use when the user mentions old /pwdev-code:* commands, asks for PWDEV Code compatibility, or wants to adopt an existing .planning workspace without losing history.

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

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.

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

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.

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

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 implementation is complete, tests pass, and the work needs integrating - merging, opening a pull request, or being left in place

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