workflow

Orchestrate plan-first development workflows with persistent state and gate checks.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/pzheng460/claude-workflow-plugin --skill workflow-pzheng460
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/pzheng460/claude-workflow-plugin/tree/main/skills/workflow
Command: npx skills add https://github.com/pzheng460/claude-workflow-plugin --skill workflow-pzheng460

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, stateful orchestration to manage non-trivial coding tasks so teams and AI agents do not lose context across sessions, take unsafe shortcuts, or introduce unreviewed black-box changes by enforcing a plan-first discipline.

Core Features & Use Cases

  • 5-step plan-first workflow: Brainstorm → Plan → Execute → Verify → Close with explicit gates between steps.
  • Persistent state and recovery: Stores workflow state in .claude/workflow-state to resume, enforce single active workflows, TTL-based cleanup, and abort protocols.
  • Verification and explainability: Mandatory test and diff checks, acceptance criteria enforcement, and review-implementation integration to ensure traceable changes.
  • Composition and integrations: Converts issues to plan-first PRs, creates feature branches, supports sub-agent decomposition for large tasks, and offers fast-track flows for trivial changes.
  • Use case: Turn a complex GitHub issue into an approved implementation plan, branch, verified changes, and a final PR with archived decisions and artifacts.

Quick Start

Start a new workflow for implementing feature X and produce a reviewable plan and persistent state file.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I enforce a plan-first development workflow for complex coding tasks?

A plan-first development workflow enforces structured phases—brainstorm, plan, execute, verify, and close—with explicit gate checks between steps to prevent unreviewed black-box changes and ensure traceable implementation.

How do I convert a GitHub issue into a reviewable plan and pull request?

Converting issues to plan-first PRs involves orchestrating a structured workflow that transforms a GitHub issue into an approved implementation plan, feature branch, verified changes, and a final PR with archived decisions.

Can I resume an interrupted coding workflow without losing context across sessions?

Persistent workflow state files stored in .claude/workflow-state enable session recovery, enforce single active workflows, provide TTL-based cleanup, and support abort protocols to resume interrupted coding tasks without losing context.

Does a strict development workflow support fast-track paths for trivial mechanical changes?

A fast-track path exists for trivial mechanical changes, bypassing the full 5-step plan-first workflow to allow quick execution while maintaining overall plan-first discipline for non-trivial coding tasks.

How do I decompose large coding tasks into manageable sub-agents?

Sub-agent decomposition breaks down large coding tasks within the execution phase of a structured workflow, allowing complex implementations to be coordinated and verified as manageable, isolated components.

What is the best way to verify code changes before closing a development workflow?

Mandatory test and diff checks, acceptance criteria enforcement, and review-implementation integration verify code changes before closure, ensuring all modifications are traceable and meet the original plan's requirements.