long-task-skill-family-skill

Orchestrate multi-phase planning, splitting, and implementation with durable state and 95% readiness gates.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/almazom/agents_slash_skills --skill long-task-skill-family-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: long-task-skill-family-skill
Source: https://github.com/almazom/agents_slash_skills/tree/main/long-task-skill-family-skill
Command: npx skills add https://github.com/almazom/agents_slash_skills --skill long-task-skill-family-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Run a durable manager-owned long session across planning, splitting, and implementation with session_state.json, reuse-first pane policy, and 95% phase gates.

Core Features & Use Cases

  • Orchestrates alignment across plan, split, and implementation phases.
  • Maintains a single source of truth with session_state.json and kanban.json for execution state.
  • Enforces readiness gates at 95% before advancing phases and supports pane continuity.

Quick Start

Start a new durable run and advance through plan, split, and implementation phases.

Frequently Asked Questions about long-task-skill-family-skill

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

FAQPage Schema
How do I orchestrate durable multi-phase workflows with strict phase gates?

Durable multi-phase workflows are orchestrated by enforcing readiness gates at 95% before advancing through planning, splitting, and implementation phases using session_state.json for continuity.

What is the best way to maintain state across long-running task families?

Maintaining state across long-running task families requires a durable session_state.json file and kanban.json for execution truth, ensuring single source of truth throughout the workflow.

Can I enforce readiness checks before advancing workflow phases?

Readiness checks are enforced at 95% before phase progression, acting as gates between planning, splitting, and implementation phases to ensure durable task completion.

How do I split a long-running plan into implementation tasks?

Splitting a long-running plan into implementation tasks is handled by the split-to-tasks phase, which feeds into kanban.json for execution truth and tracks progress through durable state.

Do I need a kanban board for durable workflow orchestration?

A kanban.json file is required as the single source of execution truth, tracking task progression across phases while session_state.json maintains pane continuity for the durable run.

Why use phase gates in multi-phase task orchestration?

Phase gates in multi-phase task orchestration prevent premature advancement by enforcing 95% readiness checks, ensuring each planning and splitting phase completes before implementation begins.