focus

Rank actionable next moves from repository state into five tiers.

37|2|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill focus-jellyrock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: focus
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/focus
Command: npx skills add https://github.com/jellyrock/jellyrock --skill focus-jellyrock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting a fresh coding session often leaves you facing multiple plausible next moves—pending handoffs, failed CI runs, stale signals, hot bugs, and tech debt—with no clear way to decide which one to tackle first or which tool to use.

Core Features & Use Cases

  • Tier-based ranking: Ranks 3–5 next-move candidates across five tiers (Resume, Blocked, Drift, Hot, Momentum) so blockers never fall off the menu.
  • Smart routing: Maps each candidate to the exact right path—domain triage skills for investigations, recipe skills for structured work like adding settings or migrations, plan files for ad-hoc one-offs, or project lifecycle commands for multi-session work.
  • Transparent recommendations: Always surfaces a Recommended pick with the rule that chose it, making the triage call overridable and explainable.

Quick Start

Use the focus skill at the start of a fresh session to rank your actionable next moves and route the chosen one to the correct downstream command.

Frequently Asked Questions about focus

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

FAQPage Schema
How do I prioritize tasks at the start of a coding session?

Session-start prioritization ranks actionable next moves from observed repository state using a tier rubric. It evaluates candidates like CI failures, handoffs, and bugs across five tiers to recommend the best next move and route it to the appropriate downstream command.

What is the best way to triage pending handoffs and CI failures together?

Triage of competing session candidates applies a fixed tier rubric across Resume, Blocked, Drift, Hot, and Momentum categories. It ranks multiple signals simultaneously, surfacing a recommended pick with the deciding rule so blockers never fall off the menu.

How does next-move routing work for tech debt and stale signals?

Next-move routing maps ranked candidates to exact downstream paths based on their tier and type. Domain triage skills handle investigations, recipe skills manage structured work like migrations, and plan files cover ad-hoc one-offs, printing invocation strings without auto-executing.

Can this workflow routing print commands without auto-executing them?

Workflow routing prints exact downstream invocation strings for each ranked candidate without auto-executing routes. This transparent approach surfaces the recommended pick alongside the rule that chose it, keeping the triage call fully overridable and explainable.

When do I need session-start catchup and prioritization?

Session-start catchup is needed when a fresh coding session presents multiple plausible next moves with no clear priority. It reads an aggregator output of repository state to resolve decision paralysis caused by competing signals like stale branches, hot bugs, and pending handoffs.