task-folder-migrator

The Task Folder Migrator is a specialized utility designed for the drupal-dev-framework, facilitating the transition from legacy v2.x single-file task documentation to the modern, modular v3.0.0 folder-based project structure. It serves as an essential bridge for developers maintaining ongoing Drupal projects, ensuring project context remains organized as requirements grow in complexity. By automating the parsing of markdown headers like Research, Architecture, and Implementation, it maintains data integrity while enhancing the discoverability of task-related artifacts. The skill identifies orphaned task files, creates corresponding directories, and splits content into distinct task.md, research.md, architecture.md, and implementation.md files, significantly reducing manual cleanup time.

• Automatically detects and migrates legacy .md task files into standardized project directories.

• Features dual-mode operation: fully autonomous background migration for seamless pipeline integration or interactive manual mode with detailed migration planning.

• Preserves data fidelity by creating mandatory .bak backups of original files before directory restructuring.

• Supports intelligent content parsing that extracts Goal, Acceptance Criteria, Related Tasks, and Notes sections based on established markdown conventions.

• Integrates directly with project-orchestrator agents to identify v2.x project states dynamically.

• Enables consistent project state tracking, making it easier to navigate complex development cycles, particularly when transitioning to phase-based editorial workflows.

• Intended for developers managing Drupal modules, themes, or multi-phase implementation projects.

• Requires the drupal-dev-framework environment to correctly interpret project state and pathing.

• Handles edge cases such as empty sections, missing content, and existing backup collisions through robust renaming strategies (e.g., appending timestamps).

• Prior to execution, ensure the project root or relevant task directory is accessible to the agent to avoid permission errors or path resolution failures.

• Verify migration results via the post-process report generated upon completion, which summarizes successfully converted tasks and links to their new file locations.