gsd-verify-work — for Claude Code gsd-verify-work, crust-design-plugin, community, for Claude Code, ide skills, $gsd-verify-work, {{GSD_ARGS}}, AskUserQuestion, request_user_input, header

v1.0.0
GitHub

À propos de ce Skill

Scenario recommande : Ideal for AI agents that need <codex skill adapter. Resume localise : Internal Chromium extension for sharing live design experiments on real websites. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Fonctionnalités

<codex skill adapter
A. Skill Invocation
This skill is invoked by mentioning $gsd-verify-work.
Treat all user text after $gsd-verify-work as {{GSD ARGS}}.
If no arguments are present, treat {{GSD ARGS}} as empty.

# Sujets clés

for Claude Code $gsd-verify-work {{GSD_ARGS}} AskUserQuestion request_user_input header
andreashxc andreashxc
[1]
[0]
Mis à jour: 4/29/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

Scenario recommande : Ideal for AI agents that need <codex skill adapter. Resume localise : Internal Chromium extension for sharing live design experiments on real websites. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Pourquoi utiliser cette compétence

Recommandation : gsd-verify-work helps agents <codex skill adapter. Internal Chromium extension for sharing live design experiments on real websites. This AI agent skill supports Claude Code, Cursor, and Windsurf

Meilleur pour

Scenario recommande : Ideal for AI agents that need <codex skill adapter.

↓ Cas d'utilisation exploitables for gsd-verify-work

Cas d'usage : Applying <codex skill adapter
Cas d'usage : Applying A. Skill Invocation
Cas d'usage : Applying This skill is invoked by mentioning $gsd-verify-work

! Sécurité et Limitations

  • Limitation : Requires repository-specific context from the skill documentation
  • Limitation : Works best when the underlying tools and dependencies are already configured

About The Source

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Démo Labs

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ et étapes d’installation

These questions and steps mirror the structured data on this page for better search understanding.

? Questions fréquentes

Qu’est-ce que gsd-verify-work ?

Scenario recommande : Ideal for AI agents that need <codex skill adapter. Resume localise : Internal Chromium extension for sharing live design experiments on real websites. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Comment installer gsd-verify-work ?

Exécutez la commande : npx killer-skills add andreashxc/crust-design-plugin/gsd-verify-work. Elle fonctionne avec Cursor, Windsurf, VS Code, Claude Code et plus de 19 autres IDE.

Quels sont les cas d’usage de gsd-verify-work ?

Les principaux cas d’usage incluent : Cas d'usage : Applying <codex skill adapter, Cas d'usage : Applying A. Skill Invocation, Cas d'usage : Applying This skill is invoked by mentioning $gsd-verify-work.

Quels IDE sont compatibles avec gsd-verify-work ?

Cette skill est compatible avec Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Utilisez la CLI Killer-Skills pour une installation unifiée.

Y a-t-il des limites pour gsd-verify-work ?

Limitation : Requires repository-specific context from the skill documentation. Limitation : Works best when the underlying tools and dependencies are already configured.

↓ Comment installer ce skill

  1. 1. Ouvrir le terminal

    Ouvrez le terminal ou la ligne de commande dans le dossier du projet.

  2. 2. Lancer la commande d’installation

    Exécutez : npx killer-skills add andreashxc/crust-design-plugin/gsd-verify-work. La CLI détectera automatiquement votre IDE ou votre agent et configurera la skill.

  3. 3. Commencer à utiliser le skill

    Le skill est maintenant actif. Votre agent IA peut utiliser gsd-verify-work immédiatement dans le projet.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

gsd-verify-work

Internal Chromium extension for sharing live design experiments on real websites. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

SKILL.md
Readonly
Upstream Repository Material
The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-verify-work.
  • Treat all user text after $gsd-verify-work as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • header → header
  • question → question
  • Options formatted as "Label" — description → {label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y") → spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit. spawn_agent has no inline model parameter; GSD embeds the resolved per-agent model directly into each agent's .toml at install time so model_overrides from .planning/config.json and ~/.gsd/defaults.json are honored automatically by Codex's agent router.
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Spawn restriction:

  • Codex restricts spawn_agent to cases where the user has explicitly requested sub-agents. When automatic spawning is not permitted, do the work inline in the current agent rather than attempting to force a spawn.

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<objective> Validate built features through conversational testing with persistent state.

Purpose: Confirm what the agent built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.

Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for $gsd-execute-phase </objective>

<execution_context> @/Users/andreas/Library/Mobile Documents/comappleCloudDocs/Code/gsd-test/.codex/get-shit-done/workflows/verify-work.md @/Users/andreas/Library/Mobile Documents/comappleCloudDocs/Code/gsd-test/.codex/get-shit-done/templates/UAT.md </execution_context>

<context> Phase: {{GSD_ARGS}} (optional) - If provided: Test specific phase (e.g., "4") - If not provided: Check for active sessions or prompt for phase

Context files are resolved inside the workflow (init verify-work) and delegated via <files_to_read> blocks. </context>

<process> Execute the verify-work workflow from @/Users/andreas/Library/Mobile Documents/com~apple~CloudDocs/Code/gsd-test/.codex/get-shit-done/workflows/verify-work.md end-to-end. Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing). </process>

Compétences associées

Looking for an alternative to gsd-verify-work or another community skill for your workflow? Explore these related open-source skills.

Voir tout

openclaw-release-maintainer

Logo of openclaw
openclaw

Resume localise : 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
Intelligence artificielle

widget-generator

Logo of f
f

Resume localise : Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

★ 149.6k
⑂ 0
Intelligence artificielle

flags

Logo of vercel
vercel

Resume localise : The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
Navigateur

pr-review

Logo of pytorch
pytorch

Resume localise : Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 98.6k
⑂ 0
Développeur