From drupal-dev-framework
Updates project_state.md, scans task directories via Bash, detects inconsistencies like empty/orphaned files, organizes structure after phase activities or task completion.
How this skill is triggered — by the user, by Claude, or both
Slash command
/drupal-dev-framework:memory-managerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Maintain clean and organized project memory.
Maintain clean and organized project memory.
Activate when:
Use Read on {project_path}/project_state.md
Extract:
v3.0.0 Folder Structure Support:
Use Bash with ls -d to inventory task directories:
# List task directories (not .md files)
ls -d {project_path}/implementation_process/in_progress/*/ 2>/dev/null
ls -d {project_path}/implementation_process/completed/*/ 2>/dev/null
For each task directory found, check for:
task.md (main tracker) - requiredresearch.md (Phase 1 content) - optionalarchitecture.md (Phase 2 content) - optionalimplementation.md (Phase 3 content) - optionalAlso scan architecture folder:
{project_path}/architecture/*.md
Count:
Backward Compatibility:
If *.md files found (not directories), warn:
⚠️ Old v2.x format detected: {count} single-file tasks
Run `/drupal-dev-framework:migrate-tasks` to upgrade to v3.0.0 folder structure.
Check for issues:
| Issue | Detection | Fix |
|---|---|---|
| Empty files | File size = 0 | Ask to delete or populate |
| Orphaned tasks | Task in wrong folder | Move to correct location |
| Stale state | project_state.md outdated | Update current focus |
| Missing files | Referenced but not found | Create or update reference |
Use Edit to update:
# {Project Name}
**Updated:** {today's date}
**Phase:** {detected phase}
**Status:** {current status}
**Path:** {project_path}
## Overview
{Keep existing or update based on recent work}
## Progress
- Phase 1 (Research): {Complete/In Progress} - {count} research files
- Phase 2 (Architecture): {Complete/In Progress} - {count} component files
- Phase 3 (Implementation): {X}/{Y} tasks complete
## Current Focus
{What's actively being worked on}
## Key Decisions
| Date | Decision | Rationale |
|------|----------|-----------|
{add new decisions, keep old ones}
## Next Steps
1. {Immediate next action}
2. {Following action}
If files are misplaced, use Bash to move:
v3.0.0 Folder Structure:
# Move completed task directory from in_progress
mv "{project_path}/implementation_process/in_progress/{task_name}/" \
"{project_path}/implementation_process/completed/{task_name}/"
v2.x Single Files (backward compatibility):
# Move completed task file from in_progress
mv "{project_path}/implementation_process/in_progress/{task_name}.md" \
"{project_path}/implementation_process/completed/{task_name}.md"
Ask before deleting anything:
Found {count} empty/orphaned files:
- {file 1}
- {file 2}
Delete these? (yes/no/review each)
Update the registry at ~/.claude/drupal-dev-framework/active_projects.json:
lastAccessed: today's datestatus: "active" or "archived" if all tasks completeIf project not in registry, offer to add it:
This project is not in the registry.
Add it for easier access next time? (yes/no)
Show summary:
Memory cleanup complete:
Files scanned: {count}
Issues found: {count}
Issues fixed: {count}
Current state:
- Phase: {phase}
- Architecture files: {count}
- Tasks in progress: {count}
- Tasks completed: {count}
project_state.md updated.
Registry updated.
Follow these rules:
STOP and wait for user:
npx claudepluginhub camoa/claude-skills --plugin drupal-dev-frameworkResumes work on existing projects: lists from registry JSON, reads project_state.md for state summary and phase, scans in-progress tasks, suggests next actions. Triggers: 'pick up where I left off'.
Sync tracking documents based on current conversation results. Updates subtask, progress, findings, task_plan, project CLAUDE.md. Use when finishing a task or reaching a milestone.
Organizes, extracts, prunes, and verifies Claude Code persistent memory files to keep MEMORY.md under the 200-line truncation limit and topic files up to date with project state.