qa-reset

Structures vague development requests into organized checklists using interaction mode and content dimension templates.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/shengmingzhishu/LeeCommonVideoCut --skill qa-reset-shengmingzhishu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-reset
Source: https://github.com/shengmingzhishu/LeeCommonVideoCut/tree/main/.trae/skills/shared/qa-reset
Command: npx skills add https://github.com/shengmingzhishu/LeeCommonVideoCut --skill qa-reset-shengmingzhishu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers and product owners often describe requirements in scattered, ambiguous language, leading to misunderstood tasks and wasted implementation effort. This Skill acts as a requirement refiner that identifies how the user wants to interact and which development phase the request belongs to, then restructures the input into clear, confirmable checklists before any code changes happen. ## Core Features & Use Cases - Seven Interaction Modes: Detects clarification, single execution, batch orchestration, correction feedback, exploration evaluation, blocking emergencies, and rollback requests, each with a dedicated response template. - Five Content Dimensions: Classifies requests into requirement design, coding, task breakdown, stage progression, or scenario testing, and applies the matching structured template. - Batch Request Handling: Numbers mixed questions (Q1, Q2...), builds an overview table, escalates blocking items to the front, and consolidates all pending confirmations. - Use Case: A user pastes five mixed requests about a video-cutting web app, including a blocked dev server and a UI tweak. The Skill outputs an execution strategy, a summary table, per-item structured plans with the blocking item first, and a consolidated confirmation list. ## Quick Start Type /qa-reset followed by your raw development request, or simply describe your requirements and let the Skill restructure them into a confirmed checklist before execution.

Frequently Asked Questions about qa-reset

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

FAQPage Schema
How do I structure vague software requirements before coding?▼

Classify the request by interaction mode (clarification, execution, batch, correction, evaluation, blocking, rollback) and content dimension (design, coding, task breakdown, progression, testing), then apply the matching structured template. Confirm the organized checklist with the requester before implementing.

How to handle multiple development questions in one message?▼

Number each independent question as Q1, Q2, and so on, tag each with its interaction mode and content dimension, and build an overview table. Expand each item with its template, move blocking issues to the front, and consolidate all pending confirmations at the end.

When should requirement structuring be skipped?▼

Skip full templates for pure clarification questions, which only need a direct explanation, and for single clear execution tasks, which need only brief confirmation. Over-structuring simple requests slows down the workflow without adding clarity.

How do I handle a correction when requirements were misunderstood?▼

Mark the previous understanding as deprecated, list the user's correction points, and regenerate the structured plan from scratch using the appropriate template. Do not patch the old interpretation; reset the context and confirm the new understanding.

What should happen when a blocking issue appears in a batch request?▼

Move the blocking item to the front of the output, describe its impact scope and which tasks can proceed in parallel, propose a solution with estimated effort, and resume the remaining task queue once the blocker is resolved.