taskflow

Enforce a four-checkpoint workflow with mandatory state tracking and verifiable evidence across code and data tasks.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/wjy0705/taskFlow-skill --skill taskflow-wjy0705
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskflow
Source: https://github.com/wjy0705/taskFlow-skill/tree/main
Command: npx skills add https://github.com/wjy0705/taskFlow-skill --skill taskflow-wjy0705

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Task Flow enforces a disciplined, verifiable AI workflow that prevents hallucinations and wasted tokens by mandating explicit stage checks, state tracking, and graceful degradation.

Core Features & Use Cases

  • Explicit four-checkpoint process (Understanding, Capability & Tooling, Evidence-based Verification, Fallback).
  • Mandatory state-tracking: outputs [当前阶段:...] at the start of each reply for traceability.
  • Environment graceful degradation: when commands can't run, auto-generate verifiable test scripts for humans.
  • Cross-platform applicability: suitable for coding, debugging, operations, and analysis tasks.

Quick Start

Trigger Task Flow with /taskflow to start the four-checkpoint protocol and guide you through understanding, capability selection, evidence verification, and safe stop.

Frequently Asked Questions about taskflow

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

FAQPage Schema
How do I prevent AI hallucinations and wasted tokens during complex coding tasks?

Preventing AI hallucinations requires enforcing an explicit four-checkpoint workflow with mandatory state tracking to verify problem understanding, capability selection, and evidence-based validation. This approach uses verifiable outputs like stdout, diffs, or runnable test scripts to ensure accuracy.

What is an evidence-based verification workflow for AI-generated code?

An evidence-based verification workflow requires verifiable evidence such as stdout, diffs, or screenshots to validate AI outputs. When direct command execution is unavailable, it automatically generates runnable test scripts for human validation to ensure environment-bound accuracy.

How to implement state tracking for AI task traceability across debugging and analysis?

Implement state tracking by mandating the AI to output current stage markers like [当前阶段:...] at the start of each reply. This provides full traceability across understanding, capability selection, verification, and fallback stages throughout coding and analysis tasks.

Can I apply a structured guardrail workflow to both data and text tasks?

Yes, a structured guardrail workflow applies cross-platform to coding, debugging, operations, and text analysis tasks. It enforces graceful degradation by generating verifiable test scripts for humans when direct environment commands cannot run.

What is the best way to handle environment graceful degradation when AI validation commands fail?

Environment graceful degradation handles validation failures by automatically generating runnable test scripts for humans to execute. This ensures that evidence-based verification continues even when the AI cannot directly run commands in the target environment.

Why does my AI workflow lack traceability across different task stages?

AI workflows lack traceability when they skip explicit state tracking checkpoints during execution. Enforcing a four-checkpoint protocol with mandatory stage outputs at the start of each reply restores traceability across understanding, capability selection, verification, and fallback phases.