workflow-start

Initialize a work session by outlining tasks and establishing focus from checkpoint paths.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill workflow-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-start
Source: https://github.com/ribatshepo/cc-auto-orchestrate/tree/main/claude-code/skills/workflow-start
Command: npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill workflow-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a work session by reviewing tasks and establishing focus, providing a clear entry point for orchestrating work.

Core Features & Use Cases

  • Initialize a new workflow session and summarize current tasks to establish focus.
  • Support crash recovery by reading the latest checkpoint and reconstructing in-progress work.
  • Resolve a session checkpoint path based on an optional SESSION_ID and fall back to a default path.
  • Retrieve current task state, identify blockers, and propose a focused next action.

Quick Start

Begin a new workflow session by requesting task overview and focus.

Frequently Asked Questions about workflow-start

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

FAQPage Schema
How do I start a work session with task management and crash recovery?

Starting a work session involves initializing a new workflow, summarizing current tasks, and establishing focus. The system reads the latest checkpoint to recover in-progress work and proposes a focused next action.

How does crash recovery work for interrupted task management workflows?

Crash recovery for task management works by reading the latest checkpoint and reconstructing in-progress work. It resolves the session checkpoint path using an optional SESSION_ID or falls back to a default path.

What is a session checkpoint path and when do I need it for workflow orchestration?

A session checkpoint path is a storage location for persisting workflow state, needed when resuming or recovering orchestrated tasks. It is resolved based on an optional SESSION_ID, falling back to a default path if not provided.

Can I retrieve current task state and identify blockers across different contexts?

Yes, you can retrieve the current task state and identify blockers across contexts. The system evaluates existing tasks and proposes a focused next action to guide the session forward.

What is the best way to initialize focused work sessions for complex task management?

The best way to initialize focused work sessions is to request a task overview and focus selection. This outlines pending tasks, resolves checkpoint persistence, and establishes a clear entry point for orchestrating work.

Do I need a specific SESSION_ID to resume a workflow session from a checkpoint?

No, you do not need a specific SESSION_ID to resume a workflow session. The system can resolve a checkpoint path using an optional SESSION_ID and will fall back to a default path if one is not provided.