Qgs

Generate TASK_REQUEST and VERIFY_CHECKLIST spec documents from prompts.

6|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qgs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Qgs
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qgs
Command: npx skills add https://github.com/inho-team/qe-framework --skill qgs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of project specifications (TASK_REQUEST + VERIFY_CHECKLIST) by acting as a shortcut to /Qgenerate-spec, reducing manual drafting time and ensuring consistent planning artifacts.

Core Features & Use Cases

  • Generates complete spec documents from natural language prompts or plan slugs.
  • Resolves the active plan from the project state or falls back to ROADMAP when needed for legacy projects.
  • Passes user-provided arguments through to the /Qgenerate-spec process without interpretation, preserving intent.

Quick Start

Type /Qgs followed by a plan slug or description to generate a spec instantly.

Frequently Asked Questions about Qgs

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

FAQPage Schema
How do I generate spec documents from a plan slug?

You can generate spec documents by providing a plan slug or natural language description as a command argument. The system automatically resolves the active project state or legacy ROADMAP to produce the required TASK_REQUEST and VERIFY_CHECKLIST artifacts.

What is the fastest way to automate product spec creation?

Automating product spec creation is fastest through a single shortcut command that triggers the underlying spec generator. It translates your natural language prompts directly into structured TASK_REQUEST and VERIFY_CHECKLIST documents without manual drafting.

How do spec generation shortcuts handle existing project ROADMAPs?

Spec generation shortcuts automatically read the active plan state from your project environment. If the active state is unavailable, the system falls back to reading the legacy ROADMAP to resolve the necessary plan details for document generation.

Can I pass custom arguments through to the spec generator without modification?

Yes, all user-provided arguments are passed directly to the underlying spec generation process without interpretation or modification. This ensures your original intent and parameters are fully preserved in the final output.

Do I need an active plan state to generate a TASK_REQUEST and VERIFY_CHECKLIST?

No, an active plan state is not strictly required to generate a TASK_REQUEST and VERIFY_CHECKLIST. The system will attempt to read the active project state first, but it can successfully fall back to resolving legacy ROADMAP files when needed.