Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
40 lines
1.2 KiB
Markdown
40 lines
1.2 KiB
Markdown
---
|
|
name: msd:verify-work
|
|
description: Validate built features through conversational UAT
|
|
argument-hint: "[phase number, e.g., '4'] [--ws <name>]"
|
|
allowed-tools:
|
|
- Read
|
|
- Bash
|
|
- Glob
|
|
- Grep
|
|
- Edit
|
|
- Write
|
|
- Agent
|
|
requires: [execute-phase, phase]
|
|
---
|
|
<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 /msd:execute-phase
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/msd-core/workflows/verify-work.md
|
|
@~/.claude/msd-core/templates/UAT.md
|
|
</execution_context>
|
|
|
|
<context>
|
|
Phase: $ARGUMENTS (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 `<required_reading>` blocks.
|
|
</context>
|
|
|
|
<process>
|
|
Execute end-to-end.
|
|
Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).
|
|
</process>
|