Stats
Actions
Tags
From task-queuer
Inject a section describing the task-queuer system, its folder structure, and conventions into the repo's CLAUDE.md so future agents find and use it. Use after init-queue, or when the user asks to register/document the task queue in CLAUDE.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/task-queuer:document-queueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Add or refresh a `## Task Queue` section in the repo's `CLAUDE.md` so any Claude Code agent opened in this repo immediately knows the queue exists, where tasks live, and how to use them.
Add or refresh a ## Task Queue section in the repo's CLAUDE.md so any Claude Code agent opened in this repo immediately knows the queue exists, where tasks live, and how to use them.
Locate CLAUDE.md at the repo root. If it doesn't exist, create a minimal one (project name as H1, one-line description placeholder, then the queue section).
Verify planning/ exists. If it doesn't, tell the user to run init-queue first and stop.
Insert or replace the ## Task Queue section with the block below. If a section with that heading already exists, replace its body; don't duplicate.
Use relative paths (e.g. planning/tasks/in-queue/), never absolute.
## Task Queue
This repo uses the **task-queuer** plugin. Planning artefacts live under `planning/`:
- `planning/logs/` — session/work logs
- `planning/bug-reports/` — standalone bug reports
- `planning/project-decisions/` — architectural and product decisions
- `planning/tasks/in-queue/<category>/` — tasks ready to be picked up
- `planning/tasks/holding/<category>/` — deferred or blocked tasks
- `planning/tasks/done/<category>/` — completed tasks (archive)
Categories: `bug-resolution`, `frontend`, `backend`, `css`, `misc`.
### Conventions
- New tasks are markdown files named `YYYY-MM-DD-<slug>.md` with frontmatter: `title`, `category`, `priority` (`high|medium|low`), `created`, `status`.
- Move a task between `in-queue/`, `holding/`, and `done/` by relocating the file — don't rewrite its path into the frontmatter.
- Bucketed/merged tasks written by the curator live under `planning/tasks/in-queue/<category>/` and reference their source tasks in a `merged_from:` frontmatter list.
### Plugin commands
- `/task-queuer:add-task` — file a new task
- `task-queuer:init-queue` — (re)scaffold `planning/`
- `task-queuer:task-curator` — categorise + prioritise the backlog and hand off to the repo's orchestration agent
npx claudepluginhub danielrosehill/claude-code-plugins --plugin task-queuerCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.