Sherpa

Decompose complex epics into 15-minute atomic steps with commit checkpoints.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Dinxeshh/agent-skills --skill sherpa-dinxeshh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Sherpa
Source: https://github.com/Dinxeshh/agent-skills/tree/main/skills/sherpa
Command: npx skills add https://github.com/Dinxeshh/agent-skills --skill sherpa-dinxeshh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sherpa keeps complex Epics moving by decomposing them into manageable 5-15 minute steps while keeping drift, blockers, and scope creep from derailing progress.

Core Features & Use Cases

  • Focused Decomposition: Map the current Epic or story into atomic steps with commit points and dependency awareness so nothing is ambiguous.
  • Progress and Risk Tracking: Show one active step at a time, chart progress against estimates, detect drift, and surface risks, blockers, and weather signals.
  • Mult-agent Coordination: Route work to Nexus, Rally, Builder, or other specialists with the right handoff formats and log outcomes for calibration and reuse.

Quick Start

Ask Sherpa to turn my current Epic into the next 15-minute atomic step with its commit checkpoint and risk notes.

Frequently Asked Questions about Sherpa

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

FAQPage Schema
How do I break complex epics into 15-minute atomic steps for focused execution?

To break complex epics into 15-minute atomic steps, decompose the epic into focused tasks with commit points and dependency awareness. This prevents ambiguity and keeps execution aligned by showing one active step at a time while charting progress against estimates.

What is the best way to prevent scope creep and drift during workflow planning?

Preventing scope creep and drift during workflow planning requires atomic task decomposition with visible progress tracking. This approach detects blockers early, applies parking lot redirection for off-topic items, and uses calibration logging to keep execution aligned with the original epic scope.

How do I route work to different agents and track outcomes for calibration?

Routing work to different agents requires applying specific handoff formats to specialists like Nexus, Rally, or Builder. This mult-agent coordination routes tasks effectively and logs outcomes for calibration and reuse, ensuring downstream agents receive properly structured work.

Can I use task decomposition to map dependencies and commit checkpoints for a large story?

Yes, task decomposition maps large stories into atomic steps with explicit commit checkpoints and dependency awareness. This ensures nothing is ambiguous, allowing you to satisfy requirements for visible progress tracking and risk assessment before handing off work.

What's the best way to surface risk assessment and blocker detection in progress tracking?

Surface risk assessment and blocker detection in progress tracking by charting active steps against estimates to identify drift. This detects weather signals and blockers early, applying parking lot redirection to keep execution focused on the current atomic step.

Does Sherpa work for mult-agent coordination with specialist handoffs?

Sherpa works for mult-agent coordination by routing work to specialists like Nexus, Rally, or Builder with the correct handoff formats. It logs outcomes for calibration and reuse, ensuring that complex epics remain aligned across multiple agents during execution.