task-workflow

Coordinate a SPEC.md task from branch creation through merge and push.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/in0ho1no/TabNest --skill task-workflow-in0ho1no
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-workflow
Source: https://github.com/in0ho1no/TabNest/tree/main/.claude/skills/task-workflow
Command: npx skills add https://github.com/in0ho1no/TabNest --skill task-workflow-in0ho1no

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the full lifecycle of completing one repository task so you can move from planning to merge without missing required steps, reviews, or documentation updates.

Core Features & Use Cases

  • End-to-end task execution: Follows the complete dev-re workflow from branch creation through implementation, testing, review, merge, push, and memory updates.
  • Repository-safe coordination: Keeps work aligned to SPEC.md and AGENTS.md while preserving branch discipline, commit hygiene, and CI validation.
  • Use Case: Use it when you need to finish a single TaskX-Y in a shared codebase and want a repeatable checklist for code changes, test runs, GUI evaluation, and cross-model review.

Quick Start

Ask the Skill to carry one SPEC.md task from branch setup through implementation, validation, review, merge, push, and memory updates in a single dev-re session.

Frequently Asked Questions about task-workflow

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

FAQPage Schema
How do I manage a development task workflow from branch creation to merge?

A development task workflow coordinates the full lifecycle from branch creation through implementation, testing, review, merge, push, and memory updates. It standardizes each step so you can move from planning to merge without missing required reviews or documentation updates.

What is the best way to ensure commit hygiene and CI validation before merging a branch?

Commit hygiene and CI validation are enforced by following a structured task workflow that requires isolated branches, deterministic test runs, and CI verification. This repository-safe coordination keeps work aligned to SPEC.md and AGENTS.md before any merge occurs.

How does cross-model code review work during task tracking?

Cross-model code review during task tracking is handled through structured handoff to sub-agents and documented review artifacts. The workflow applies controlled recovery from failed reviews to ensure quality standards are met before merging.

Do I need a SPEC.md file to run isolated branch testing?

Yes, a SPEC.md file is required to define the individual task being executed. The workflow specifically completes one SPEC.md task per session, adhering to AGENTS.md guidelines while preserving branch discipline and running deterministic validation.

What happens when tests fail during the implementation and review cycle?

When tests fail during the implementation and review cycle, the workflow applies controlled recovery procedures. It isolates the failure within the branch context and re-runs deterministic validation until CI verification passes before proceeding to merge.

Can I include GUI evaluation in an automated task tracking workflow?

Yes, GUI evaluation is included in the task tracking workflow when needed. It operates alongside deterministic validation and code review steps, ensuring visual changes are assessed before the branch is merged and memory updates are applied.