// Check project progress, resume paused work, and route to the next action. Loads project state from the knowledge base, presents a status report, detects incomplete work or handoffs, and suggests the most logical next workflow to invoke.
Audit knowledge freshness and coverage. Checks what's documented against the current codebase, identifies stale or outdated knowledge, finds gaps, and provides targeted brv curate commands to fix them.
Investigate bugs using scientific method with persistent knowledge. Queries known issues and past bug fixes, applies hypothesis-driven investigation, and stores root cause analysis and fix patterns via brv curate for future reference.
Execute a phase plan task by task with verification. Loads the plan from the knowledge base, implements each task sequentially, verifies against success criteria, records progress, and transitions to the next phase. Stores execution results via brv curate.
Systematically explore a codebase, documentation, and knowledge gaps. Maps technology stack, architecture, conventions, testing, integrations, and concerns into the ByteRover context tree via brv curate.
Define project milestones with goals, scoped requirements, and phased roadmaps. Gathers user intent through questioning, assigns REQ-IDs for traceability, derives phases using goal-backward analysis, and optionally captures implementation decisions for gray areas. Stores everything via brv curate.
Interactive knowledge-driven project onboarding. Queries comprehensive knowledge across all domains, presents a structured project overview, identifies knowledge gaps, and suggests running explore to fill them.
| name | byterover-progress |
| description | Check project progress, resume paused work, and route to the next action. Loads project state from the knowledge base, presents a status report, detects incomplete work or handoffs, and suggests the most logical next workflow to invoke. |
A structured workflow for understanding where a project stands and what to do next. Loads all project state from the knowledge base, detects paused work or incomplete phases, and intelligently routes to the appropriate next action.
Run brv status first. If errors occur, instruct the user to resolve them in the brv terminal. See the byterover skill's TROUBLESHOOTING.md for details.
Query the knowledge base for complete project context:
brv query "What is the project definition and current milestone?"
brv query "What is the current project status and last activity?"
brv query "What is the project roadmap and phase completion status?"
brv query "Is there paused work, handoff context, or incomplete tasks to resume?"
brv query "What pending items, deferred ideas, or todos exist?"
If no project knowledge exists, inform the user and recommend running byterover-milestone to define a project.
From the retrieved knowledge, determine:
Format a clear status summary:
# [Project Name] — Progress Report
Milestone: v[X.Y] [Name]
Phase: [N] of [Total] — [Phase Name] — [Status]
Last activity: [description]
Completed Phases:
- Phase 1: [Name] — [one-line summary]
- Phase 2: [Name] — [one-line summary]
Current Phase:
Phase [N]: [Name] — [Goal]
Status: [Not started / Planned / In progress / Blocked]
Pending Items: [count] items
[Top 3-5 items if any]
Paused Work: [Yes/No]
[Handoff context if paused]
Based on the assessed state, recommend the most logical next step:
| State | Recommended Action |
|---|---|
| Paused work exists | Resume from handoff — describe what was in progress and next steps |
| Phase has a plan, not yet executed | Run byterover-execute to begin phase execution |
| Phase needs a plan | Run byterover-plan for the current phase |
| Current phase complete, more remain | Run byterover-plan for the next phase |
| All phases complete | Run byterover-ship to complete the milestone |
| Pending items need attention | Present items, let user choose: work on it, defer, or add to phase |
| No project defined | Run byterover-milestone to start a new project |
Present the recommendation with reasoning. If multiple options are valid, list them in priority order and let the user choose.
If the user wants to review pending items:
After the routing decision, update the knowledge base:
brv curate "Project status: Session resumed. Current position: Phase [N] — [status]. Next action: [what user chose]. Pending items: [count]" -f [relevant files]
Clearly state:
brv curate / brv query.env, credential files, and similarbrv curate view <logId> to confirm what was stored (logId is printed by brv curate on completion). Run brv curate view --help to see all options.