hyper-sprint

Orchestrates complete delivery sprints from intake through blind validation and archived reporting.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/migletto/slides --skill hyper-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyper-sprint
Source: https://github.com/migletto/slides/tree/main/.claude/skills/hyper-sprint
Command: npx skills add https://github.com/migletto/slides --skill hyper-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill turns a messy batch of implementation requests into a disciplined, end-to-end sprint that plans, delegates, tests, validates, and archives the result without the main agent becoming the worker.

Core Features & Use Cases

  • Sprint orchestration: Breaks a large change list into file-local clusters, assigns work to sub-agents, and keeps the orchestrator lean.
  • Blind validation: Uses fresh validators to independently confirm features, hunt for cross-cutting bugs, and gate completion on zero confirmed defects.
  • Cost-aware delivery: Emphasizes hub hygiene, context economy, readiness gating, and sprint reporting with burndown, stats, and cost artifacts.
  • Use case: A team receives a multi-issue spec for a UI-heavy app and wants implementation, regression testing, and a proof report completed in one controlled session.

Quick Start

Use the hyper-sprint skill to plan, delegate, test, and blind-validate this repository change set, then produce the final sprint report and archive.

Frequently Asked Questions about hyper-sprint

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

FAQPage Schema
How do I orchestrate a multi-issue implementation sprint with parallel workers?

Sprint orchestration breaks a large change list into file-local clusters, assigns work to sub-agents, and keeps the orchestrator lean. This delegates implementation tasks to parallel workers rather than having the main agent execute them directly.

What is blind validation for software delivery and how does it work?

Blind validation uses fresh validators to independently confirm features, hunt for cross-cutting bugs, and gate completion on zero confirmed defects. This independent verification ensures implementation quality without bias from the original worker agents.

Can I use Playwright for regression testing in a UI-heavy delivery sprint?

Yes, Playwright is a required dependency for running canonical verify commands during the sprint. It supports regression-heavy UI delivery by enabling automated browser testing for multi-issue implementation work and cross-cutting bug hunts.

Do I need git worktrees to isolate parallel sub-agent workers?

Yes, worktree isolation is required to separate parallel sub-agent workers during change delivery. This ensures each worker operates independently within the sprint without causing file conflicts across the repository.

How do I track sprint cost and burndown for a batch of implementation requests?

Sprint reporting generates a Markdown proof artifact containing burndown evidence, statistics, and cost tracking data. This cost-aware delivery approach emphasizes context economy and hub hygiene to monitor progress throughout the session.

What's the best way to handle cross-cutting bug hunts across a large codebase?

Cross-cutting bug hunts require sub-agent delegation and worktree isolation to search independently, followed by blind validation from fresh validators to gate completion. This ensures zero confirmed defects before archiving the final sprint report.