Gustavosareto/gsd-verify-work

<augment_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-verify-work or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Augment tools when executing GSD workflows:

• launch-process for running commands (terminal operations)
• str-replace-editor for editing existing files
• view for reading files and listing directories
• save-file for creating new files
• grep for searching code (or use MCP servers for advanced search)
• web-search, web-fetch for web queries
• add_tasks, view_tasklist, update_tasks for task management

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use the built-in subagent spawning capability
• Define agent prompts in .augment/agents/ directory </augment_skill_adapter>

<objective> Validate built features through conversational testing with persistent state.

Purpose: Confirm what Claude 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> @C:/Users/gusta/OneDrive/Documentos/gerenciador-de-quadras/.augment/get-shit-done/workflows/verify-work.md @C:/Users/gusta/OneDrive/Documentos/gerenciador-de-quadras/.augment/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 @C:/Users/gusta/OneDrive/Documentos/gerenciador-de-quadras/.augment/get-shit-done/workflows/verify-work.md end-to-end. Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing). </process>