juno-code 1.0.49 → 1.0.51

package/dist/templates/skills/claude/kanban-workflow/SKILL.md

@@ -0,0 +1,138 @@
+---
+name: kanban-workflow
+description: Comprehensive guide for using juno-kanban task management. Covers all commands (create, list, search, get, mark, update, archive, deps, ready, order, merge), dependency management, best practices, and workflow patterns. Use when you need to interact with the kanban board.
+argument-hint: "[command or workflow question]"
+---
+
+## Kanban CLI Reference
+
+All commands use `./.juno_task/scripts/kanban.sh` (wrapper around juno-kanban Python CLI).
+
+### Core Commands
+
+**CREATE** — Add a new task
+```bash
+./.juno_task/scripts/kanban.sh create "Task description here" --status backlog --tags feature,backend
+```
+Options: `--status` (backlog|todo|in_progress|done), `--tags` (comma/space-separated), `--blocked-by` (task IDs), `--related-tasks` (task IDs)
+
+**LIST** — Browse tasks with summary stats
+```bash
+./.juno_task/scripts/kanban.sh list --limit 5 --sort asc
+./.juno_task/scripts/kanban.sh list --status todo --sort asc
+./.juno_task/scripts/kanban.sh list --status todo,in_progress --limit 10
+```
+
+**SEARCH** — Find tasks by criteria
+```bash
+./.juno_task/scripts/kanban.sh search --status todo --tag backend --limit 10
+./.juno_task/scripts/kanban.sh search --body "OAuth" --open
+./.juno_task/scripts/kanban.sh search --commit abc123
+```
+Filters: `--status`, `--tag`, `--body`, `--response`, `--commit`, `--open` (no agent_response), `--recent`, `--exclude` (exclude tags)
+
+**GET** — Full task details (including dependency info and related task details)
+```bash
+./.juno_task/scripts/kanban.sh get TASK_ID
+```
+
+**MARK** — Update status with required response message
+```bash
+./.juno_task/scripts/kanban.sh mark in_progress --id TASK_ID --response "Starting work on this"
+./.juno_task/scripts/kanban.sh mark done --id TASK_ID --response "Completed: implemented X, tested Y" --commit abc123def
+./.juno_task/scripts/kanban.sh mark todo --id TASK_ID --response "Reopening: found regression"
+```
+Required: `--id` and `--response`. Optional: `--commit` (recommended for done).
+
+**UPDATE** — Modify task fields
+```bash
+./.juno_task/scripts/kanban.sh update TASK_ID --status todo --tags backend,urgent
+./.juno_task/scripts/kanban.sh update TASK_ID --commit abc123def
+./.juno_task/scripts/kanban.sh update TASK_ID --response "Additional context"
+```
+
+**ARCHIVE** — Soft delete (preserves data, sets status to archive)
+```bash
+./.juno_task/scripts/kanban.sh archive TASK_ID
+```
+
+### Dependency Management
+
+**DEPS** — View, add, or remove task dependencies
+```bash
+# View dependency info (blockers, dependents, priority score)
+./.juno_task/scripts/kanban.sh deps TASK_ID
+
+# Add blockers (TASK_ID cannot start until BLOCKER1 and BLOCKER2 are done)
+./.juno_task/scripts/kanban.sh deps add --id TASK_ID --blocked-by BLOCKER1 BLOCKER2
+
+# Remove a blocker
+./.juno_task/scripts/kanban.sh deps remove --id TASK_ID --blocked-by BLOCKER1
+```
+Cycle detection prevents circular dependencies automatically.
+
+**READY** — Tasks with all blockers satisfied (safe to work on)
+```bash
+./.juno_task/scripts/kanban.sh ready
+./.juno_task/scripts/kanban.sh ready --tag backend --limit 5
+```
+Returns tasks where status is backlog/todo/in_progress AND all `blocked_by` tasks are done/archive.
+
+**ORDER** — Topological sort of open tasks respecting dependencies
+```bash
+./.juno_task/scripts/kanban.sh order
+./.juno_task/scripts/kanban.sh order --scores
+```
+Use for determining safe parallel execution order.
+
+### Body Markup for Inline Dependencies
+
+Declare dependencies and relations directly in task body text:
+
+```
+[blocked_by]TASK_ID[/blocked_by]          — This task is blocked by TASK_ID
+[blocked_by]ID1, ID2[/blocked_by]         — Blocked by multiple tasks
+[task_id]RELATED_ID[/task_id]             — Reference a related task
+[task_id]ID1 ID2[/task_id]                — Multiple related tasks
+```
+
+These are parsed automatically when the task is created/updated.
+
+### Merge (Multi-Directory Consolidation)
+
+When tasks get scattered across subdirectories:
+```bash
+# Auto-discover and merge all .juno_task dirs
+./.juno_task/scripts/kanban.sh merge --find-all --into ./.juno_task --dry-run
+
+# Merge specific sources
+./.juno_task/scripts/kanban.sh merge ./sub1/.juno_task ./sub2/.juno_task --into ./.juno_task
+```
+Strategy: `--strategy keep-newer` (default) or `--strategy keep-both`.
+
+### Output Formats
+
+All commands support: `-f json`, `-f ndjson` (default), `-f xml`, `-f table`
+Add `--raw` for compact output. Add `-p` for pretty print.
+
+### Best Practices
+
+1. **Task sizing**: Create tasks small enough to complete in one iteration without filling the context window
+2. **Status flow**: backlog → todo → in_progress → done (or archive for abandoned tasks)
+3. **Always include `--response`** when using `mark` — document what you did and how you tested it
+4. **Attach commits**: Use `--commit HASH` when marking done, then `update TASK_ID --commit HASH` to link the git history
+5. **Use `ready`** before starting work to find unblocked tasks
+6. **Use `order --scores`** to plan parallel execution pipelines
+7. **Use `[blocked_by]` markup** in task body when creating tasks that depend on others
+8. **Use `[task_id]` markup** in task body to cross-reference related tasks
+9. **Use `get TASK_ID`** to see full task details including resolved dependency and related task info
+10. **One task in_progress at a time** — finish or re-queue before starting the next
+
+### Environment Variables
+
+- `JUNO_TASK_ROOT` — Pin kanban operations to a specific project root directory
+- `JUNO_DEBUG=true` — Show diagnostic messages
+- `JUNO_VERBOSE=true` — Show informational messages
+- `JUNO_KANBAN_LIST_BODY_TRUNCATE_CHARS=N` — Override list body truncation (default: 1200)
+
+$ARGUMENTS

package/dist/templates/skills/claude/plan-kanban-tasks/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: plan-kanban-tasks
 description: Generate Product Development Requirments(PDR) and create task on kanban. Use when user explictly ask for, or ask for creating a task, planing a feature, register a task on kaban. "Generate PDR"
-argument-hint: [Required Features] [Constraints] [Specification] [Test Criteria]
+argument-hint: "[Required Features] [Constraints] [Specification] [Test Criteria]"
 enable-shell-directives: true
 ---
 

package/dist/templates/skills/claude/ralph-loop/scripts/kanban.sh

@@ -190,6 +190,17 @@ fi
 # Change to project root
 cd "$PROJECT_ROOT"
 
+# Export JUNO_TASK_ROOT so juno-kanban resolves .juno_task paths from project root,
+# not from wherever the calling agent happens to be. Respects existing override.
+export JUNO_TASK_ROOT="${JUNO_TASK_ROOT:-$PROJECT_ROOT}"
+
+# Prefer local juno_kanban source when available (monorepo development).
+# This keeps wrapper behavior aligned with working-tree changes without requiring
+# immediate reinstall from PyPI between local iterations.
+if [[ -d "$PROJECT_ROOT/juno_kanban/src" ]]; then
+    export PYTHONPATH="$PROJECT_ROOT/juno_kanban/src${PYTHONPATH:+:$PYTHONPATH}"
+fi
+
 # Arrays to store normalized arguments (declared at script level for proper handling)
 declare -a NORMALIZED_GLOBAL_FLAGS=()
 declare -a NORMALIZED_COMMAND_ARGS=()

package/dist/templates/skills/claude/understand-project/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: understand-project
 description: Understand current project and create/update specs under @.juno_task/specs/* , it allows you understand dependencies. and prepare for implementation. Use when user explicitly ask you, or when asking for understand the project, first see how it works and then do [main task] with respect to [constraints]
-argument-hint: [Main Task] [Constraints] [Ultimate Goal]
+argument-hint: "[Main Task] [Constraints] [Ultimate Goal]"
 enable-shell-directives: true
 ---
 

package/dist/templates/skills/codex/kanban-workflow/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: kanban-workflow
+description: Comprehensive guide for using juno-kanban task management. Covers all commands (create, list, search, get, mark, update, archive, deps, ready, order, merge), dependency management, best practices, and workflow patterns. Use when you need to interact with the kanban board.
+argument-hint: "[command or workflow question]"
+enable-shell-directives: true
+---
+
+## Kanban CLI Reference
+
+All commands use `./.juno_task/scripts/kanban.sh` (wrapper around juno-kanban Python CLI).
+
+### Core Commands
+
+**CREATE** — Add a new task
+```bash
+./.juno_task/scripts/kanban.sh create "Task description here" --status backlog --tags feature,backend
+```
+Options: `--status` (backlog|todo|in_progress|done), `--tags` (comma/space-separated), `--blocked-by` (task IDs), `--related-tasks` (task IDs)
+
+**LIST** — Browse tasks with summary stats
+```bash
+./.juno_task/scripts/kanban.sh list --limit 5 --sort asc
+./.juno_task/scripts/kanban.sh list --status todo --sort asc
+./.juno_task/scripts/kanban.sh list --status todo,in_progress --limit 10
+```
+
+**SEARCH** — Find tasks by criteria
+```bash
+./.juno_task/scripts/kanban.sh search --status todo --tag backend --limit 10
+./.juno_task/scripts/kanban.sh search --body "OAuth" --open
+./.juno_task/scripts/kanban.sh search --commit abc123
+```
+Filters: `--status`, `--tag`, `--body`, `--response`, `--commit`, `--open` (no agent_response), `--recent`, `--exclude` (exclude tags)
+
+**GET** — Full task details (including dependency info and related task details)
+```bash
+./.juno_task/scripts/kanban.sh get TASK_ID
+```
+
+**MARK** — Update status with required response message
+```bash
+./.juno_task/scripts/kanban.sh mark in_progress --id TASK_ID --response "Starting work on this"
+./.juno_task/scripts/kanban.sh mark done --id TASK_ID --response "Completed: implemented X, tested Y" --commit abc123def
+./.juno_task/scripts/kanban.sh mark todo --id TASK_ID --response "Reopening: found regression"
+```
+Required: `--id` and `--response`. Optional: `--commit` (recommended for done).
+
+**UPDATE** — Modify task fields
+```bash
+./.juno_task/scripts/kanban.sh update TASK_ID --status todo --tags backend,urgent
+./.juno_task/scripts/kanban.sh update TASK_ID --commit abc123def
+./.juno_task/scripts/kanban.sh update TASK_ID --response "Additional context"
+```
+
+**ARCHIVE** — Soft delete (preserves data, sets status to archive)
+```bash
+./.juno_task/scripts/kanban.sh archive TASK_ID
+```
+
+### Dependency Management
+
+**DEPS** — View, add, or remove task dependencies
+```bash
+# View dependency info (blockers, dependents, priority score)
+./.juno_task/scripts/kanban.sh deps TASK_ID
+
+# Add blockers (TASK_ID cannot start until BLOCKER1 and BLOCKER2 are done)
+./.juno_task/scripts/kanban.sh deps add --id TASK_ID --blocked-by BLOCKER1 BLOCKER2
+
+# Remove a blocker
+./.juno_task/scripts/kanban.sh deps remove --id TASK_ID --blocked-by BLOCKER1
+```
+Cycle detection prevents circular dependencies automatically.
+
+**READY** — Tasks with all blockers satisfied (safe to work on)
+```bash
+./.juno_task/scripts/kanban.sh ready
+./.juno_task/scripts/kanban.sh ready --tag backend --limit 5
+```
+Returns tasks where status is backlog/todo/in_progress AND all `blocked_by` tasks are done/archive.
+
+**ORDER** — Topological sort of open tasks respecting dependencies
+```bash
+./.juno_task/scripts/kanban.sh order
+./.juno_task/scripts/kanban.sh order --scores
+```
+Use for determining safe parallel execution order.
+
+### Body Markup for Inline Dependencies
+
+Declare dependencies and relations directly in task body text:
+
+```
+[blocked_by]TASK_ID[/blocked_by]          — This task is blocked by TASK_ID
+[blocked_by]ID1, ID2[/blocked_by]         — Blocked by multiple tasks
+[task_id]RELATED_ID[/task_id]             — Reference a related task
+[task_id]ID1 ID2[/task_id]                — Multiple related tasks
+```
+
+These are parsed automatically when the task is created/updated.
+
+### Merge (Multi-Directory Consolidation)
+
+When tasks get scattered across subdirectories:
+```bash
+# Auto-discover and merge all .juno_task dirs
+./.juno_task/scripts/kanban.sh merge --find-all --into ./.juno_task --dry-run
+
+# Merge specific sources
+./.juno_task/scripts/kanban.sh merge ./sub1/.juno_task ./sub2/.juno_task --into ./.juno_task
+```
+Strategy: `--strategy keep-newer` (default) or `--strategy keep-both`.
+
+### Output Formats
+
+All commands support: `-f json`, `-f ndjson` (default), `-f xml`, `-f table`
+Add `--raw` for compact output. Add `-p` for pretty print.
+
+### Best Practices
+
+1. **Task sizing**: Create tasks small enough to complete in one iteration without filling the context window
+2. **Status flow**: backlog → todo → in_progress → done (or archive for abandoned tasks)
+3. **Always include `--response`** when using `mark` — document what you did and how you tested it
+4. **Attach commits**: Use `--commit HASH` when marking done, then `update TASK_ID --commit HASH` to link the git history
+5. **Use `ready`** before starting work to find unblocked tasks
+6. **Use `order --scores`** to plan parallel execution pipelines
+7. **Use `[blocked_by]` markup** in task body when creating tasks that depend on others
+8. **Use `[task_id]` markup** in task body to cross-reference related tasks
+9. **Use `get TASK_ID`** to see full task details including resolved dependency and related task info
+10. **One task in_progress at a time** — finish or re-queue before starting the next
+
+### Environment Variables
+
+- `JUNO_TASK_ROOT` — Pin kanban operations to a specific project root directory
+- `JUNO_DEBUG=true` — Show diagnostic messages
+- `JUNO_VERBOSE=true` — Show informational messages
+- `JUNO_KANBAN_LIST_BODY_TRUNCATE_CHARS=N` — Override list body truncation (default: 1200)
+
+$ARGUMENTS

package/dist/templates/skills/codex/plan-kanban-tasks/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: plan-kanban-tasks
+description: Generate Product Development Requirments(PDR) and create task on kanban. Use when user explictly ask for, or ask for creating a task, planing a feature, register a task on kaban. "Generate PDR"
+argument-hint: "[Required Features] [Constraints] [Specification] [Test Criteria]"
+enable-shell-directives: true
+---
+
+Ultrathink for this task
+First task is to study @.juno_task/plan.md (it may be incorrect)
+and study what is needed to achieve the main task.
+
+Second Task is to understand the task, create a spec for process to follow, plan to execute, scripts to create, virtual enviroment that we need, things that we need to be aware of, how to test the scripts and follow progress.
+Think hard and plan/create spec for every step of this task
+and for each part create a seperate .md file under @.juno_task/specs/\*
+
+## Task 2
+
+Update @.juno_task/plan.md with the new specs and Requirments.
+
+## Part 3
+
+Create PDR on kanban, kanban is available in @.juno_task/scripts/kanban.sh
+In the task body, include requirments, success criteria, test scenarios and jobs to be done.
+For each chunk of the required feature create a seperate task, we want tasks, small enough to be done in one iteration, without compacting context window.
+
+### Specs
+
+Current state of specs under @.juno_task/specs/
+
+!`ls -lrt .juno_task/specs/`
+
+$ARGUMENTS

package/dist/templates/skills/codex/ralph-loop/scripts/kanban.sh

@@ -190,6 +190,17 @@ fi
 # Change to project root
 cd "$PROJECT_ROOT"
 
+# Export JUNO_TASK_ROOT so juno-kanban resolves .juno_task paths from project root,
+# not from wherever the calling agent happens to be. Respects existing override.
+export JUNO_TASK_ROOT="${JUNO_TASK_ROOT:-$PROJECT_ROOT}"
+
+# Prefer local juno_kanban source when available (monorepo development).
+# This keeps wrapper behavior aligned with working-tree changes without requiring
+# immediate reinstall from PyPI between local iterations.
+if [[ -d "$PROJECT_ROOT/juno_kanban/src" ]]; then
+    export PYTHONPATH="$PROJECT_ROOT/juno_kanban/src${PYTHONPATH:+:$PYTHONPATH}"
+fi
+
 # Arrays to store normalized arguments (declared at script level for proper handling)
 declare -a NORMALIZED_GLOBAL_FLAGS=()
 declare -a NORMALIZED_COMMAND_ARGS=()

package/dist/templates/skills/codex/understand-project/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: understand-project
+description: Understand current project and create/update specs under @.juno_task/specs/* , it allows you understand dependencies. and prepare for implementation. Use when user explicitly ask you, or when asking for understand the project, first see how it works and then do [main task] with respect to [constraints]
+argument-hint: "[Main Task] [Constraints] [Ultimate Goal]"
+enable-shell-directives: true
+---
+
+## Main Task
+
+!`jq -r '.mainTask' ./.juno_task/config.json`
+
+$1
+
+### Task 1
+
+Ultrathink !
+First task is to study @.juno_task/plan.md (it may be incorrect) and is to use up to 500 subagents to study existing project
+and study what is needed to achieve the main task.
+From that create/update a @.juno_task/plan.md which is a bullet point list sorted in priority of the items which have yet to be implemeneted. Think extra hard.
+Study @.juno_task/plan.md to determine starting point for research and keep it up to date with items considered complete/incomplete using subagents.
+
+### Task 2
+
+Second Task is to understand the task, create a spec for process to follow, plan to execute, scripts to create, virtual enviroment that we need, things that we need to be aware of, how to test the scripts and follow progress.
+Think hard and plan/create spec for every step of this task
+and for each part create a seperate .md file under @.juno_task/specs/\*
+
+## ULTIMATE Goal
+
+We want to achieve the main Task with respect to the Constraints section
+Consider missing steps and plan. If the step is missing then author the specification at @.juno_task/specs/FILENAME.md (do NOT assume that it does not exist, search before creating). The naming of the module should be GenZ named and not conflict with another module name. If you create a new step then document the plan to implement in @.juno_task/plan.md
+
+### @.juno_task/specs/ file format.
+
+- github flavored markdown
+- GenZ module names and without conflict to another module name.
+- Start with Priority in Codebase, Example: P0-core-module.md
+- the goal is when we run `ls` command in the specs folder we could understand what are the cornerstone of the project with one glance.
+
+### Constraints
+
+$1
+
+---
+
+$ARGUMENTS

package/dist/templates/skills/pi/kanban-workflow/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: kanban-workflow
+description: Comprehensive guide for using juno-kanban task management. Covers all commands (create, list, search, get, mark, update, archive, deps, ready, order, merge), dependency management, best practices, and workflow patterns. Use when you need to interact with the kanban board.
+argument-hint: "[command or workflow question]"
+enable-shell-directives: true
+---
+
+## Kanban CLI Reference
+
+All commands use `./.juno_task/scripts/kanban.sh` (wrapper around juno-kanban Python CLI).
+
+### Core Commands
+
+**CREATE** — Add a new task
+```bash
+./.juno_task/scripts/kanban.sh create "Task description here" --status backlog --tags feature,backend
+```
+Options: `--status` (backlog|todo|in_progress|done), `--tags` (comma/space-separated), `--blocked-by` (task IDs), `--related-tasks` (task IDs)
+
+**LIST** — Browse tasks with summary stats
+```bash
+./.juno_task/scripts/kanban.sh list --limit 5 --sort asc
+./.juno_task/scripts/kanban.sh list --status todo --sort asc
+./.juno_task/scripts/kanban.sh list --status todo,in_progress --limit 10
+```
+
+**SEARCH** — Find tasks by criteria
+```bash
+./.juno_task/scripts/kanban.sh search --status todo --tag backend --limit 10
+./.juno_task/scripts/kanban.sh search --body "OAuth" --open
+./.juno_task/scripts/kanban.sh search --commit abc123
+```
+Filters: `--status`, `--tag`, `--body`, `--response`, `--commit`, `--open` (no agent_response), `--recent`, `--exclude` (exclude tags)
+
+**GET** — Full task details (including dependency info and related task details)
+```bash
+./.juno_task/scripts/kanban.sh get TASK_ID
+```
+
+**MARK** — Update status with required response message
+```bash
+./.juno_task/scripts/kanban.sh mark in_progress --id TASK_ID --response "Starting work on this"
+./.juno_task/scripts/kanban.sh mark done --id TASK_ID --response "Completed: implemented X, tested Y" --commit abc123def
+./.juno_task/scripts/kanban.sh mark todo --id TASK_ID --response "Reopening: found regression"
+```
+Required: `--id` and `--response`. Optional: `--commit` (recommended for done).
+
+**UPDATE** — Modify task fields
+```bash
+./.juno_task/scripts/kanban.sh update TASK_ID --status todo --tags backend,urgent
+./.juno_task/scripts/kanban.sh update TASK_ID --commit abc123def
+./.juno_task/scripts/kanban.sh update TASK_ID --response "Additional context"
+```
+
+**ARCHIVE** — Soft delete (preserves data, sets status to archive)
+```bash
+./.juno_task/scripts/kanban.sh archive TASK_ID
+```
+
+### Dependency Management
+
+**DEPS** — View, add, or remove task dependencies
+```bash
+# View dependency info (blockers, dependents, priority score)
+./.juno_task/scripts/kanban.sh deps TASK_ID
+
+# Add blockers (TASK_ID cannot start until BLOCKER1 and BLOCKER2 are done)
+./.juno_task/scripts/kanban.sh deps add --id TASK_ID --blocked-by BLOCKER1 BLOCKER2
+
+# Remove a blocker
+./.juno_task/scripts/kanban.sh deps remove --id TASK_ID --blocked-by BLOCKER1
+```
+Cycle detection prevents circular dependencies automatically.
+
+**READY** — Tasks with all blockers satisfied (safe to work on)
+```bash
+./.juno_task/scripts/kanban.sh ready
+./.juno_task/scripts/kanban.sh ready --tag backend --limit 5
+```
+Returns tasks where status is backlog/todo/in_progress AND all `blocked_by` tasks are done/archive.
+
+**ORDER** — Topological sort of open tasks respecting dependencies
+```bash
+./.juno_task/scripts/kanban.sh order
+./.juno_task/scripts/kanban.sh order --scores
+```
+Use for determining safe parallel execution order.
+
+### Body Markup for Inline Dependencies
+
+Declare dependencies and relations directly in task body text:
+
+```
+[blocked_by]TASK_ID[/blocked_by]          — This task is blocked by TASK_ID
+[blocked_by]ID1, ID2[/blocked_by]         — Blocked by multiple tasks
+[task_id]RELATED_ID[/task_id]             — Reference a related task
+[task_id]ID1 ID2[/task_id]                — Multiple related tasks
+```
+
+These are parsed automatically when the task is created/updated.
+
+### Merge (Multi-Directory Consolidation)
+
+When tasks get scattered across subdirectories:
+```bash
+# Auto-discover and merge all .juno_task dirs
+./.juno_task/scripts/kanban.sh merge --find-all --into ./.juno_task --dry-run
+
+# Merge specific sources
+./.juno_task/scripts/kanban.sh merge ./sub1/.juno_task ./sub2/.juno_task --into ./.juno_task
+```
+Strategy: `--strategy keep-newer` (default) or `--strategy keep-both`.
+
+### Output Formats
+
+All commands support: `-f json`, `-f ndjson` (default), `-f xml`, `-f table`
+Add `--raw` for compact output. Add `-p` for pretty print.
+
+### Best Practices
+
+1. **Task sizing**: Create tasks small enough to complete in one iteration without filling the context window
+2. **Status flow**: backlog → todo → in_progress → done (or archive for abandoned tasks)
+3. **Always include `--response`** when using `mark` — document what you did and how you tested it
+4. **Attach commits**: Use `--commit HASH` when marking done, then `update TASK_ID --commit HASH` to link the git history
+5. **Use `ready`** before starting work to find unblocked tasks
+6. **Use `order --scores`** to plan parallel execution pipelines
+7. **Use `[blocked_by]` markup** in task body when creating tasks that depend on others
+8. **Use `[task_id]` markup** in task body to cross-reference related tasks
+9. **Use `get TASK_ID`** to see full task details including resolved dependency and related task info
+10. **One task in_progress at a time** — finish or re-queue before starting the next
+
+### Environment Variables
+
+- `JUNO_TASK_ROOT` — Pin kanban operations to a specific project root directory
+- `JUNO_DEBUG=true` — Show diagnostic messages
+- `JUNO_VERBOSE=true` — Show informational messages
+- `JUNO_KANBAN_LIST_BODY_TRUNCATE_CHARS=N` — Override list body truncation (default: 1200)
+
+$ARGUMENTS

package/dist/templates/skills/pi/plan-kanban-tasks/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: plan-kanban-tasks
 description: Generate Product Development Requirments(PDR) and create task on kanban. Use when user explictly ask for, or ask for creating a task, planing a feature, register a task on kaban. "Generate PDR"
-argument-hint: [Required Features] [Constraints] [Specification] [Test Criteria]
+argument-hint: "[Required Features] [Constraints] [Specification] [Test Criteria]"
 enable-shell-directives: true
 ---
 

package/dist/templates/skills/pi/ralph-loop/SKILL.md

@@ -37,3 +37,7 @@ description: should only get executed with explicit user request.
 1012. After reveiwing Feedback, if you find an open issue, you need to update previously handled issues status as well. If user reporting a bug, that earlier on reported on the Tasks or @AGENTS.md as resolved. You should update it to reflect that the issue is not resolved.
       it would be ok to include past reasoning and root causing to the open issue, You should mention. <PREVIOUS_AGENT_ATTEMP> Tag and describe the approach already taken, so the agent knows 1.the issue is still open,2. past approaches to resolve it, what it was, and know that it has failed.
       Tasks , USER_FEEDBACK and @AGENTS.md should repesent truth. User Open Issue is a high level of truth. so you need to reflect it on the files.
+
+<SPECIFIC_INSTRUCTION>
+$ARGUMENTS
+</SPECIFIC_INSTRUCTION>

package/dist/templates/skills/pi/understand-project/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: understand-project
 description: Understand current project and create/update specs under @.juno_task/specs/* , it allows you understand dependencies. and prepare for implementation. Use when user explicitly ask you, or when asking for understand the project, first see how it works and then do [main task] with respect to [constraints]
-argument-hint: [Main Task] [Constraints] [Ultimate Goal]
+argument-hint: "[Main Task] [Constraints] [Ultimate Goal]"
 enable-shell-directives: true
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "juno-code",
-  "version": "1.0.49",
+  "version": "1.0.51",
   "description": "Ralph Wiggum meet Kanban! Ralph style execution for [Claude Code, Codex, Gemini, Cursor]. One task per iteration, automatic progress tracking, and git commits. Set it and let it run.",
   "keywords": [
     "Ralph",
@@ -31,7 +31,8 @@
   },
   "bin": {
     "juno-code": "./dist/bin/juno-code.sh",
-    "juno-collect-feedback": "./dist/bin/feedback-collector.mjs"
+    "yy": "./dist/bin/juno-code.sh",
+    "feedback-juno-code": "./dist/bin/feedback-collector.mjs"
   },
   "files": [
     "dist",
@@ -81,7 +82,7 @@
     "commander": "^11.1.0",
     "execa": "^8.0.1",
     "fs-extra": "^11.1.1",
-    "glob": "^10.4.5",
+    "glob": "^13.0.6",
     "js-yaml": "^4.1.1",
     "semver": "^7.5.4",
     "strip-ansi": "^7.1.2",
@@ -103,8 +104,9 @@
     "eslint": "^8.55.0",
     "eslint-config-prettier": "^9.1.0",
     "prettier": "^3.1.1",
-    "rimraf": "^5.0.5",
-    "tsup": "^8.0.1",
+    "rimraf": "^6.1.3",
+    "sucrase": "^3.35.1",
+    "tsup": "^8.5.1",
     "tsx": "^4.6.2",
     "typescript": "^5.3.3",
     "vitest": "^1.0.4"