菜单
Use when the user invokes Qgs or a Qplan handoff needs TASK_REQUEST + VERIFY_CHECKLIST generation. Alias for Qgenerate-spec. Use Qplan for roadmap; use Qexecute after specs exist.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when collecting verified project-local coding guidance into .claude/skills based on the project tech stack, with TTL and user-edit protection.
Shows QE Framework usage overview. With no arg, prints the full catalog. With a skill name arg (e.g., /Qhelp Qcommit), reads that skill's SKILL.md and summarizes it in the user's language. Also supports find/search skills mode via reference/find-skills.md.
QE framework (Query Executor) initial setup. Creates the QE state directory, client-specific instruction/config artifacts, and .gitignore entries in a new project, then auto-analyzes the project. Use when the user wants to initialize a project or set up the framework.
Diagnoses and repairs QE installation health across qe-framework, MCP client config, and the project .qe directory. Use for 'doctor', 'check QE health', dependency verification, corrupted .qe state, or repair guidance. Distinct from Qupdate, which updates installed assets.
Use when executing a TASK_REQUEST/VERIFY_CHECKLIST or when already-changed code needs the test-review-fix quality loop. With no flag it auto-selects sequential or parallel-wave execution; `-verify` runs verification. Use Qautoresearch for iterative code-optimization loops and Qscenario-test for scenario/E2E.
Use when a plan or task needs spec documents: TASK_REQUEST and VERIFY_CHECKLIST. Use Qplan for roadmap/phases; use Qexecute after the spec exists.
| name | Qgs |
| description | Use when the user invokes Qgs or a Qplan handoff needs TASK_REQUEST + VERIFY_CHECKLIST generation. Alias for Qgenerate-spec. Use Qplan for roadmap; use Qexecute after specs exist. |
| user_invocable | true |
| invocation_trigger | When the user wants to generate a spec, create a task, or types /Qgs on Claude or $Qgs on Codex. Also triggered from PSE Chain handoffs after Qplan. |
| recommendedModel | haiku |
| tier | core |
This is the canonical shortcut for Qgenerate-spec.
Qgs is the same skill regardless of client; only the user-visible command
prefix changes.
/Qgs ...$Qgs ...Pass arguments through unchanged after the active client has resolved the skill invocation.
{adapter.commandPrefix}Qmcp ensure before spec generation only when the spec depends on a user-requested MCP server (see Qgenerate-spec → Optional MCP Preflight).Qgenerate-spec.[a-z0-9][a-z0-9-]{0,63} followed by :), Qgenerate-spec treats everything before the colon as the plan slug and reads .qe/planning/plans/{slug}/ROADMAP.md + STATE.md for that plan's active Phase..qe/state/current-session.json → .qe/planning/.sessions/{session_id}.json → .qe/planning/ACTIVE_PLAN, falling back to the flat .qe/planning/ROADMAP.md for legacy projects.Claude:
/Qgs # Interactive — asks for project info
/Qgs auth-refactor: 인증 모듈 # Slug-based — reads plans/auth-refactor/
/Qgs dashboard-v2: Polish # Another plan in parallel — no collision
/Qgs fix login bug # Freeform — generates spec from description
Codex:
$Qgs # Interactive — asks for project info
$Qgs auth-refactor: 인증 모듈 # Slug-based — reads plans/auth-refactor/
$Qgs dashboard-v2: Polish # Another plan in parallel — no collision
$Qgs codex-native-parity: Skill Compatibility
Legacy:
/Qgs Phase 2: Codex Bridgeon Claude, or$Qgs Phase 2: Codex Bridgeon Codex, still works against the flat.qe/planning/ROADMAP.mdfor projects that pre-date Named Plans. New projects always use slug form.
Invoke the Qgenerate-spec skill with the user's full argument string. Do not modify or interpret the arguments — pass them through as-is.