phase-task-verification

Create and verify git-spice branches across sequential and parallel task modes.

19|Updated Oct 21, 2025

Search Tags:#automation #git #workflow #devops #task execution #quality-assurance #branch verification

Ready to run

npx skills add https://github.com/arittr/spectacular --skill phase-task-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: phase-task-verification
Source: https://github.com/arittr/spectacular/tree/main/skills/phase-task-verification
Command: npx skills add https://github.com/arittr/spectacular --skill phase-task-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents silent failures and lost work in complex development workflows by ensuring proper git branch creation and verification across sequential and parallel task execution modes.

Core Features & Use Cases

Branch Creation & Verification: Automatically creates git-spice branches and verifies HEAD positioning based on execution mode.
Mode-Specific Logic: Handles both sequential (branch checkout verification) and parallel (HEAD detachment) scenarios.
Error Detection: Identifies and escalates git operation failures before they cause downstream issues.
Use Case: When running automated development pipelines with multiple tasks, use this Skill to ensure each task's work is properly staged in git branches and accessible for subsequent operations.

Quick Start

Use the phase-task-verification skill to create and verify a git branch for task "1-1" with run ID "8c8505" and commit message "Implement feature X".

Frequently Asked Questions about phase-task-verification

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

FAQPage Schema

How do I verify git branches are created correctly in automated task workflows?▼

Branch verification ensures each task's work is properly staged in git before downstream operations. This Skill automatically creates and verifies git-spice branches, checking HEAD positioning based on execution mode—verifying branch checkout in sequential mode and detaching HEAD in parallel mode—to prevent lost work and silent failures.

What's the difference between sequential and parallel task execution in git branch verification?▼

Sequential mode verifies HEAD against the expected branch after task completion, ensuring the correct branch is checked out. Parallel mode detaches HEAD to isolate task work. This Skill applies mode-specific logic to both, using RUN_ID, TASK_ID, and MODE to handle each correctly.

Can I use git branch verification to catch errors before they break my development pipeline?▼

Yes. This Skill identifies and escalates git operation failures—including git add errors, branch creation failures, and repository state issues—before they cascade downstream, preventing silent failures in complex automation workflows.

How do I automate branch creation and staging for multiple sequential tasks?▼

This Skill creates git-spice branches and stages changes automatically across sequential task execution. It validates branch naming, handles git add operations, and verifies HEAD positioning, so each task's work integrates cleanly without manual git commands.

What information do I need to provide for automated git branch verification?▼

Provide RUN_ID, TASK_ID, TASK_NAME, COMMIT_MESSAGE, and MODE. The Skill uses these to create appropriately named branches, stage changes with the correct commit message, and apply the correct verification logic for your execution context.

Does this work with existing git workflows and repository structures?▼

Yes. The Skill handles standard git repository operations—branch creation, staging, and HEAD verification—and detects repository state errors, making it compatible with existing workflows that need reliable branch management across task automation.