dryrun-human

Simulate human stakeholder responses in STI dry-run ticket workflows.

Updated Aug 23, 2026

Search Tags:#workflow #decision #stakeholder #ticket #dry-run #human-responses #stopper

Ready to run

npx skills add https://github.com/gapfDev/workflow --skill dryrun-human

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dryrun-human
Source: https://github.com/gapfDev/workflow/tree/main/.claude/skills/dryrun-human
Command: npx skills add https://github.com/gapfDev/workflow --skill dryrun-human

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Dry Run — Human Agent provides a realistic human stakeholder persona to participate in STI dry-run tests, enabling accurate decision-making and validation without exposing real agents.

Core Features & Use Cases

Simulates a realistic human stakeholder who files and reviews tickets during STI dry runs.
Writes responses only to temp/dryrun/{V}/[ticket-id]/human-responses.md and reads allowed input from temp/dryrun/{V}/[ticket-id]/synthetic-ticket.md and pending-stopper.md as specified.
Ensures adherence to STOPPER flow, providing decision feedback at S1/S2/S3/S4 stages.

Quick Start

Review the synthetic ticket at temp/dryrun/{V}/[ticket-id]/synthetic-ticket.md and start recording your human responses in temp/dryrun/{V}/[ticket-id]/human-responses.md.

Frequently Asked Questions about dryrun-human

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

FAQPage Schema

How do I simulate a human stakeholder for an STI dry-run workflow?▼

To simulate a human stakeholder for an STI dry-run workflow, this Skill provides realistic ticket input and decision feedback at S1, S2, S3, and S4 stopper points without exposing real agents. It enforces STOPPER workflow rules to validate decisions accurately.

What is a stopper decision point in dry-run ticket workflows?▼

A stopper decision point in dry-run ticket workflows is a stage requiring human input or approval, such as S1 input, S2 intake, or S3/S4 flow. This Skill enforces these rules and generates human responses to validate the process.

How do I record human responses during a dry-run test?▼

To record human responses during a dry-run test, the Skill writes exclusively to the temp/dryrun/{V}/[ticket-id]/human-responses.md file. It reads allowed input from synthetic-ticket.md and pending-stopper.md to generate accurate stakeholder feedback.

Can I use this for STI dry runs without exposing real agents?▼

Yes, you can use this for STI dry runs without exposing real agents. It simulates a realistic human stakeholder who files and reviews tickets, providing necessary decision feedback while keeping actual agents safe during validation.

Does the dry-run human agent read from any context source available?▼

No, the dry-run human agent does not read from any context source available. It strictly reads only from allowed input files like synthetic-ticket.md and pending-stopper.md located in the temp/dryrun directory structure.

Why does my dry-run workflow need a simulated human stakeholder?▼

A dry-run workflow needs a simulated human stakeholder to enable accurate decision-making and validation at stopper points. It provides realistic ticket input and feedback, ensuring the workflow functions correctly before involving actual human agents.