nacl-tl-reopened

Coordinate fixes, reviews, stubs checks, and shipping for reopened QA tasks.

23|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-reopened
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nacl-tl-reopened
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-reopened
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-reopened

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reopened tasks in YouGile require structured triage, root-cause analysis, and coordinated fixes across the full stack. This Skill automates the orchestration and handoff between verification/QA feedback and the fix/shipping workflow.

Core Features & Use Cases

  • Orchestrates the end-to-end reopen flow: fetch tester feedback, plan fixes, delegate to nacl-tl-fix, run reviews, perform stubs checks, and ship.
  • Maintains task context and status updates across nacl-tl-fix, nacl-tl-review, nacl-tl-stubs, nacl-tl-ship, and YouGile DevDone.
  • Escalation: if a task has been reopened 2+ times, it escalates to the user.

Use case: When a task in Reopened fails verification, this skill triggers a fix plan and tracks progression until DevDone.

Quick Start

Invoke /nacl-tl-reopened to process a reopened YouGile task end-to-end.

Frequently Asked Questions about nacl-tl-reopened

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

FAQPage Schema
How do I automate the workflow for reopened QA tasks?

Automating reopened QA tasks is handled by orchestrating fixes, reviews, and deployment steps end-to-end. The workflow fetches tester feedback, delegates fixes, runs reviews, performs stubs checks, and ships updates while maintaining task context and status.

What happens when a QA task is reopened multiple times?

When a reopened QA task fails verification multiple times, an escalation rule triggers. If the task has been reopened two or more times, the workflow automatically escalates the issue directly to the user for manual intervention.

How do I coordinate fixes and reviews for failed verification tasks?

You coordinate fixes and reviews for failed verification tasks by triggering an automated multi-step workflow. This process delegates fixes, runs automated reviews, performs stubs checks, and tracks progression until the task reaches DevDone status.

Can I track status updates across fix, review, and shipping steps for reopened tasks?

You can track status updates across fix, review, and shipping steps because the workflow maintains task context and progression states. It propagates status updates across fix, review, stubs, and shipping stages until the task reaches DevDone.

What is the best way to handle rework for reopened QA tasks?

The best way to handle rework for reopened QA tasks is using a structured triage and root-cause analysis workflow. This automates the handoff between verification feedback and the fix or shipping pipeline, ensuring coordinated fixes across the full stack.

Does the reopened task workflow require any specific dependencies?

The reopened task workflow operates without specific external dependencies, but it orchestrates internal workflow components. It delegates execution to fix, review, stubs check, and shipping modules to process the task end-to-end.