ren-wu-shou-wei-qi

Name: ren-wu-shou-wei-qi
Availability: InStock
Author: dalomeve

Validate task completion with DONE_CHECKLIST and EVIDENCE artifacts.

3|Updated Feb 28, 2026

Search Tags:#automation #workflow #communication #completion #evidence #task #project-management

Ready to run

npx skills add https://github.com/Dalomeve/bot-output --skill ren-wu-shou-wei-qi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ren-wu-shou-wei-qi
Source: https://github.com/Dalomeve/bot-output/tree/main/skills/ren-wu-shou-wei-qi
Command: npx skills add https://github.com/Dalomeve/bot-output --skill ren-wu-shou-wei-qi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a mandatory wrap-up mechanism that ensures every substantive task ends with a clear goal, visible progress, a defined next action, and a verifiable completion artifact, preventing mid-task stalls and missing evidence.

Core Features & Use Cases

Enforced closure for each meaningful step: emit a goal, progress, and next action.
Evidence-first completion: multi-step tasks include DONE_CHECKLIST and EVIDENCE artifacts.
Structured handoffs and recovery: supports start, progress updates, and next autonomous steps for seamless transitions.
Use cases: project coordination among agents, multi-step workflows, and post-task verification.

Quick Start

Start a task by stating the goal, current progress, and the next concrete action, then supply DONE/EVIDENCE when milestones are reached.

Frequently Asked Questions about ren-wu-shou-wei-qi

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

FAQPage Schema

How do I enforce task completion with verifiable evidence in an automated workflow?▼

To enforce task completion with verifiable evidence, you need a mandatory wrap-up mechanism that requires explicit DONE and EVIDENCE formats before a multi-step workflow can close. This prevents mid-task stalls by validating visible progress and defined next actions.

What is the best way to handle task handoffs and recovery after interruptions in project management?▼

Handling task handoffs and recovery after interruptions requires structured progress updates that state the goal, current progress, and next autonomous step. This structured completion policy supports seamless transitions and explicit recovery actions.

How do I prevent mid-task stalls in multi-step agent workflows?▼

Preventing mid-task stalls in multi-step agent workflows involves applying an enforced closure policy for each meaningful step. This requires emitting a goal, progress update, and next action, alongside a DONE_CHECKLIST to verify completion artifacts.

Do I need a specific framework to validate task completion artifacts and progress tracking?▼

You do not need a specific framework to validate task completion artifacts and progress tracking. The validation relies on defined prompts and output formats requiring goals, progress, next actions, and verifiable evidence.

When do I need to use an evidence-first completion policy for project coordination?▼

You need an evidence-first completion policy for project coordination when executing multi-step workflows, agent handoffs, or post-task verification. It ensures every substantive task concludes with verifiable artifacts and explicit DONE formats.