play

Orchestrate sequential agent reviews to log defects as GitHub issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/krystophny/prompts --skill play
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: play
Source: https://github.com/krystophny/prompts/tree/main/skills/play
Command: npx skills add https://github.com/krystophny/prompts --skill play

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables structured defect discovery by orchestrating an agent sequence to review repositories and log issues on GitHub, ensuring no file modifications occur.

Core Features & Use Cases

  • Agent sequence coordination: Orchestrates max-devops-engineer, patrick-reviewer, vicky-acceptance-tester, and chris-architect in order to surface defects.
  • Non-destructive workflow: Operations rely on GitHub API reads and issue creation; no file changes to source.
  • Structured reporting: Creates GitHub issues with clear descriptions, reproduction steps, and code references.

Use Case: During a sprint review, the agent sequence surfaces a defect and logs a GitHub issue with all pertinent details.

Quick Start

Initiate a sprint review and run the agent sequence to surface defects and create GitHub issues.

Frequently Asked Questions about play

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

FAQPage Schema
How do I automate defect discovery during a sprint review without modifying source files?

Automate defect discovery by orchestrating an agent sequence that reviews repositories and logs issues on GitHub. This non-destructive workflow relies on GitHub API reads and issue creation, ensuring no source code files are changed during the sprint review.

How does an agent sequence create GitHub issues for code reviews?

An agent sequence coordinates specific roles to review code and surface defects. It automatically creates well-labeled GitHub issues containing clear descriptions, reproduction steps, and code references based on the findings from the code review.

Can I use an automated defect discovery workflow for QA cycles?

Yes, you can use this workflow for QA cycles where defects must be captured as issues. The agent sequence applies to QA cycles by logging issues on GitHub without modifying source files, ensuring structured reporting of all discovered defects.

What is the best way to capture code review defects as structured GitHub issues?

The best way to capture code review defects is using an agent-driven workflow that creates GitHub issues with clear descriptions, reproduction steps, and evidence. This approach enforces no file changes while coordinating agent roles to systematically surface defects.

Do I need specific agent roles to automate defect discovery on GitHub?

Yes, the defect discovery process coordinates specific agent roles including max-devops-engineer, patrick-reviewer, vicky-acceptance-tester, and chris-architect. These agents work in sequence to review repositories and log structured GitHub issues.