ck:project-organization

Standardize project directory structure by enforcing consistent top-level categories for code, docs, plans, and assets, while applying kebab-case slugs and timestamped patterns for predictable file paths.

Reorganize existing project files safely by scanning target paths, proposing a migration plan with conflict-safe behavior, confirming changes before execution, and validating the final structure without overwriting protected files.

Enforce consistent markdown templates for documentation by applying standardized body formats for plans, phases, reports, journals, specs, ADRs, changelogs, and guides to ensure predictable formatting.

Automate file migration plans for repository hygiene by scanning target directories for inconsistencies and generating a before-and-after file structure migration plan that confirms changes before executing moves or renames.

Use kebab-case slugs combined with timestamped, evergreen, or variant naming patterns for project organization to achieve predictable paths and maintain strict repository hygiene across all assets.

This project organization approach works for both new files and existing assets by applying enforced category rules to creating new files, determining output paths, and reorganizing current documentation, scripts, and media.