From drupal-dev-framework
Analyzes task directories and markdown files to determine development phase: 1-Research, 2-Architecture, 3-Implementation. Checks for task.md, research.md, architecture.md, implementation.md in project structure. Useful for task status and next actions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/drupal-dev-framework:phase-detectorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze a task file to determine its current development phase.
Analyze a task file to determine its current development phase.
Phases apply to TASKS, not projects. A project has requirements (gathered once), then contains multiple tasks. Each task independently progresses through phases.
Activate when:
project-orchestrator agent| Phase | Focus | Code? |
|---|---|---|
| 1 - Research | Understand requirements, research solutions | NO |
| 2 - Architecture | Design approach, patterns, decisions | NO |
| 3 - Implementation | Build with TDD, interactive coding | YES |
Get task name from:
Check for task directory at:
{project_path}/implementation_process/in_progress/{task_name}/
If not found, check:
{project_path}/implementation_process/completed/{task_name}/
If neither exists, check for v2.x single file (backward compatibility):
{project_path}/implementation_process/in_progress/{task_name}.md
{project_path}/implementation_process/completed/{task_name}.md
If nothing found, task hasn't started yet → Phase 0 (Not Started)
v3.0.0 Folder Structure:
Use Bash to check for phase files:
# Check which phase files exist
[ -f "{task_name}/task.md" ] && echo "tracker"
[ -f "{task_name}/research.md" ] && echo "research"
[ -f "{task_name}/architecture.md" ] && echo "architecture"
[ -f "{task_name}/implementation.md" ] && echo "implementation"
Then use Read on {task_name}/task.md to check:
Phase 1 Complete Indicators:
research.md file existsPhase 2 Complete Indicators:
architecture.md file existsPhase 3 Progress Indicators:
implementation.md file existsv2.x Single File (backward compatibility):
If single .md file found, check for sections:
## Research section exists → Phase 1 complete## Architecture section exists → Phase 2 complete## Implementation section exists → Phase 3 in progressTask file doesn't exist?
→ Phase 0: Not Started - "Create task and begin research"
Task file exists but no Research section?
→ Phase 1: Research - "Research this task"
Research complete but no Architecture section?
→ Phase 2: Architecture - "Design architecture for this task"
Architecture complete?
→ Phase 3: Implementation - "Implement this task"
All checkboxes complete?
→ Done - "Complete this task"
Format output as:
## Task Phase: {task_name}
**Phase:** {0/1/2/3} - {Not Started/Research/Architecture/Implementation}
**Status:** {Not Started/In Progress/Complete}
### Evidence
| Section | Found | Content |
|---------|-------|---------|
| Research | Yes/No | {summary or "Empty"} |
| Architecture | Yes/No | {summary or "Empty"} |
| Implementation | Yes/No | {progress or "Empty"} |
### Next Action
{What to do next for this task}
### Command
{Suggested command to run}
When checking overall project status, summarize all tasks:
## Project: {project_name}
### Requirements
{Complete / Not gathered}
### Task Summary
| Task | Phase | Status | Next Action |
|------|-------|--------|-------------|
| {task1} | 3 | In Progress | Continue implementation |
| {task2} | 1 | In Progress | Complete research |
| {task3} | 0 | Queued | Start research |
### Completed Tasks
- {task_a} ✓
- {task_b} ✓
| Situation | Handling |
|---|---|
| No task specified | List all tasks with their phases |
| Task not found | Offer to create it |
| Task in completed/ | Report as done |
| Multiple tasks in progress | Show all, ask which to focus on |
STOP if:
npx claudepluginhub camoa/claude-skills --plugin drupal-dev-frameworkDisplays project status, roadmap progress, blockers, and next-action suggestions based on workflow state. Use for progress checks and orientation.
Displays Plan-Build-Run project status dashboard, progress, blockers from .planning files, and suggests next actions.
Routes sessions in long-task projects to the correct phase skill by checking files like bugfix-request.json, feature-list.json, design docs, and codebase state.