From Dev10x
Routes deferred tasks to rediscovery contexts like PR comments, tickets, code TODOs, Slack DMs, or project TODO files. Triggers for tasks saved for later, not immediate action.
npx claudepluginhub dev10x-guru/dev10x-claude --plugin Dev10xThis skill uses the workspace's default tool permissions.
**Announce:** "Using Dev10x:park to save this item for later."
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Announce: "Using Dev10x:park to save this item for later."
This skill follows references/task-orchestration.md patterns.
Create a task at invocation, mark completed when done:
REQUIRED: Create a task at invocation. Execute at startup:
TaskCreate(subject="Defer work item", activeForm="Deferring item")Mark completed when done: TaskUpdate(taskId, status="completed")
Route a single deferred item to the right discovery context. Can be
invoked standalone or called by Dev10x:session-wrap-up for each open loop.
Accept the item to defer. This is either:
Dev10x:session-wrap-up (structured)/Dev10x:park "item description"Run these checks to determine available targets:
Branch + ticket:
git branch --show-current
Extract ticket ID from branch name (pattern: username/TICKET-ID/[worktree/]desc).
Open PR:
gh pr list --head "$(git branch --show-current)" --state open \
--json number,url --limit 1
Repository root:
basename "$(git rev-parse --show-toplevel)"
Build target list based on detected context. Always available:
| # | Target | When it surfaces |
|---|---|---|
| 1 | .claude/TODO.md | Next Claude session in this project |
| 2 | Slack DM to self | When clearing Slack messages |
| 3 | Create issue | When triaging backlog or planning sprint |
Conditionally available (include only when detected):
| # | Target | Condition |
|---|---|---|
| 4 | Issue tracker comment | Ticket ID found in branch |
| 5 | PR comment | Open PR found for current branch |
| 5b | PR session bookmark | Open PR + session end / session-wrap-up context |
| 6 | Inline TODO/FIXME | User mentions a specific file |
| 7 | Keep in session | User wants to finish later this session |
REQUIRED: Call AskUserQuestion (do NOT use plain text)
with multiSelect enabled so user can pick multiple targets
for the same item.
For each selected target:
| Target | Action |
|---|---|
.claude/TODO.md | Invoke Dev10x:park-todo (project file mode) |
| Slack DM | Invoke Dev10x:park-remind |
| Create issue | Ask user which tracker (Linear, GitHub Issues, Jira, etc.) then create the issue with the deferred item as description |
| Issue tracker comment | Post comment via the appropriate tracker MCP or CLI tool |
| PR comment | Post as PR comment (simple format) |
| PR session bookmark | Post as PR comment with rich metadata (see PR Bookmark Format below) |
| Inline TODO/FIXME | Invoke Dev10x:park-todo (inline mode) — ask user for file path if not provided |
| Keep in session | Invoke Dev10x:session-tasks to create a TaskCreate entry |
Report which targets received the item:
Deferred "Add order confirmation email":
✓ .claude/TODO.md (project)
✓ Slack DM sent
Issue tracker comment:
🔖 **Deferred from session [YYYY-MM-DD]**
<item description>
_Branch: `<branch-name>`_
PR comment (simple):
🔖 **Deferred item**
<item description>
_Session: YYYY-MM-DD_
PR session bookmark (rich metadata):
Use this format when deferring work on a PR to the next session. It
provides enough context for claude --resume to pick up where the
session left off.
Gather this data before composing:
basename "$(ls -t ~/.claude/projects/<encoded-cwd>/*.jsonl | head -1)" .jsonl
mcp__plugin_Dev10x_cli__pr_comments(action="list", pr_number={number})
in_reply_to_id is null)git log --oneline <base-branch>..HEADgh pr view {number} --json body -q '.body'Compose the comment:
> **Automated reminder** — @{reviewer} session bookmark for
> picking up this review tomorrow.
> Session ID: `{session_id}`
> Resume with: `claude --resume {session_id}`
---
## PR #{number} Review — State of Play ({date})
### Context
{1-2 sentence summary of what the PR does}
### Review comments addressed
| Thread | Status | Key point |
|--------|--------|-----------|
| [r{id}]({url}) | Addressed / Open | {one-line summary} |
### Current state after grooming (`{short_sha}`)
{Brief description of production code and test state}
### What to do next
1. {next step}
2. {next step}
Write the comment to a unique temp file and post via --body-file:
/tmp/Dev10x/bin/mktmp.sh git pr-comment .txt
Write content to the returned path using Write tool, then:
gh pr comment {number} --body-file <unique-path>
To update an existing bookmark comment instead of creating a new one:
gh api repos/{owner}/{repo}/issues/comments/{comment_id} \
-X PATCH -F body=@<unique-path>
Dev10x:session-wrap-up — Phase 3 calls this for each deferred itemDev10x:gh-pr-bookmark — thin wrapper that pre-selects PR session bookmark target