djug

Centralizes four-stage decision anchors for startup, execution, acceptance, and correction workflows.

4|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/ssdiwu/diwu-workflow --skill djug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: djug
Source: https://github.com/ssdiwu/diwu-workflow/tree/main/skills/djug
Command: npx skills add https://github.com/ssdiwu/diwu-workflow --skill djug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Judgement anchors centralize management: all decision-type rules are organized by task stage into a four-stage index, providing a clear framework for when to proceed, pause, or require human input.

Core Features & Use Cases

  • Centralized four-stage decision framework (startup, implementation, acceptance, correction) with example anchors.
  • Provides explicit positive, negative, and boundary examples to guide actions and risk handling.
  • Supports edge-case handling, gating, and recording decisions to ensure traceability across tasks.

Quick Start

Identify the current phase and decision target, and provide it to the system to receive an appropriate decision anchor set.

Frequently Asked Questions about djug

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

FAQPage Schema
What are stage-based decision anchors in workflow governance?

Stage-based decision anchors centralize workflow governance by organizing rules into a four-stage index, guiding when to proceed, pause, or require human input during task progression.

How do I apply four-stage gating to software development tasks?

Apply four-stage gating by identifying the current phase and decision target, then receiving an appropriate decision anchor set to enforce explicit positive, negative, and boundary examples for execution.

Can I use this decision framework for operational workflows with edge cases?

Yes, this decision framework supports operational workflows by handling edge cases, enforcing stage-based gating, and recording decisions to ensure traceability across complex tasks.

What is the best way to manage human-in-the-loop decisions in project tasks?

Manage human-in-the-loop decisions by applying a centralized four-stage decision framework that explicitly defines when tasks require human input and records the execution flow for traceability.

When should I not use a stage-bound decision anchor framework?

Avoid using stage-bound decision anchors for tasks that lack distinct startup, execution, acceptance, and correction phases, or when continuous flow execution is required without risk assessment gating.