crafter-scaffold-task

Automating task file creation from a markdown template involves reading a canonical TASK.md file, deriving a YYYYMMDD-slug filename, and writing the standardized structure to a tasks directory. This scaffold skill enforces collision checks to prevent overwriting existing files during the task-lifecycle setup.

A task scaffold ensures consistent lifecycle structure by applying a canonical template that standardizes content into Metadata, verbatim Request, Plan placeholder, Decisions, and Outcome sections. It materializes new task files with uniform formatting to eliminate the inconsistency of hand-assembling task structures.

Preventing file collisions when generating task files requires validating the non-existence of the target path before writing. This scaffold derives the filename as YYYYMMDD-slug and performs collision checks against the resolved context directory to ensure no existing task files are overwritten.

Generated task files should be stored under the resolved context directory, preferring the .crafter/ folder or falling back to .planning/. The scaffold writes the newly created task file to the tasks/ subdirectory within this resolved context to maintain organized workflow automation.

The task scaffold does not require manual editing of the template structure because it reads templates/TASK.md to source the structure automatically. It fills the metadata and verbatim request while preserving the Plan placeholder, ensuring standardized content generation without manual assembly.

You can use this scaffold to generate tasks for any project context that supports the expected directory structure. It resolves the context directory dynamically and applies the canonical template to produce standardized task files, making it composable for agent-only task-lifecycle setups across different projects.