pwdev-solucoes
- 190 skills
- 0 followers
- 3 repo stars
- last week last updated
- ▌ QA Specialist Requirements · pwdev-solucoesAssess requirement clarity, testability, completeness, consistency, and traceability without inventing missing acceptance criteria.
- ▌ QA Specialist Accessibility · pwdev-solucoesDesign traceable accessibility checks that combine scanners with observable keyboard, focus, semantic, and assistive-technology behavior.
- ▌ Hermes Orca · pwdev-solucoesUse 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.
- ▌ QA Specialist Mobile · pwdev-solucoesDesign platform-specific Android and iOS checks with explicit SDK, driver, device, lifecycle, and evidence prerequisites.
- ▌ Quality Gates PHP · pwdev-solucoesQuality gates determinísticos para PHP e Laravel. Use quando o usuário pedir "quality gate PHP", "quality gate Laravel", "PHPStan", "Larastan", "Pest", "PHPUnit", "PHPMD", "Composer Audit", cobertura PHP ou baseline PHP.
- ▌ Quality Gates Vue · pwdev-solucoesQuality gates determinísticos para Vue.js, JavaScript e TypeScript. Use quando o usuário pedir "quality gate Vue.js", ESLint, vue-tsc ou Vitest em projeto Vue.js, cobertura, complexidade, bundle, acessibilidade ou baseline para Vue.js.
- ▌ QA Specialist Defects · pwdev-solucoesTriage defects with independent severity and priority, reproducible evidence, preserved attempt history, and explicit resolution retesting.
- ▌ QA Specialist Metrics · pwdev-solucoesDefine auditable QA metrics with explicit numerators, denominators, populations, windows, and treatment of every result state.
- ▌ Quality Gates Node · pwdev-solucoesQuality gates determinísticos para aplicações e serviços Node.js, JavaScript e TypeScript. Use quando o usuário pedir "quality gate Node.js", ESLint ou tsc em Node.js, testes, cobertura, complexidade, SAST, SCA, build ou baseline para Node.js.
- ▌ QA Specialist Security · pwdev-solucoesDesign authorized, bounded, reproducible security checks without turning scanner findings into penetration-test permission.
- ▌ QA Specialist Strategy · pwdev-solucoesAnalyze product risk and propose traceable QA coverage, priorities, environments, data, and explicit coverage gaps.
- ▌ Power Roadmap Status · pwdev-solucoes bundleUse when the status, progress, completeness, traceability, or next valid action of a PWDEV Power product roadmap is requested
- ▌ Power Skill Refactor · pwdev-solucoes bundleUse 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.
- ▌ QA Specialist Readiness · pwdev-solucoesAssess release readiness from applicable criteria, all current defects, risks, limitations, and recorded human decisions without approving release.
- ▌ QA Specialist Automation · pwdev-solucoesDesign isolated repeatable automation, distinguish interactive browser exploration, and handle flaky results through evidence and reproduction.
- ▌ QA Specialist Functional · pwdev-solucoesDesign traceable functional test conditions across positive, negative, boundary, and error behavior with observable expectations.
- ▌ QA Specialist Production · pwdev-solucoesPlan explicitly authorized read-only production observations and trace evidence-backed causes into preventive regression coverage without external effects.
- ▌ QA Specialist Regression · pwdev-solucoesSelect traceable regression coverage from change impact, affected risks, criteria, dependencies, and prior defects rather than execution convenience.
- ▌ QA Specialist Performance · pwdev-solucoesDesign bounded performance profiles with explicit load authorization, contextual samples, percentiles, and agreed thresholds.
- ▌ Quality Gates Postgres · pwdev-solucoesQuality gates determinísticos para PostgreSQL. Use quando o usuário pedir "quality gate PostgreSQL", "quality gate Postgres", migrations ou schema drift PostgreSQL, constraints ou índices PostgreSQL, EXPLAIN, plano de consulta ou baseline para PostgreSQL.
- ▌ Power Product · pwdev-solucoes bundleUse when a product requirement, PRD, or executable roadmap is requested, or when an approved requirement needs decomposing into phases, epics, features and tasks
- ▌ Quality Gates · pwdev-solucoesEstratégia de quality gates determinísticos e adoção incremental para CI/CD. Use quando o usuário pedir "quality gate", "gate de qualidade", "política de bloqueio", "baseline", "ratchet", "qualidade no CI" ou "SonarQube".
- ▌ Github Issues · pwdev-solucoes bundleCria, 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).
- ▌ Github Status · pwdev-solucoes bundleUse 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.
- ▌ Power Worktree · pwdev-solucoes bundleUse when starting feature work that needs isolation from the current workspace, or before executing an implementation plan
- ▌ QA Specialist API · pwdev-solucoesDesign traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.
- ▌ QA Specialist Web · pwdev-solucoesDesign traceable Web and browser checks with explicit browser coverage, observed interactions, isolated sessions, and evidence limitations.
- ▌
- ▌ Github Project · pwdev-solucoes bundleUse 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).
- ▌ Github Publish · pwdev-solucoes bundleUse 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).
- ▌ QA Specialist Cicd · pwdev-solucoesDesign deterministic CI quality gates that read the normalized manifest verdict independently from report-export process status.
- ▌ QA Specialist Data · pwdev-solucoesDesign traceable data checks for reconciliation, integrity, transactions, and atomicity with separate observable oracles.
- ▌ Skill Refactor · pwdev-solucoes bundleReview or refactor an existing SKILL.md and its bundled resources — a smaller always-loaded core, conditional references, preserved behavior, lean/guided consumer profiles, and an A/B protocol to compare a candidate with the previous version. Use when a skill repeats itself, loads references on every run, triggers too broadly or misses legitimate requests, or needs its efficiency measured across models. Do NOT use for writing a new skill from scratch, refactoring application code, translating a skill verbatim, or performing the target skill's own task.
- ▌ Power Brainstorm · pwdev-solucoes bundleUse before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation
- ▌ Sdd Review · pwdev-solucoes bundleIndependent, traceable code review of one SDD Composy task in review_required against its approved PRD, stories, TechSpec, evidence, and project rules, with stable findings and severities. Use when a task passed QA and evidence — 'revisar a TASK-003', 'code review da task', 'review this task's diff'. Do NOT use for code review outside an SDD workspace (use the host code review), for QA (sdd-qa), or for verification (sdd-verify).
- ▌ Sdd Status · pwdev-solucoes bundleRead-only consolidated snapshot of an SDD Composy workspace: lifecycle stage, task contracts, trace integrity, loops, fleets, and the next action, without changing any file. Use for 'em que pé está o SDD', 'status do fluxo', 'qual a próxima ação', 'where are we in the workflow'. Do NOT use for git, CI, infrastructure, or other plugins' status, or to change state.
- ▌ Sdd Verify · pwdev-solucoes bundleAdversarial 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.
- ▌ Feat Backend · pwdev-solucoes bundleUse when the user wants a backend-only action plan — API endpoints, services, models, migrations, jobs and their tests — 'plano de backend para o endpoint X', 'plan the orders API'. Writes .planning/feat/features/{slug}/plan.md with the PWDEVIA method. Do NOT use for UI work (feat-frontend), full features spanning backend and UI (feat-feature), writing code (feat-exec) or quick 1–3 file fixes (feat-quick).
- ▌ Feat Feature · pwdev-solucoes bundleUse 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).
- ▌ Power Debug · pwdev-solucoes bundleUse when encountering any bug, test failure, or unexpected behavior, before proposing any fix
- ▌ Power Fleet · pwdev-solucoes bundleUse 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
- ▌ Power Quick · pwdev-solucoes bundleUse 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
- ▌ Sdd Execute · pwdev-solucoes bundleImplement 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.
- ▌ Sdd Stories · pwdev-solucoes bundleCreate, revise, or resolve applicability for SDD Composy user stories (US/SC) from an approved PRD and domain evidence, stopping at the human gate. Use after the PRD is approved — 'gerar as histórias de usuário', 'cenários de aceite', 'stories for prd-SLUG', 'is stories NOT_APPLICABLE here'. Do NOT use before the PRD is approved, for the TechSpec, or for user-story writing outside SDD.
- ▌ Feat Frontend · pwdev-solucoes bundleUse when the user wants a UI-only action plan — components, pages, composables/hooks, state, forms and their E2E coverage — 'plano de frontend para a tela X', 'plan the settings page'. Writes .planning/feat/features/{slug}/plan.md with E2E scenarios and playwright-cli checks. Do NOT use for API/database work (feat-backend), full features (feat-feature), writing code (feat-exec) or UI review (feat-review).
- ▌ Github Init · pwdev-solucoes bundleUse 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).
- ▌ Power Finish · pwdev-solucoes bundleUse when implementation is complete, tests pass, and the work needs integrating - merging, opening a pull request, or being left in place
- ▌ Power Review · pwdev-solucoes bundleUse when work needs reviewing before it is merged, and when review feedback has arrived and needs acting on
- ▌ Power Verify · pwdev-solucoes bundleUse when about to claim work is complete, fixed, or passing, and when a finished feature needs adversarial verification before integration
- ▌ Sdd Evidence · pwdev-solucoes bundleDiscover, build, verify, and optionally export (HTML, optional PDF) the evidence manifest of one SDD Composy task in evidence_required, routing it toward review_required. Use when acceptance evidence must be assembled or checked — 'juntar as evidências da task', 'gerar o relatório de evidências', 'verify the evidence manifest'. Do NOT use to run tests (sdd-qa), review code (sdd-review), or inspect the trace (sdd-trace).
- ▌ Sdd Techspec · pwdev-solucoes bundleCreate or revise the SDD Composy technical specification (tasks/prd-SLUG/techspec.md) from the approved PRD, resolved stories, and mapped codebase, with DEC/RISK and TU/TI/E2E traceability and a human gate. Use when the product contracts are approved and architecture is needed — 'criar a spec técnica', 'techspec do prd-SLUG', 'design the solution for…'. Do NOT use to change product scope, before PRD and stories approval, or for design notes outside SDD.
- ▌ Power Execute · pwdev-solucoes bundleUse when an approved plan needs executing task by task in this session, with a fresh implementer per task and review between tasks
- ▌ Sdd Loop · pwdev-solucoes bundleRun a bounded, provider-neutral SDD Composy correction loop on one approved task (EXECUTE, QA, EVIDENCE, REVIEW, VERIFY; at most 3 iterations) with explicit approval, safe-stop guards, and fresh verification. Use to continue an approved TASK autonomously — 'rodar o loop na TASK-003', 'continuar a task até passar', 'start a loop on task 4'. Do NOT use for the host's recurring loop runner, for fleets (sdd-fleet), or for a task without human approval.
- ▌ Sdd Sync · pwdev-solucoes bundleReconcile SDD Composy task Markdown and the JSON projection: read-only inspect and plan, then apply only with an explicit authority and the CONFIRM-SDD-SYNC token. Use when task contracts and operational state diverged — 'sincronizar as tarefas', 'o JSON das tasks está desatualizado', 'markdown and json disagree'. Do NOT use to list or advance tasks (sdd-tasks), for a status overview (sdd-status), or to simulate approval.
- ▌ Feat Audit · pwdev-solucoes bundleUse when the user wants to query the local pwdev audit trail — 'ver auditoria', 'relatório de auditoria', 'audit stats', 'exportar auditoria em PDF' — summary, events, decisions, artifacts, statistics, a Markdown/PDF export or a custom read-only SELECT. Do NOT use to enable the audit (feat-init) or for plan status (feat-status).
- ▌ Feat Quick · pwdev-solucoes bundleUse when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).
- ▌ Feat Setup · pwdev-solucoes bundleUse when the user wants the project instructions file generated or updated from the detected stack and conventions — 'gerar o arquivo de instruções do projeto', 'criar convenções do projeto', 'setup governance', 'gerar AGENTS'. Writes the shared instructions file read by Claude Code, Codex, Hermes and OpenCode. Do NOT use to analyze the codebase in depth (feat-map) or to initialize the workspace (feat-init).
- ▌ Power Tdd · pwdev-solucoes bundleUse when implementing any feature or fixing any bug, before writing implementation code
- ▌ Prd Publish · pwdev-solucoes bundleUse when an approved PRD roadmap must go to GitHub — 'publicar o roadmap no GitHub', 'criar o project e as issues do PRD', 'publish PRD roadmap' — handing over to pwdev-github (Project from a template, issues, sub-issues, blocked-by). Do NOT use for a single issue with the whole PRD (prd-export).
- ▌ Prd Roadmap · pwdev-solucoes bundleUse when an approved PRD must become an executable roadmap — 'gerar roadmap do PRD', 'quebrar o PRD em épicos e features', 'cadeia de dependências', 'roadmap with dependencies' — Phase/Epic/Feature/Task with explicit dependencies, waves and critical path, validated by a deterministic checker, with an approval gate. Do NOT use for a PRD that is not approved (prd- create/prd-refine first).
- ▌ Prd Stories · pwdev-solucoes bundleUse 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).
- ▌ Sdd Fleet · pwdev-solucoes bundleLaunch, inspect, or tear down an isolated fleet of ready SDD Composy tasks: one branch and Git worktree per member, a bound LOOP, cmux/tmux/headless presentation, no automatic merge. Use to run several ready tasks in parallel — 'rodar várias tarefas em paralelo', 'lançar o fleet', 'fleet status', 'tear down member X'. Do NOT use for a single task (sdd-execute, sdd-loop) or for merging without the explicit teardown token.
- ▌ Sdd Quick · pwdev-solucoes bundleDeliver a small bounded change inside an initialized SDD Composy workspace through the quick path: at most five implementation files, a registered TASK, TDD, evidence, trace, and a verified verdict, escalating otherwise. Use for a precise objective with no existing task — 'ajuste rápido via SDD', 'quick fix under SDD', 'small change to X in the SDD flow'. Do NOT use for an already registered task (sdd-execute), for architecture, migrations, or destructive work, or in repositories without SDD Composy (other plugins' quick).
- ▌ Sdd Tasks · pwdev-solucoes bundleGenerate and safely advance the SDD Composy task projection from approved PRD, stories, and TechSpec: import contracts, list/next/show, and guarded start/block/transition/verify. Use when work must be decomposed or a task's state inspected or moved — 'quebrar a spec em tarefas', 'listar as tarefas', 'qual a próxima task', 'mark TASK-003 blocked'. Do NOT use to implement a task (sdd- execute), reconcile Markdown and JSON (sdd-sync), or for a status overview (sdd- status).
- ▌ Sdd Trace · pwdev-solucoes bundleInspect, rebuild, or verify the append-only SDD Composy semantic trace (events.jsonl) and its derived projection (trace.json). Use for 'o que aconteceu nessa task', 'histórico do fluxo', 'verificar o trace', 'rebuild the trace projection'. Do NOT use for a status overview (sdd-status), evidence manifests (sdd-evidence), or to edit trace history.
- ▌ Feat Review · pwdev-solucoes bundleUse 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.
- ▌ Feat Status · pwdev-solucoes bundleUse when the user asks for the state of pwdev-feat plans — 'status do feat', 'quais planos estão pendentes', 'show feature status' — listing pending, complete, with-caveats, failed and resumable plans plus codebase-context health. Read-only. Do NOT use to execute (feat-exec) or query the audit trail (feat-audit).
- ▌ Power Init · pwdev-solucoes bundleUse 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
- ▌ Power Plan · pwdev-solucoes bundleUse when a design or set of requirements exists and work needs decomposing into tasks, before touching any code
- ▌ QA Regression · pwdev-solucoesBuild an impact-based regression selection with explicit traceability, inclusions, exclusions, and limitations.
- ▌ Sdd QA · pwdev-solucoes bundleIndependent quality assurance for one SDD Composy task in qa_required: CA coverage, unit/integration/E2E, accessibility, responsiveness, environment, and evidence inventory, producing the QA report and requesting evidence_required. Use when a task finished execution — 'rodar o QA da task', 'testar a TASK-003', 'validar a implementação'. Do NOT use for code review (sdd-review), the final verdict (sdd-verify), or test runs outside an SDD task.
- ▌ Feat Map · pwdev-solucoes bundleUse 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).
- ▌ Prd Audit · pwdev-solucoes bundleUse when the user asks about the pwdev-prd audit trail — 'auditoria do prd', 'eventos', 'decisões registradas', 'audit report', 'exportar relatório de auditoria' — querying the shared SQLite database read-only (summary, events, decisions, artifacts, stats, export, query).
- ▌ QA Explore · pwdev-solucoesExecute an explicitly authorized exploratory charter and record notes, findings, evidence, and follow-up without claiming false coverage.
- ▌ QA Release · pwdev-solucoesProduce an evidence-backed release readiness opinion while keeping the human release decision separate.
- ▌ QA Tooling · pwdev-solucoesRecommend context-appropriate QA tools while preserving observed availability, constraints, and safer alternatives.
- ▌ Sdd Map · pwdev-solucoes bundleProduce 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.
- ▌ Sdd Prd · pwdev-solucoes bundleCreate or revise the problem-first SDD Composy PRD (tasks/prd-SLUG/prd.md) with stable RF/CA identifiers, stopping at the human approval gate. Use when a user problem needs a product contract — 'criar o PRD', 'documento de requisitos', 'revisar o PRD do slug X', 'write the requirements for…'. Do NOT use for user stories (sdd-stories), technical design (sdd-techspec), or PRDs outside an initialized SDD workspace.
- ▌ Feat Exec · pwdev-solucoes bundleUse 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).
- ▌ Feat Init · pwdev-solucoes bundleUse 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.
- ▌ Feat Loop · pwdev-solucoes bundleUse 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).
- ▌ Feat Test · pwdev-solucoes bundleUse when the user wants tests planned for existing code or a test audit — unit, integration, E2E scenarios exportable to Playwright, playwright-cli UI checks, a coverage matrix — 'criar testes para o UserService', 'plano de testes E2E do login', 'auditar a cobertura'. Writes .planning/feat/features/{slug}/plan.md. Do NOT use for code review (feat-review), for implementing features (feat-feature) or to run an existing plan (feat-exec).
- ▌ Prd Create · pwdev-solucoes bundleUse when the user wants a new Product Requirements Document — 'criar um PRD', 'escrever os requisitos de', 'new PRD for', 'documento de requisitos' — through a 12-step interview, one question at a time, ending with an approval gate. Do NOT use to change an existing PRD (prd- refine) or to plan implementation.
- ▌ Prd Export · pwdev-solucoes bundleUse when the user wants a PRD exported — 'exportar o PRD', 'gerar o prd.json', 'criar issue com o PRD', 'export PRD to GitHub' — as canonical JSON or as a single GitHub issue. Do NOT use to publish a roadmap with many issues (prd-publish).
- ▌ Prd Refine · pwdev-solucoes bundleUse 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).
- ▌ QA Strategy · pwdev-solucoesProduce a traceable risk-based QA strategy without executing tests or expanding authorization.
- ▌ Sdd Init · pwdev-solucoes bundleInitialize 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.
- ▌ QA · pwdev-solucoesUse when a user asks for QA planning, execution, review, release assessment, reporting, status, or test-tool recommendations and the correct PWDEV QA workflow must be selected safely.
- ▌ QA Bug · pwdev-solucoesRecord a reproducible defect, independent triage, immutable attempts, and evidence-backed retest state.
- ▌ QA Init · pwdev-solucoesInitialize or inspect project-local PWDEV QA context without overwriting existing state or installing tools.
- ▌ QA Test · pwdev-solucoesExecute explicitly authorized tests and record traceable expected, observed, evidence-bound results.
- ▌ Power · pwdev-solucoes bundleUse when starting any conversation in a repository that uses PWDEV Power - establishes how to find and apply Power skills before any response, including clarifying questions
- ▌ Prd Init · pwdev-solucoes bundleUse when the user wants to set up pwdev-prd in a project — 'inicializar o pwdev-prd', 'init prd', 'configurar PRDs' — creating the .planning/prds/ workspace and choosing language and the optional SQLite audit trail. Do NOT use to write a PRD (prd-create).
- ▌ Prd List · pwdev-solucoes bundleUse when the user asks which PRDs exist — 'listar PRDs', 'quais PRDs temos', 'list PRDs' — with status, version, roadmap state and GitHub Project. Read-only.
- ▌ QA Report · pwdev-solucoesExport one validated QA manifest as matching HTML and PDF without executing tests or evidence commands.
- ▌ QA Review · pwdev-solucoesReview requirements, coverage, results, evidence, and findings without changing the product or recorded state.
- ▌ QA Status · pwdev-solucoesSummarize existing QA criteria, cases, evidence, defects, limitations, authorization, and verdict without mutation.
- ▌ Nginx Expert · pwdev-solucoesConfigura e diagnostica Nginx: reverse proxy, TLS, HTTP/2, HTTP/3, cache, compressão, rate limit e load balancing, com verificação obrigatória de configuração antes de recarregar.
- ▌ Postgres Dba · pwdev-solucoesDiagnoses and tunes PostgreSQL performance issues such as slow queries, missing indexes, bloat, locks, and connection problems, providing SQL commands and best practices.
- ▌ AWS Architect · pwdev-solucoesDiagnoses AWS architecture issues and reviews Well-Architected pillars using read-only AWS CLI commands, with confirmation required for any changes.