$ loading_
Suggests the most suitable next implementation task after finishing current work.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "next-task" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/next-task/SKILL.md 2. Save it as ~/.claude/skills/next-task/SKILL.md 3. Reload skills and tell me it's ready
I just finished the user login API and basic unit tests. Based on this progress, recommend the next development task I should do now, and explain the reason and priority.
A recommendation for one or more immediate next development tasks with priority and brief rationale.
The payment callback logic, order status updates, and error logging are complete. Recommend the most reasonable next implementation task without jumping into high-level planning too early.
A next-task recommendation aligned with the current implementation stage, such as adding tests, integrating the frontend, monitoring, or handling edge cases.
I have completed the core code changes for this requirement and passed local validation. Please suggest the next most worthwhile task directly, making it specific, actionable, and briefly noting dependencies.
A clear and actionable next task, including what to do, why it matters, and any likely prerequisites.
After completing implementation (PR created or push performed):
Task completed! Would you like a suggestion for the next task?
[Y] Yes, suggest next task
[N] No, end session
type:task, no assignee, state open| Criterion | Weight | Description |
|---|---|---|
| Priority | High | P1 > P2 > P3 |
| Dependencies satisfied | High | Tasks without blockers first |
| Same User Story | Medium | Context continuity |
| Same feature | Medium | Domain continuity |
| Sequential phase | Low | Setup → Foundation → Core → Integration |
Before presenting suggestions, check if there are open PRs in the repository that haven't been merged yet. The dependency is about code that is not in main, regardless of who opened the PR.
# List open PRs in the repository
# GitHub: github/list_pull_requests(owner, repo, state: "open")
# Azure DevOps: ado/repo_pull_request(action: "list", status: "active")
If there are open PRs, check if the suggested tasks depend on the code in those PRs (same user story, later phase, or explicit dependency in tasks.md).
Recommended next tasks:
1. #[number]: [title]
Priority: P1 | Feature: [name] | Phase: [phase]
Reason: Highest priority, same feature
2. #[number]: [title]
Priority: P1 | Feature: [name] | Phase: [phase]
Reason: Dependency from previous task satisfied
3. #[number]: [title]
Priority: P2 | Feature: [name] | Phase: [phase]
Reason: User Story continuity
[1/2/3] Select task
[O] See other options
[N] End session
If the selected task depends on code from an open PR (not merged), alert:
Warning: this task depends on code from PR #[number] ([title]), which has not been merged yet.
If you create the branch from the main branch, the code from the previous task will not be available.
[W] Wait for PR merge and continue later
[B] Create branch from the previous branch ([branch-name]) — stacked branch
[I] Ignore and create from the main branch anyway
Note: Option [B] (stacked branch) works, but requires rebase after the previous PR is merged. Alert the dev about this implication.
If the user selects a task:
git status
git log origin/$(git branch --show-current)..HEAD --oneline 2>/dev/null
If there are uncommitted changes:
You have uncommitted changes on the current branch:
[modified files]
[C] Commit changes and continue
[S] Stash and continue (not recommended)
[A] Abort and continue on the current task
If there are unpushed commits:
You have local commits not pushed to remote:
[list of commits]
[P] Push and continue
[A] Abort and continue on the current task
If the current branch is not main/master/develop:
You are on branch: [branch-name]
To keep branches short-lived, I recommend:
[M] Return to main/develop and create a new branch
[C] Continue on the current branch (not recommended for different tasks)
After ensuring a clean branch:
cat .memory/git-config.md 2>/dev/nullgit symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@'git checkout <integration-branch>git pull origin <integration-branch>Design and review software architecture diagrams for clearer, documentation-friendly visuals.
Create, switch, and verify Git branches before starting implementation work.
Initialize projects or verify and generate up-to-date SDD documentation templates.
Verify and create standard community and governance files for new projects.
Verify assignee, dependencies, priority, and capacity before starting a work item.
Systematically triage failures and fix broken builds or unexpected runtime issues.
Sync active tasks and refresh project memory to catch missed work.
Finalize completed work by committing, pushing, and opening reviewed pull requests.
Review implementation plans for gaps, assumptions, and sequencing before coding starts
Turn Notion specs into implementation plans, tasks, and progress tracking.
Create step-by-step implementation plans for engineers new to a codebase.
Execute implementation plans by splitting and advancing independent tasks in-session.