pace-next

Analyze project signals to recommend the most important next development action.

73|6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/arch-team/devpace --skill pace-next
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pace-next
Source: https://github.com/arch-team/devpace/tree/main/skills/pace-next
Command: npx skills add https://github.com/arch-team/devpace --skill pace-next

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users understand the most important next action to take in their development workflow, preventing decision paralysis and ensuring progress on high-priority tasks.

Core Features & Use Cases

  • Global Navigation: Provides a single, prioritized recommendation for the next task across all project domains (e.g., development, review, release, strategy).
  • Contextual Recommendations: Analyzes project state, backlog, risks, and goals to offer tailored advice.
  • Use Case: When unsure what to work on next, a user can ask "What should I do now?" and receive a clear, actionable suggestion like "Focus on reviewing the critical bug fix in the authentication module."

Quick Start

Ask the skill for the most important next action.

Frequently Asked Questions about pace-next

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine the most important next action in my development workflow?

To determine the most important next action, this Skill analyzes cross-domain signals like backlog status and strategic goals, then recommends a single prioritized task to prevent decision paralysis.

What is the best way to prioritize development tasks when facing a complex backlog?

The best way to prioritize development tasks is to analyze release progress and risks across all project domains, yielding a clear recommendation for your next task and a journey path visualization.

Can I get a detailed explanation for why a specific task was recommended as my next step?

Yes, you can get a detailed explanation for your next action recommendation by requesting reasoning chains that analyze your project state, backlog, risks, and strategic goals.

Does this task management approach work across different project domains like review and release?

Yes, this task management approach works across different project domains by analyzing release progress and risks globally, providing a single contextual recommendation regardless of the specific domain.

When should I avoid using an automated next action recommendation for project planning?

You should avoid using automated next action recommendations when you lack sufficient project state data, as the analysis relies on cross-domain signals like backlog status and release progress to function accurately.