feat(verify): suggest product doc updates after spec verification

[workshur]

Summary

After completing spec verification, check if product context documents need updates based on implementation learnings and suggest actionable /awos:* commands.

Motivation

During implementation, teams often discover architectural changes or product refinements that should be documented. This enhancement ensures those learnings are captured by prompting users to update product docs when relevant.

Changes

• Add Step 5 "Review Product Context" to verification flow
• Check architecture.md, product-definition.md, roadmap.md against actual implementation
• Suggest specific /awos:* commands with prompts when discrepancies are found

Test plan

• Run /awos:verify on a completed spec
• Confirm product doc review step executes
• Verify actionable command suggestions are formatted correctly

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Enhances the /awos:verify workflow to prompt users to reconcile implementation learnings with higher-level product context documentation by suggesting actionable follow-up /awos:* commands.

Changes:

• Adds an optional output to /awos:verify: suggested /awos:* commands when product context docs should be updated.
• Introduces a new “Review Product Context” step that compares context/product/* docs against the implemented reality and suggests targeted update commands.

[Copilot]

In Step 5, the listed product documents are referenced as architecture.md, product-definition.md, and roadmap.md, but elsewhere the workflow treats these as files under context/product/ (e.g., Step 4 updates context/product/roadmap.md). To avoid ambiguity for the agent/user, please reference the full paths here as well (e.g., context/product/architecture.md, context/product/product-definition.md, context/product/roadmap.md).

Suggested change

	1. **Read product documents:** `architecture.md`, `product-definition.md`, `roadmap.md`
	2. **Compare against implementation:** Does the actual implementation match what's documented?
	3. **If discrepancies found:** Tell the user which command to run with a specific prompt:
	- **product-definition.md outdated:** `/awos:product <prompt describing what changed>`
	- **architecture.md outdated:** `/awos:architecture <prompt describing what changed>`
	- **roadmap.md outdated:** `/awos:roadmap <prompt describing what changed>`
	1. **Read product documents:** `context/product/architecture.md`, `context/product/product-definition.md`, `context/product/roadmap.md`
	2. **Compare against implementation:** Does the actual implementation match what's documented?
	3. **If discrepancies found:** Tell the user which command to run with a specific prompt:
	- **`context/product/product-definition.md` outdated:** `/awos:product <prompt describing what changed>`
	- **`context/product/architecture.md` outdated:** `/awos:architecture <prompt describing what changed>`
	- **`context/product/roadmap.md` outdated:** `/awos:roadmap <prompt describing what changed>`