init-queue

name	init-queue
description	Scaffold the task-queuer planning/ folder in the current repo — creates logs, bug-reports, project-decisions, and tasks/{in-queue,holding,done} with category subfolders (bug-resolution, frontend, backend, css, misc). Use when the user asks to set up the task queue, initialise planning, or add task-queuer to this repo.

Initialise the Task Queue

Scaffold a planning/ directory tree at the root of the current repository. This is the on-disk structure the task-queuer plugin operates on.

Steps

1. Determine the target root. Use the current working directory. If it is not a git repository, confirm with the user before scaffolding.

2. Check existing state. If planning/ already exists, do not overwrite. List what is present and what is missing, then create only the missing directories.

3. Create the directory tree. The full structure is:

   planning/
   ├── logs/
   ├── bug-reports/
   ├── project-decisions/
   └── tasks/
       ├── in-queue/
       │   ├── bug-resolution/
       │   ├── frontend/
       │   ├── backend/
       │   ├── css/
       │   └── misc/
       ├── holding/
       │   ├── bug-resolution/
       │   ├── frontend/
       │   ├── backend/
       │   ├── css/
       │   └── misc/
       └── done/
           ├── bug-resolution/
           ├── frontend/
           ├── backend/
           ├── css/
           └── misc/
   

4. Seed .gitkeep files in every leaf directory so the empty tree commits cleanly.

5. Write planning/README.md with a short description of each folder's purpose:

   • logs/ — dated session or work logs
   • bug-reports/ — standalone bug reports (distinct from actionable bug-resolution tasks)
   • project-decisions/ — architectural/product decisions and rationale
   • tasks/in-queue/ — tasks ready to be picked up, grouped by category
   • tasks/holding/ — tasks deferred or blocked
   • tasks/done/ — completed tasks (archive)

6. Report to the user what was created and suggest running the document-queue skill next to register the system in CLAUDE.md.

Category conventions

The five default category subfolders under each of in-queue, holding, done:

• bug-resolution/ — fixes for identified bugs
• frontend/ — UI, client-side logic
• backend/ — server, API, data
• css/ — styling-only changes
• misc/ — anything uncategorised; also the landing zone for unsorted backlog items

If a repo has clearly different domain slices (e.g. mobile/, infra/, docs/), the user may extend the category list — preserve misc/ as the catch-all.