plan-kanban-tasks
Skill66 starsChanged 58 days agoMITView on GitHub
Create a concise Product Development Requirement and one or more implementation-sized Kanban tasks when the user explicitly asks to plan or register work.
In this repository7 other files it gives its agents.
- kanban-workflowSkill
- plan-kanban-tasksSkill
- ralph-loopSkill
- understand-projectSkill
- kanban-workflowSkill
- ralph-loopSkill
- understand-projectSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the project instructions and relevant product code from the integration or feature worktree.
- Very specific: line 13
Create tasks through the controller's .juno_task/scripts/kanban.sh.
- Distinctive: line 15
Do not start implementation, create worktrees, push, deploy, or mutate production unless the user separately asks.
- Very specific: line 17
Use --id, not legacy --ID, for Kanban mutations.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plan Kanban work
- Read the project instructions and relevant product code from the integration or feature worktree. Read existing task/spec metadata through the canonical controller; do not assume
.juno_task/plan.mdexists. - Produce one concise PDR covering the goal, current behavior, scope, exclusions, risks, dependencies, acceptance criteria, and focused tests.
- Split only when pieces can be implemented and validated independently. Concurrent tasks must have explicit path ownership and dependencies.
- Create tasks through the controller's
.juno_task/scripts/kanban.sh. Put durable requirements and acceptance criteria in each task body; relate follow-ups instead of reopening archived IDs. - Store any durable specification through a controller-authorized metadata operation. Never create controller-private
.juno_task/specs, tasks, ledger, state, or receipts inside a product or feature worktree. - Do not start implementation, create worktrees, push, deploy, or mutate production unless the user separately asks.
Use --id, not legacy --ID, for Kanban mutations. Return the task IDs and a short dependency/order summary.
$ARGUMENTS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

