running-sprint-zero-trial

Plan and execute a Sprint 0 exploratory trial for phased software delivery.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tuvens/phased-development --skill running-sprint-zero-trial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: running-sprint-zero-trial
Source: https://github.com/tuvens/phased-development/tree/main/skills/running-sprint-zero-trial
Command: npx skills add https://github.com/tuvens/phased-development --skill running-sprint-zero-trial

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Phase Leads validate a large phase before real implementation by running a learning-only Sprint 0 that exposes hidden complexity, coordination gaps, and user experience issues early.

Core Features & Use Cases

  • Exploratory trial branch setup: Creates the dedicated Sprint 0 worktree and prompt structure for a phase-level trial pass.
  • Learning-only implementation: Guides an implementer to attempt the full planned scope across all intended sprints without producing merge-ready output.
  • Evidence capture and refinement: Produces friction logs, test results, regression guidance, and optional UX review artifacts that inform Sprint 1-N prompt revisions.
  • Use case: A Phase Lead uses this Skill when a multi-sprint feature set is uncertain and needs a realistic trial run before committing the team to detailed implementation.

Quick Start

Ask the AI to set up and execute Sprint 0 for the current phase, then collect the friction log, testing results, and any UX review deliverables for prompt refinement.

Frequently Asked Questions about running-sprint-zero-trial

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

FAQPage Schema
What is a Sprint 0 exploratory trial in software delivery?

A Sprint 0 exploratory trial is a learning-only implementation pass that attempts full planned scope across multi-sprint phases to expose hidden complexity, coordination gaps, and UX issues before committing to real implementation.

How do I run a Sprint 0 trial for a multi-sprint Claude Code project?

Set up a dedicated branch worktree, guide an implementer through learning-only attempts of the full scope, then collect FRICTION-LOG.md, UX-REVIEW.md, and testing artifacts to refine Sprint 1-N prompts.

Do I need a dedicated branch setup for a Sprint 0 exploratory phase?

Yes, Sprint 0 requires dedicated branch setup with non-merge PR conventions to ensure the trial output remains isolated and does not produce merge-ready code for the main project line.

Can I capture UX walkthrough reviews during a phased software delivery trial?

Yes, the trial supports optional Chrome MCP walkthrough handling to perform UX review and deliver canonical UX-REVIEW.md artifacts that inform prompt revisions for subsequent sprints.

What is the best way to discover hidden risks before starting multi-sprint implementation?

Running a learning-only Sprint 0 trial is the best approach, as it produces friction logs and regression guidance that reveal coordination gaps and complexity early, before the team commits to detailed implementation.

When should I not use a Sprint 0 trial approach for phase planning?

Avoid Sprint 0 trials for single-sprint or well-understood phases, as the dedicated branch setup and evidence capture process is designed for uncertain, multi-sprint feature sets needing realistic validation.