repo-whats-next-skill

Determine the safest next repository-scope action with milestone-first routing and approval-ready output.

29|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/OceanEyeFF/servo --skill repo-whats-next-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-whats-next-skill
Source: https://github.com/OceanEyeFF/servo/tree/main/product/harness/skills/repo-whats-next-skill
Command: npx skills add https://github.com/OceanEyeFF/servo --skill repo-whats-next-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps the Harness decide the next best action at the code-repository scope without expanding scope or changing control state, producing a structured routing and approval-ready decision.

Core Features & Use Cases

  • Milestone-First next-step decisioning: Anchors decisions at the milestone level (create/activate/closeout/append) and only then derives worktrack-level intent when allowed.
  • Mode-driven reasoning with guardrails: Supports a default decision path, an embedded priority reframe/contradiction analysis mode, and an overview fallback mode when evidence is insufficient.
  • Strict routing projection: Outputs explicit next-route, allowed actions, blockers, and approval requirements rather than narrative summaries, respecting deployed route boundaries and stop conditions.
  • Boundary-safe integration: Reads worktrack artifacts only as boundary evidence and prevents updating or rewriting worktrack queues within repo-scope decisions.

Quick Start

Use repo-whats-next-skill to determine the next Harness routing step for a repository when you need a constrained, evidence-based “what next” decision without executing worktracks directly.

Frequently Asked Questions about repo-whats-next-skill

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

FAQPage Schema
How do I determine the safest next action for a code repository without expanding scope?▼

To determine the safest next action for a code repository, this Skill uses milestone-first reasoning to evaluate repo-scope transitions and outputs a structured routing decision with explicit blockers and approval requirements.

What is milestone-first routing when deciding whether to enter a worktrack or refresh repo state?▼

Milestone-first routing anchors decisions at the milestone level—create, activate, closeout, or append—and only then derives worktrack-level intent when allowed, ensuring boundary-safe integration when choosing between entering a worktrack, refreshing repo state, or continuing observation.

How do I generate approval-ready routing decisions with guardrails for repository scope?▼

Generate approval-ready routing decisions by applying mode-driven reasoning with guardrails, which outputs explicit next-route, allowed actions, blockers, and approval requirements while respecting deployed route boundaries and stop conditions.

Can I update or rewrite worktrack queues when making a repo-scope routing decision?▼

No, you cannot update or rewrite worktrack queues during repo-scope routing decisions; the system reads worktrack artifacts strictly as boundary evidence to prevent scope expansion or control state changes.

What happens when evidence is insufficient to determine the next repository move?▼

When evidence is insufficient to determine the next repository move, the system applies an overview fallback mode to safely project the next routing step without forcing a worktrack entry or state change.

Does priority reframe mode help with contradiction analysis during repository routing?▼

Yes, priority reframe mode analyzes contradictions and reframes priorities during repository routing, providing an alternative decision path within the default mode-driven reasoning to ensure boundary-safe milestone-first outcomes.