メニュー
Gate function ensuring implementations are tested before claiming completion. Prevents rationalization and untested claims. Use at the end of any implementation task to validate work actually functions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | verification-before-completion |
| description | Gate function ensuring implementations are tested before claiming completion. Prevents rationalization and untested claims. Use at the end of any implementation task to validate work actually functions. |
| metadata | {"status":"stable","drupal-version":"all","last-reviewed":"2026-04"} |
Mandatory verification gate for all implementation tasks.
Before claiming ANY task is complete:
If any step fails, fix and re-test. Do not skip to claiming completion.
| Claim | Requires | NOT Sufficient |
|---|---|---|
| "Service works" | drush eval or curl test passes | "Code looks correct" |
| "Page renders" | curl smoke test HTTP 200 + content check | "Template created" |
| "Config imports" | ddev drush cim -y succeeds | "Exported config" |
| "Hook fires" | drush eval or behavioral test | "Added the hook" |
| "Module enabled" | ddev drush pm:list --status=enabled shows it | "Created .info.yml" |
| "Route works" | curl returns expected response | "Added routing.yml" |
| "Field exists" | drush eval field definition check | "Added field config" |
| "Permission works" | Login as role + curl test | "Added permission" |
| "Form submits" | Curl POST or Behat test | "Created form class" |
| "Cache works" | Two requests, second faster or cached | "Added cache tags" |
Include in your completion message:
## Verification Results
**Tested**: [what was tested]
**Method**: [curl/drush eval/test script]
**Results**:
- [Test 1]: PASS/FAIL - [details]
- [Test 2]: PASS/FAIL - [details]
**Scripts created**: [list any scripts in scripts/tests/]
**Status**: [VERIFIED/NEEDS ATTENTION]
Common excuses that are NOT verification:
| Excuse | Reality | Do Instead |
|---|---|---|
| "The code follows best practices" | Best practices don't guarantee it works | Run a test |
| "I've seen this pattern work before" | This specific implementation may differ | Run a test |
| "It should work after cache clear" | "Should" is not "does" | Clear cache AND test |
| "The logic is straightforward" | Typos and misconfigurations are common | Run a test |
| "I've created all required files" | Files existing != system working | Run a test |
| "The service definition looks correct" | YAML indentation, class names can be wrong | drush eval to check |
[ ] Ran at least one verification test
[ ] Read the actual test output (not assumed)
[ ] Test output confirms the specific claim
[ ] Included test results in completion message
[ ] Scripts stored in scripts/tests/ (if created)
[ ] Updated scripts/tests/index.md (if scripts created)
Analyze autopilot effectiveness and tune the drupal-workflow plugin based on real session data. Use when the autopilot feels too noisy, too quiet, or is being ignored. Also use when you want to check if recent changes to the plugin are actually working, review intervention acceptance rates, or improve classifier accuracy. Trigger on: "tune autopilot", "autopilot stats", "self-improve", "is the autopilot working", "too many warnings", "interventions being ignored", "plugin health", or after any conversation about autopilot effectiveness.
Core Drupal development rules covering code quality, security, services, and testing verification. ALWAYS consult when writing Drupal code.
Docs-first discovery for efficient codebase exploration. Use before Glob/Grep/Explore to get Logic IDs and file paths directly from semantic documentation. Saves tokens by avoiding expensive file searches. Commands include `/discover FEATURE` for feature lookup, `/discover "search terms"` for keyword search, and `/discover --prime` to load the business index.
Explore requirements, constraints, and design options before implementing Drupal features. Use BEFORE writing code — when starting a new feature, module, or significant change. Produces a decision record with entity design, service architecture, and hook/event strategy.
Cache bins, tags, contexts, invalidation strategies, and external caching for Drupal 10/11. Use when implementing caching, optimizing performance, or configuring cache backends.
PHPCS, PHPStan, naming conventions, and code style enforcement for Drupal 10/11. Use when checking coding standards, running static analysis, or enforcing code quality.