Loads task context including architecture files, referenced patterns, guides, and phase files (task.md, research.md, etc.) when starting implementation.
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.
Guides agentic engineering workflows: eval-first loops, 15-min task decomposition, model routing (Haiku/Sonnet/Opus), AI code reviews, and cost tracking.
Load all context needed before implementing a task.
!ls implementation_process/in_progress/ 2>/dev/null
Activate when you detect:
/drupal-dev-framework:implement <task> commandGet project path from project_state.md. Find the task:
v3.0.0 Folder Structure:
implementation_process/in_progress/{task}/ for task directorytask.md file existsv2.x Single File (backward compatibility):
implementation_process/in_progress/{task}.md for single fileIf neither exists, offer to create one using the Skill tool to invoke implementation-task-creator (it is a skill, not an agent)
Use Read tool to load:
{project_path}/architecture/main.md
{project_path}/architecture/{component}.md (if exists)
Extract from architecture:
v3.0.0 Folder Structure:
Load all relevant phase files:
Load task.md (tracker):
Use `Read` on `{task}/task.md`
Extract:
Load research.md (if exists):
Use `Read` on `{task}/research.md`
Context from Phase 1 research
Load architecture.md (if exists):
Use `Read` on `{task}/architecture.md`
Extract:
Load implementation.md (if exists):
Use `Read` on `{task}/implementation.md`
Extract:
v2.x Single File (backward compatibility):
Use Read on {task}.md and extract all sections
From architecture files, find pattern references like:
Based on: core/modules/.../src/...
Use Read to load the referenced core files. Extract:
If project_state.md has a guides path, invoke guide-loader skill for relevant guides.
Format output as:
## Ready to Implement: {Task Name}
### Objective
{from task file}
### Architecture Summary
{key points from architecture}
### Pattern Reference
{primary core file}:
- Key methods to follow: {list}
- Dependencies to inject: {list}
### TDD Approach
1. Test file: {path}
2. First test: {what to test}
### Files to Create/Modify
- {file 1}: {what to do}
- {file 2}: {what to do}
### Acceptance Criteria
- [ ] {criterion 1}
- [ ] {criterion 2}
### Dependencies
Complete these first:
- {prerequisite task, if any}
---
Ready to write the first test?
After presenting context, remind:
TDD reminder: Write test first, then implement.
Use superpowers:test-driven-development for detailed TDD guidance.
STOP and wait for user: