prd-requirements-verifier
Verify completed work against a PRD's Given/When/Then requirements.
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-20 00:12
54,037 results
Verify completed work against a PRD's Given/When/Then requirements.
Ask the user for project status, then draft an English weekly update and suggested Health value using the Vilgain project wiki format.
Harness v3 integrated setup skill. Handles project initialization, tool configuration, 2-agent structure, memory configuration, and public skill mirror synchronization. Launch with: setup, initialization, new project, CI setup, codex…
Understand Apex language rules, ANTLR grammar structure, and how to implement parser listeners for language server features. Use when working on Apex parser…
Everything about generating, maintaining, and troubleshooting the Apex standard library stubs in StandardApexLibrary. Use when regenerating stubs, debugging…
Fix lint errors by removing unused variables and imports rather than prefixing with underscore. Use when lint errors are reported, when fixing compilation…
Draft PRs with trailing " - W-XXXXXXXX" in titles, conventional commit-style before it, GUS refs in body. Use when drafting PRs, PR titles, PR descriptions,…
Find open GitHub issues whose linked GUS work item is closed AND whose issue number appears in the shipped GitHub release notes, then close them. Use when user…
Guidelines for using vscode.window.show*Message methods. Use when working with showInformationMessage, showWarningMessage, showErrorMessage.
Numbering convention for ordering GUS work items within an epic. Numeric prefixes in Subject__c express sequencing (do X before Y) and parallelism. Use when…
Polish the automated CHANGELOG for a release branch. Removes GUS refs, categorizes under-the-cover changes, improves customer-facing descriptions. Use when…
Create feature branches for all work. Use when creating branches, checking out, or pushing. Prevents accidental pushes to protected branches.
Editing extension i18n message files and their consumers. Use when editing packages/*/src/messages/i18n.ts, adding/changing nls.localize strings, or choosing…
Draft PRs with trailing " - W-XXXXXXXX" in titles, conventional commit-style before it, GUS refs in body. Use when drafting PRs, PR titles, PR descriptions,…
Use file-based span/log export for AI consumption. Where it lives, how to enable/clear, record format for Node and Web. Use when enabling span file dump,…
Author and use Wireit scripts for npm. Use when working with Wireit configuration, npm scripts, build pipelines, or when the user mentions Wireit.
Numbering convention for ordering GUS work items within an epic. Numeric prefixes in Subject__c express sequencing (do X before Y) and parallelism. Use when…
Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen,…
Must follow when writing or reviewing index.ts/index.js barrel export files, ensuring all exports follow standards such as re-export only, no business logic, named exports, etc.
Use when a full best-practice check of a project is needed—automatically discover and sequentially execute all skills ending with best-practice, output a summary report, and enforce standardized validation instructions. Trigger words: check all skills, full specification validation, batch best-practice check.
Use when you need to batch-verify whether Skills comply with best-practice specifications, automatically check dimensions such as naming, front matter, structure, and dependencies, generate a detailed report, and output fix suggestions; supports single or batch checks. Trigger words: check skill specifications, batch-verify skill quality, scan all skills, full skill quality validation.
Use when you need to generate, optimize, fix, or check all index files (barrel exports) in a project, ensuring that index.ts/index.js all follow the standard barrel export specification. Trigger words: generate barrel exports, optimize index files, check barrel export specification.
Use when it is necessary to check whether hardcoded content exists in the code, including magic numbers, paths, URLs, keys, environment variables, response messages, etc.; ensure that all configurable values are managed using constants or configuration files. Trigger words: hardcode, hard code, magic number.
Use when you need to check whether Props Drilling exists in the code, identifying data that should be obtained directly from the Zustand Store but is passed through multiple component layers. Trigger words: check props passing, props drilling, eliminate passing through, check component dependencies.