Creates task files breaking down PHP/Drupal components into TDD steps with acceptance criteria, loaded from architecture docs. Use for implementation planning from phase 2 to 3.
From drupal-dev-frameworknpx claudepluginhub camoa/claude-skills --plugin drupal-dev-frameworkThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Create task files that break down components into implementable TDD steps.
Activate when you detect:
Use Read on {project_path}/architecture/{component}.md
If file doesn't exist, ask: "No architecture found for {component}. Create architecture first?"
Extract:
Ask user:
How should this component be broken down?
1. Single task (small component)
2. Multiple tasks by method/feature
3. Multiple tasks by layer (test, implementation, integration)
Your choice:
Based on dependencies, determine implementation order. Ask:
Proposed task order:
1. {task 1} - {why first}
2. {task 2} - {depends on 1}
3. {task 3} - {depends on 2}
Adjust order? (yes/no)
For each task, use Write to create {project_path}/implementation_process/in_progress/{nn}_{task_name}.md:
# Task: {Task Name}
**Component:** {component name}
**Created:** {YYYY-MM-DD}
**Status:** Not Started
**Priority:** {nn}
## Objective
{What this task accomplishes - one paragraph}
## Prerequisites
- [ ] {Task that must be complete first, or "None"}
## Acceptance Criteria
- [ ] {Criterion 1 - specific and testable}
- [ ] {Criterion 2}
- [ ] {Criterion 3}
- [ ] All tests pass
- [ ] Code follows Drupal standards
## TDD Steps
### Step 1: Write Failing Test
Create test file:
tests/src/{Unit|Kernel}/{TestClass}Test.php
Test case:
```php
public function test{MethodName}(): void {
// Arrange: {setup}
// Act: {action}
// Assert: {expected result}
}
Run: ddev phpunit {test_path}
Expected: Test fails (class/method not found)
Create: src/{Type}/{ClassName}.php
Implement only enough to pass the test.
Run: ddev phpunit {test_path}
Expected: Test passes
Clean up code while keeping tests green.
| File | Action | Purpose |
|---|---|---|
src/{path} | Create | Main implementation |
tests/src/{path} | Create | Test coverage |
*.services.yml | Modify | Service registration |
Follow: {core path from architecture}
Key aspects:
{Any specific considerations from architecture}
### 5. Update project_state.md
Use `Edit` to update the project state:
```markdown
## Current Focus
Implementation Phase - {component name}
## Next Steps
1. Complete task: {first task name}
Show user:
Created {count} task(s) for {component}:
1. {task 1} - in_progress/{filename}
2. {task 2} - in_progress/{filename}
Start with task 1? Use: /drupal-dev-framework:implement {task_name}
STOP and wait for user: