From tsk-add
Queues a single task from conversation using `tsk add`. Summarizes discussions into templated prompts with task names for asynchronous agent execution.
npx claudepluginhub dtormoen/tsk-tsk --plugin tsk-addThis skill is limited to using the following tools:
You are helping the user queue a task based on the conversation you just had. The user has been discussing a design, architecture decision, or code change with you, and now wants to queue it as an asynchronous task.
Provides documentation on tsk CLI for delegating dev tasks to AI agents in Docker/Podman containers, running interactive shells, managing task queues/servers, and creating git branches.
Adds actionable tasks to TASKS.md for follow-up work or subtasks using ctx bash tool. Validates specificity, priority, uniqueness, and actionability before recording.
Creates taskmd task files via CLI: parses user input for title, template, flags like priority/tags/group; fills objective, subtasks, criteria; validates output. Use when adding project tasks.
Share bugs, ideas, or general feedback.
You are helping the user queue a task based on the conversation you just had. The user has been discussing a design, architecture decision, or code change with you, and now wants to queue it as an asynchronous task.
These are the task templates available for use with tsk add -t <template>:
!`tsk template list`
To see the full content of a template, run tsk template show <template>. When a task is created, the {{PROMPT}} placeholder in the template is replaced with whatever you pipe in via heredoc or pass via the -p flag, and any YAML frontmatter is stripped. The result is what gets sent to the agent.
Summarize the agreed-upon work: Review the conversation above and identify:
Create a task name: Come up with a short, branch-friendly name (e.g., add-auth, refactor-api, fix-validation)
Pick the best template: Based on the nature of the task, choose the template from the list above that best matches the work to be done (e.g., feat for new features, fix for bug fixes, refactor for restructuring, doc for documentation).
Write the task prompt: Create a clear, self-contained prompt that includes:
Queue the task: Use tsk add to create the task:
--prompt-filetsk add -t <template> -n "<task-name>" <<'EOF'
<task description>
EOF
# Alternatively:
tsk add -t <template> --prompt-file <path_to_the_plan>
-p flag. They do not work together.tsk add -t feat -n "add-rate-limiting" <<'EOF'
Add rate limiting to the API endpoints.
### Context
The API currently has no rate limiting, which could allow abuse. We discussed using a token bucket algorithm with Redis for distributed rate limiting.
### Requirements
- Add rate limiting middleware to all /api/* routes
- Use token bucket algorithm: 100 requests per minute per API key
- Store rate limit state in Redis (connection config already exists)
- Return 429 Too Many Requests with Retry-After header when limit exceeded
### Files to Focus On
- src/middleware/ - add new rate limiting middleware
- src/routes/api.ts - apply middleware to routes
- src/config/redis.ts - reuse existing Redis connection
### Acceptance Criteria
- Rate limiting works correctly under load
- Proper error responses with Retry-After header
- Tests cover rate limit enforcement and reset behavior
EOF
After queuing the task, remind the user they can run tsk server start if the server isn't already running.
tsk is installed and on the path. Here are the main commands:
!`tsk help`
Here are the options for adding tasks:
!`tsk add --help`