메뉴
Recommend the best next task to work on based on open GitHub issues. Analyzes priority, dependencies, milestone urgency, and codebase readiness. Trigger when user asks: what should I work on, what is next, next task, pick a task, what to do next, suggest work, prioritize tasks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | next-task |
| description | Recommend the best next task to work on based on open GitHub issues. Analyzes priority, dependencies, milestone urgency, and codebase readiness. Trigger when user asks: what should I work on, what is next, next task, pick a task, what to do next, suggest work, prioritize tasks. |
Analyze open GitHub issues and recommend the best task to start working on right now.
Run these in parallel to understand the current state:
gh issue list --repo Destrayon/Connapse --state open --json number,title,labels,milestone,assignees,createdAt,updatedAt --limit 100
git status --short
git branch --show-current
gh pr list --repo Destrayon/Connapse --state merged --json number,title,mergedAt,labels --limit 5
Read .claude/state/decisions.md and .claude/state/issues.md for any known blockers, dependencies, or recent decisions that affect prioritization.
Evaluate each open issue against these criteria, in order of importance:
| Priority | Score |
|---|---|
| P0-Critical | 100 |
| P1-High | 70 |
| P2-Medium | 40 |
| P3-Low | 10 |
| No priority set | 20 |
Issues in the nearest milestone score higher. The reasoning: shipping a complete milestone is more valuable than scattering work across multiple milestones.
| Milestone | Score |
|---|---|
| Current (nearest due date or lowest version) | +30 |
| Next | +15 |
| Future | +5 |
| No milestone | +0 |
An issue that has no blockers and no unmerged dependencies should score higher than one waiting on other work. Check:
blocked?| Status | Score |
|---|---|
| Unblocks other issues | +25 |
| No dependencies, ready to start | +15 |
| Dependencies met (referenced issues are closed) | +10 |
| Has open dependencies | -30 |
Labeled blocked | -50 |
If recent merged PRs touched the same area, there's context advantage — the codebase patterns are fresh.
| Condition | Score |
|---|---|
| Same area label as a recently merged PR | +10 |
| Builds directly on a recently merged PR | +15 |
Smaller issues are easier to start and finish in a single session. Bias toward completing something rather than starting something large.
| Size | Score |
|---|---|
| XS | +15 |
| S | +10 |
| M | +5 |
| L (should be decomposed) | -10 |
| No size | +0 |
Present the top 3 ranked issues in this format:
## Recommended Next Task
### #1: [Issue Title] (#number)
**Score**: [total] | **Priority**: [P-level] | **Milestone**: [version] | **Size**: [size]
**Why this one**: [1-2 sentences explaining why this is the best pick right now —
reference momentum, unblocking, milestone progress, etc.]
**Quick start**: [Which files to look at first, what interface to implement, etc.]
---
### #2: [Issue Title] (#number)
...
### #3: [Issue Title] (#number)
...
After presenting, ask the user which one they'd like to start — or if they want to see more options.
Once the user picks a task:
git checkout -b <type>/<issue-number>-<short-description># Get the project item ID for this issue
ITEM_ID=$(gh project item-list 3 --owner Destrayon --format json | jq -r '.items[] | select(.content.number == <ISSUE_NUMBER> and .content.repository == "Destrayon/Connapse") | .id')
# Move to In Progress
gh project item-edit --project-id PVT_kwHOAldLE84BQszG --id "$ITEM_ID" --field-id PVTSSF_lAHOAldLE84BQszGzg-vn-U --single-select-option-id 47fc9ee4
gh issue view <number>/create-tickets if they have ideas to discuss.Batch-create GitHub issues from a brainstorming discussion. Decomposes ideas into properly-sized tickets with labels, milestones, and project board placement. Trigger when user says: create tickets, make tickets, turn ideas into issues, create issues from brainstorm, create issues from discussion, batch create issues.
Run multiple Claude Code agents on separate GitHub issues simultaneously, each in its own worktree. Picks non-conflicting tasks, spawns autonomous agents that implement, commit, and open PRs. Trigger when user says: parallel work, work on multiple tasks, run agents in parallel, multi-agent, spawn agents, parallel tasks, work on N things at once.
End-to-end release validation for Connapse — the 'final boss' before any version ships. Downloads the latest alpha from GitHub Releases, deploys an isolated Docker instance (separate from production), then systematically tests every feature: UI via Playwright, API via curl/REST, MCP tools, search quality, security testing, boundary conditions, and adversarial inputs. If the release under test also bundles the standalone connapse-cli, adds CLI install + API/CLI parity gates. Produces a structured go/no-go release decision with evidence. Use this skill whenever someone says: release test, release validation, release gatekeeper, ready to ship, final QA, pre-release check, validate alpha, test the release, ship it, go/no-go, release candidate testing, end-to-end release test, or wants to verify a Connapse build is ready for public release.
Deep research across codebase, GitHub issues, discussions, project board, and architecture docs to discover new tasks, gaps, technical debt, and improvement ideas. Trigger when user says: discover work, find tasks, what needs doing, audit codebase, find gaps, technical debt audit, backlog discovery, brainstorm tasks, what is missing, research tasks, code audit.