xplan

Convert a Hurrah.tv feature request into a phased engineering plan.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/mkerchenski/hurrah-tv --skill xplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xplan
Source: https://github.com/mkerchenski/hurrah-tv/tree/main/.claude/skills/xplan
Command: npx skills add https://github.com/mkerchenski/hurrah-tv --skill xplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The xplan skill prevents feature work from becoming chaotic by turning a vague implementation idea into a staged, reviewable plan that accounts for Hurrah.tv’s architecture, APIs, and database constraints.

Core Features & Use Cases

  • Two-mode planning (quick vs plan): Choose quick for small, single-concern tasks or plan for structured, phased delivery.
  • Hurrah.tv-aware pre-research: Scans existing learnings and plans, checks repo context and memory, and identifies the affected projects (Api/Client/Shared).
  • Phased plan with safety constraints: Enforces commit-able phases, requires DB schema changes to be Phase 1, and includes Hurrah.tv-specific guidance for Blazor WASM lifecycle, DTO ripple effects, and integration constraints.
  • Persistent artifacts: Saves approved plans to Plans/<feature>.md and prompts for whether to link/create/skip a tracking issue.

Quick Start

Use xplan in plan mode by asking it to plan a new feature and then approve the generated phased plan so it saves to Plans with Hurrah.tv context.

Frequently Asked Questions about xplan

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

FAQPage Schema
How do I plan phased delivery for a Blazor WASM feature across multiple projects?

Phased delivery for a Blazor WASM feature is planned by converting the idea into a structured plan that coordinates work across the Api, Client, and Shared projects, enforcing database schema changes as Phase 1 and including Blazor lifecycle guidance.

What is the best way to structure database migrations and DTO updates in a feature plan?

Structuring database migrations in a feature plan requires enforcing schema changes as Phase 1, followed by identifying API client DTO ripple effects and integration constraints to ensure commit-able phases across the architecture.

How do I create a GitHub issue tracking plan for a complex API and Blazor client feature?

Creating a tracking issue for a feature plan is triggered after the phased plan is approved and saved as a durable artifact, prompting you to decide whether to link, create, or skip a tracking issue for the work.

Can I do quick planning for single-concern tasks without a full phased delivery plan?

Quick planning for single-concern tasks is supported by choosing quick mode, which bypasses the structured phased delivery approach used for complex features requiring cross-project coordination.

Does pre-research for feature planning scan existing repo context and memory?

Pre-research for feature planning scans existing learnings, plans, issues, memory, and repo context to gather architectural constraints before proposing a plan with phase-by-phase verify steps.

When should I not use a structured phased plan for database migrations?

A structured phased plan for database migrations should be bypassed when handling small, single-concern tasks that do not require coordination across the Api, Client, and Shared projects.