start-phase

Opens a project phase by gating entry conditions and cutting a phase branch off main.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill start-phase-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-phase
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/start-phase
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill start-phase-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a development phase without checking readiness leads to half-opened work: branches cut from dirty trees, wrong base branches, or stories that were never refined. This Skill enforces a hard entry gate before any phase begins, so every phase starts from a clean, verified state. ## Core Features & Use Cases - Explicit scope resolution: Resolves a phase, chat, or epic target into a concrete story list and echoes it for review before anything is created. - Three-part entry gate: Verifies a clean working tree, that the current branch is main, and that every story carries a ready status, aborting with a specific gap list if any check fails. - Safe branch creation: Surfaces a copy-pasteable git switch command to cut the phase branch off main, never force-creating or overwriting an existing branch. - Board synchronization: Records the phase opening in MONITOR.md and ACTIVE.md and regenerates the dashboard in one atomic step. - Use Case: Before running an execute-batch on chat CHAT-01, invoke this Skill to confirm all stories are ready, cut the phase/chat-01 branch, and update the project board. ## Quick Start Ask the assistant to start phase CHAT-01 so it verifies the entry gate, cuts the phase branch off main, and records the opening on the board.

Frequently Asked Questions about start-phase

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

FAQPage Schema
How do I start a new development phase in a git-based project workflow?

Provide an explicit phase, chat, or epic target such as CHAT-01 or EPIC-10. The Skill resolves the stories in scope, verifies the entry gate, surfaces the git switch command to cut the phase branch off main, and records the opening on the project board.

What conditions must be met before opening a phase branch?

Three conditions must all pass: the working tree must be clean with no uncommitted changes, the current branch must be main, and every story in the phase must carry a ready status. If any check fails, the Skill aborts and lists the specific failing item.

What happens if a phase branch already exists?

The Skill stops and surfaces that the branch already exists rather than overwriting it. It never force-creates branches, uses no force flags, and assumes no GitHub CLI is available.

Can I open a phase without specifying a target?

No. The Skill requires an explicit phase, chat, or epic target and never infers scope from ambient state. An ambiguous, missing, or zero-story target causes it to stop and ask for a concrete target.

Why does the phase opening fail when stories are not ready?

Stories with a not-started or unrefined status have not passed the Definition-of-Ready gate. They must go through backlog refinement first, and the Skill lists each not-ready story id with its status so you know exactly what to fix.