Name: nextTask
Author: Francescolatorre

Prompt file imported from Francescolatorre/learnplattform.roocode (.claude/commands/nextTask.md). Fill in {{arguments}} before use. Copyright stays with the author.

Identify, develop, and deliver the next critical task end-to-end following the workflow defined in agents.md.

Task ID: {{arguments}} (optional: specify task, otherwise auto-select highest priority)

Workflow Steps:

Task Selection:
- Primary Source: Check memory_bank/current/backlog/active/current-sprint.md for committed sprint tasks
- Secondary Source: Check memory_bank/current/backlog/active/p0-critical.md for emergency items
- Fallback Source: Review memory_bank/current/backlog/active/p1-high.md for high priority tasks
- Context Check: Reference memory_bank/workspace/analysis/activeContext.md for current development focus
- Use provided task-id if specified, otherwise auto-select highest priority OPEN task
Branch Creation: Create feature branch following naming convention feature/[task-id]-[brief-description] or fix/[task-id]-[brief-description]
Development:
- Move task status from OPEN → IN PROGRESS in task documents
- Implement solution following vertical slice approach (Backend + API + Frontend + Tests)
- Apply all coding conventions from AGENTS.md sections 1-2
- Run validation checks throughout development
Quality Assurance:
- Execute comprehensive testing (Unit + Integration + E2E where applicable)
- Run linting, formatting, and type checking
- Ensure all programmatic checks pass
Documentation:
- Update task status in appropriate backlog files (memory_bank/current/backlog/active/)
- Update memory_bank/current/backlog/active/current-sprint.md with progress
- Update memory_bank/workspace/analysis/activeContext.md and memory_bank/workspace/analysis/progress.md
- Create/update any necessary technical documentation
- Move completed tasks to memory_bank/history/completed/ following the established pattern
Pull Request:
- Commit with proper message format: [TASK-ID] [STATUS] [SUMMARY]
- Push branch to remote
- Create pull request with comprehensive description including test plan
- Link to task documentation

Prerequisites: Clean working directory, all previous commits pushed Output: Ready-to-review pull request with complete implementation and documentation

Install nextTask and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Identify, develop, and deliver the next critical task end-to-end following the workflow defined in agents.md. **Task ID**: {{arguments}} (optional: specify task, otherwise auto-select highest priority) **Workflow Steps:** 1. **Task Selection**: - **Primary Source**: Check `memory_bank/current/backlog/active/current-sprint.md` for committed sprint tasks - **Secondary Source**: Check `memory_bank/current/backlog/active/p0-critical.md` for emergency items - **Fallback Source**: Review `memory_bank/current/backlog/active/p1-high.md` for high priority tasks - **Context Check**: Reference `memory_bank/workspace/analysis/activeContext.md` for current development focus - Use provided task-id if specified, otherwise auto-select highest priority OPEN task 2. **Branch Creation**: Create feature branch following naming convention `feature/[task-id]-[brief-description]` or `fix/[task-id]-[brief-description]` 3. **Development**: - Move task status from OPEN → IN PROGRESS in task documents - Implement solution following vertical slice approach (Backend + API + Frontend + Tests) - Apply all coding conventions from AGENTS.md sections 1-2 - Run validation checks throughout development 4. **Quality Assurance**: - Execute comprehensive testing (Unit + Integration + E2E where applicable) - Run linting, formatting, and type checking - Ensure all programmatic checks pass 5. **Documentation**: - Update task status in appropriate backlog files (`memory_bank/current/backlog/active/`) - Update `memory_bank/current/backlog/active/current-sprint.md` with progress - Update `memory_bank/workspace/analysis/activeContext.md` and `memory_bank/workspace/analysis/progress.md` - Create/update any necessary technical documentation - Move completed tasks to `memory_bank/history/completed/` following the established pattern 6. **Pull Request**: - Commit with proper message format: `[TASK-ID] [STATUS] [SUMMARY]` - Push branch to remote - Create pull request with comprehensive description including test plan - Link to task documentation **Prerequisites**: Clean working directory, all previous commits pushed **Output**: Ready-to-review pull request with complete implementation and documentation

{ "prompt": "Identify, develop, and deliver the next critical task end-to-end following the workflow defined in agents.md.\n\n**Task ID**: {{arguments}} (optional: specify task, otherwise auto-select highest priority)\n\n**Workflow Steps:**\n1. **Task Selection**:\n - **Primary Source**: Check `memory_bank/current/backlog/active/current-sprint.md` for committed sprint tasks\n - **Secondary Source**: Check `memory_bank/current/backlog/active/p0-critical.md` for emergency items\n - **Fallback Source**: Review `memory_bank/current/backlog/active/p1-high.md` for high priority tasks\n - **Context Check**: Reference `memory_bank/workspace/analysis/activeContext.md` for current development focus\n - Use provided task-id if specified, otherwise auto-select highest priority OPEN task\n2. **Branch Creation**: Create feature branch following naming convention `feature/[task-id]-[brief-description]` or `fix/[task-id]-[brief-description]`\n3. **Development**: \n - Move task status from OPEN → IN PROGRESS in task documents\n - Implement solution following vertical slice approach (Backend + API + Frontend + Tests)\n - Apply all coding conventions from AGENTS.md sections 1-2\n - Run validation checks throughout development\n4. **Quality Assurance**:\n - Execute comprehensive testing (Unit + Integration + E2E where applicable)\n - Run linting, formatting, and type checking\n - Ensure all programmatic checks pass\n5. **Documentation**:\n - Update task status in appropriate backlog files (`memory_bank/current/backlog/active/`)\n - Update `memory_bank/current/backlog/active/current-sprint.md` with progress\n - Update `memory_bank/workspace/analysis/activeContext.md` and `memory_bank/workspace/analysis/progress.md`\n - Create/update any necessary technical documentation\n - Move completed tasks to `memory_bank/history/completed/` following the established pattern\n6. **Pull Request**: \n - Commit with proper message format: `[TASK-ID] [STATUS] [SUMMARY]`\n - Push branch to remote\n - Create pull request with comprehensive description including test plan\n - Link to task documentation\n\n**Prerequisites**: Clean working directory, all previous commits pushed\n**Output**: Ready-to-review pull request with complete implementation and documentation", "variables": [ "arguments" ], "notes": "Identify, develop, and deliver the next critical task end-to-end Tools: Read(*), Write(*), Edit(*), MultiEdit(*), Bash(*), Glob(*), Grep(*), TodoWrite(*).", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/Francescolatorre/learnplattform.roocode", "path": ".claude/commands/nextTask.md", "ref": "75a2cf39bf583d579f5de2438cd1d0b6f7907c5d", "url": "https://github.com/Francescolatorre/learnplattform.roocode/blob/75a2cf39bf583d579f5de2438cd1d0b6f7907c5d/.claude/commands/nextTask.md", "key": "Francescolatorre/learnplattform.roocode/.claude/commands/nextTask.md" } } }

nextTask

About

Install nextTask and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews