drupal-dev-framework

Mark a task as done and move to completed. Trigger: 'finish task', 'mark done', 'task complete', 'close task'. Runs ALL 5 quality gates before allowing completion.

Design architecture for a specific task. Trigger: 'architecture', 'design task', 'plan component', 'Phase 2'. REQUIRES completed research. Enforces Library-First, CLI-First, SOLID, DRY.

Load context and start implementing a task. Trigger: 'start coding', 'implement task', 'begin implementation', 'Phase 3', 'write code'. REQUIRES completed architecture. Enforces TDD (test-first).

Migrate v2.x single-file tasks to v3.0.0 folder structure. Trigger: 'upgrade tasks', 'convert task format', 'v2 to v3 migration'.

Start a new development project. Trigger: 'start project', 'new module', 'initialize project', 'begin development'. Creates project structure and gathers requirements BEFORE any coding.

Use when designing project architecture - creates architecture/main.md with component breakdown, service dependencies, and pattern references. Trigger: 'design module', 'plan architecture', 'create architecture document', 'component design', 'service design'. MUST enforce Library-First (services before forms/controllers), CLI-First (Drush commands for all features), SOLID principles, and DRY patterns. NEVER approve architecture that puts business logic in forms or controllers.

Use when validating implementation against architecture - checks approach matches documented patterns, dependencies, architecture principles (Library-First, CLI-First), and SOLID/DRY principles. Trigger: 'check my code', 'does this match the architecture', 'validate implementation', 'architecture review', 'code review against architecture'. MUST validate against ALL 5 quality gates: SOLID, Library-First/CLI-First, DRY, TDD, Security. BLOCK on violations — do not just warn. Use proactively after ANY code changes during Phase 3.

Use when researching Drupal contrib modules or existing solutions - analyzes drupal.org and contrib code to identify reusable patterns and integration points. Trigger: 'find existing module', 'is there a contrib for this', 'search drupal.org', 'existing solutions', 'before building'. Use proactively at the START of Phase 1 — ALWAYS check contrib before building custom. Never let user skip contrib research.

Use when choosing between Drupal patterns (FormBase vs ListBuilder, Entity vs Config) - recommends patterns with core/contrib references. Trigger: 'which pattern should I use', 'FormBase vs ConfigForm', 'entity type selection', 'best approach for', 'Drupal pattern for'. ALWAYS recommend patterns with core/contrib references. NEVER recommend a pattern without showing a core example.

Use when checking project status or deciding next steps - reads memory files, manages tasks, suggests actions, routes to appropriate agents/skills. Trigger: 'project status', 'what should I do next', 'which task', 'resume project', 'start working', 'continue'. ALWAYS route through 3-phase workflow (Research → Architecture → Implementation). NEVER skip phases. ALWAYS check quality gates before marking tasks complete.

Use before committing code - validates Drupal coding standards, SOLID/DRY principles, security practices, and CSS standards. Trigger: 'check code quality', 'pre-commit check', 'lint Drupal code', 'validate standards'. Use proactively before ANY commit. Checks SOLID, DRY, security, and Drupal coding standards.

Use when designing a specific module component - creates architecture/component_name.md with purpose, interface, dependencies, and pattern references

Use when needing Drupal core implementation examples - searches core modules for specific patterns and returns file path references

Use when visualizing architecture - generates Mermaid diagrams for data flow, service relationships, or entity structures. Trigger: 'draw diagram', 'visualize', 'show relationships', 'mermaid chart'.

Use when designing features - loads plugin methodology refs and delegates to dev-guides-navigator for online Drupal domain knowledge. Trigger: 'load guides', 'get reference docs', 'methodology references'. Use proactively during Phase 2 design — loads SOLID, Library-First, DRY, TDD, Security guides.

4 hooks across 4 events