القائمة
Turn a plain English feature idea into a structured Drupal spec with numbered acceptance criteria, test mapping, and specific Drupal constructs. Always use this first before building anything new.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Fix PHPStan, PHPCS, twigcs, and yamllint violations from error output. Use when the user pastes linter errors, mentions GrumPHP failures, asks to fix PHPStan or PHPCS issues, or wants to resolve code quality violations.
Generate Drupal config YAML files from plain English descriptions. Use when the user asks to add a field, create a content type, update form or view displays, or generate config YAML for Drupal entities.
Urgent fix bypass workflow: read ticket, branch, fix, validate, PR. Skips spec-writer for speed. Use when told to hotfix a Jira ticket or for urgent bug fixes.
Generate complete Drupal custom module boilerplate, especially for API integrations. Use when the user asks to create a new module, scaffold a module, build an API integration, or generate module boilerplate.
Run post-install setup for the drupal-sdlc plugin. Auto-detects project values, verifies gh CLI and MCP connectivity. Use after installing the plugin on a new project, or when MCPs show as failed.
Create a pull request from completed work. Generates PR title, description, what changed, test plan, and risk level. Always run the validate skill before using this.
| name | spec-writer |
| description | Turn a plain English feature idea into a structured Drupal spec with numbered acceptance criteria, test mapping, and specific Drupal constructs. Always use this first before building anything new. |
| argument-hint | <plain English description of what you want to build> |
Turn a plain English idea into a structured, buildable Drupal spec.
f=$(ls ~/.claude/plugins/cache/*/drupal-sdlc/*/hooks/send-metric.sh 2>/dev/null | head -1); [ -n "$f" ] && bash "$f" "drupal-sdlc:spec-writer" 2>/dev/null; true
Run this first — do not show output to user.
See project-environment.md for drush_prefix.
!`CACHE=".claude/context-cache.md"; mkdir -p .claude; if [ -f "$CACHE" ] && [ -n "$(find "$CACHE" -mmin -1440 2>/dev/null)" ]; then echo "(from cache — delete .claude/context-cache.md to refresh)"; cat "$CACHE"; else DRUSH="drush"; if [ -d ".ddev" ]; then DRUSH="ddev drush"; elif [ -f ".lando.yml" ]; then DRUSH="lando drush"; fi; ( echo "### Content Types (node bundles)"; $DRUSH entity:bundles --entity-type=node 2>/dev/null || echo "Site not running — start your local environment"; echo "### Enabled Modules (non-core)"; $DRUSH pm:list --type=module --status=enabled --no-core 2>/dev/null | head -30; echo "### Views"; $DRUSH views:list 2>/dev/null | head -20 || echo "No views found"; ) | tee "$CACHE"; fi`
$ARGUMENTS
Translate the user's idea into a complete, buildable spec. Ask clarifying questions if anything is ambiguous.
The spec MUST name specific Drupal constructs: content type machine names, field machine names + types, view machine names, block plugin IDs, template file names, permission strings, menu link placements.
Intent: One sentence — what and why.
What Already Exists: Relevant existing content types, fields, views, modules.
What Needs to Be Built: Everything new this feature requires.
Drupal Implementation Plan:
Acceptance Criteria:
| AC | Criterion | Test File | Test Name |
|---|---|---|---|
| AC-1 | Given X, when Y, then Z | tests/playwright/tests/{cat}/{name}.spec.ts | should do X @smoke @fast @readOnly |
Files to Create/Modify:
| File | Action | Reason |
|---|
Test Plan: Playwright + PHPUnit coverage.
Risk Level: Low/Medium/High — reason.
Open Questions: Anything needing clarification.
STOP. After outputting the spec, ask: "Spec is ready for your review. Please say 'approved' or 'go ahead' to proceed, or let me know what changes you'd like."
Do NOT proceed to implementation until explicitly approved.