From drupal-dev-framework
Enforces 5 quality gates (code standards, tests, architecture, security) before completing tasks, moves to completed/, updates project_state.md, suggests next task. Blocks on failures.
How this skill is triggered — by the user, by Claude, or both
Slash command
/drupal-dev-framework:task-completerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Finalize tasks and update project memory.
Finalize tasks and update project memory.
Load before completing any task:
| Reference | Enforces |
|---|---|
references/quality-gates.md | Gates 2, 3, 4 (must ALL pass) |
| dev-guides: https://camoa.github.io/dev-guides/drupal/security/ | Gate 4 security review |
Activate when you detect:
/drupal-dev-framework:complete commandTask CANNOT be completed until ALL gates pass:
| Gate | Check | Blocking? |
|---|---|---|
| Gate 1 | Code standards (invoke code-pattern-checker) | YES |
| Gate 2 | Tests pass (user confirms) | YES |
| Gate 3 | Architecture compliance | YES |
| Gate 4 | Security review | YES |
Use Read on the task file: {project_path}/implementation_process/in_progress/{task}.md
Check each acceptance criterion. Ask user:
Completion checklist for {task_name}:
Acceptance Criteria:
- [ ] {criterion 1} - Is this done?
- [ ] {criterion 2} - Is this done?
- [ ] {criterion 3} - Is this done?
Confirm all acceptance criteria are met (yes/no):
If NO, identify what's remaining and continue working.
ALL gates must pass before completion:
Invoke code-pattern-checker skill on modified files.
\Drupal::service() in new codeAsk user to confirm:
Tests verification (user must run):
ddev phpunit {test_path}
- [ ] All existing tests pass?
- [ ] New code has test coverage?
- [ ] No skipped tests without documented reason?
Confirm tests pass (yes/no):
Check against architecture/main.md:
https://camoa.github.io/dev-guides/drupal/security/ for detailed security guidanceIf ANY blocking gate fails: Task completion is BLOCKED. Fix issues first.
Use Edit to add completion section to the task file:
---
## Completion
**Completed:** {YYYY-MM-DD}
**Final Status:** Complete
### Summary
{Brief description of what was implemented}
### Files Changed
| File | Action |
|------|--------|
| src/... | Created |
| tests/... | Created |
| *.services.yml | Modified |
### Test Results
- Unit tests: {count} passing
- Kernel tests: {count} passing
- Total: All passing
### Notes
{Any implementation notes, deviations, or decisions made}
Use Bash to move the task:
mv "{project_path}/implementation_process/in_progress/{task}.md" "{project_path}/implementation_process/completed/{task}.md"
Use Edit to update:
## Progress
### Completed Tasks
| Task | Completed | Notes |
|------|-----------|-------|
| {task_name} | {date} | {one-line summary} |
## Current Focus
{Update to next task or "Ready for next component"}
Use Glob to find remaining tasks:
{project_path}/implementation_process/in_progress/*.md
Analyze dependencies and priorities. Present:
Task complete: {task_name}
Next task options:
1. {next_task} - {reason: dependency unblocked / priority}
2. {alternative} - {reason}
3. No more tasks - component complete
Which task next? (1/2/3 or other):
If this was the last task for a component, suggest:
Component {name} appears complete.
Run final validation?
- superpowers:verification-before-completion
- Full test suite
- Integration tests
Proceed? (yes/no)
STOP and wait for user:
npx claudepluginhub camoa/claude-skills --plugin drupal-dev-frameworkOrchestrates task lists with documentation-first execution, sequential progress tracking, quality checklists, and user confirmations. Use for multi-step implementations and feature development.
Marks tasks as completed after verifying subtasks, acceptance criteria, optional verify checks (bash/assert), and worklogs. Handles solo and PR-review workflows.
Executes tasks from TASK_N.md files or free-form descriptions, auto-generating missing scope, success criteria, and verification plans via /generate-tasks before implementation.