docs: add blocking requirement to monitor and respond to PR feedback

Updates PROMPT.md to enforce that Contributors must:
- Check for open PR feedback BEFORE starting new work (blocking)
- Implement requested fixes immediately using TDD
- Self-verify with build and tests
- Reply to comments with verification confirmation
- NOT proceed to new tasks while PRs have unresolved feedback

Updated in three locations:
1. EXTREMELY-IMPORTANT section (blocking requirement)
2. Workflow Rules section (steps 3-4, 14)
3. Instructions for Claude (steps 2, 10)

This ensures Contributors prioritize addressing review feedback
over starting new tasks, improving PR turnaround time.

Author: martincjarvis

PROMPT.md

@@ -13,6 +13,12 @@
 >   - See CLAUDE.local.md "CRITICAL: Verify Both Git and GitHub CLI Credentials" section
 > - All changes need to be done via feature branch and merged via PR
 > - Work as `Contributor` implementing code changes and raising PR's. Do not review PR's unless explicitly prompted by the user - just monitor active PR and Issues for comment feedback.
+> - **BLOCKING: Monitor ALL open PRs for feedback**
+>   - Check open PRs created by Contributor account for comments or "Changes requested" reviews
+>   - Implement requested fixes immediately using TDD approach
+>   - Self-verify fixes with `dotnet build --warnaserror && dotnet test`
+>   - Reply to review comments with: "Fixed. Changes verified - ready for re-review."
+>   - DO NOT proceed to new tasks while open PRs have unresolved feedback
 
 </EXTREMELY-IMPORTANT>
 
@@ -110,15 +116,17 @@ See **[docs/plans/rules-engine-design.md](docs/plans/rules-engine-design.md)** f
 
 1. **FIRST: Verify credentials** - Run `./scripts/verify-credentials.sh contributor` before any work
 2. Work as Contributor
-3. Check for GitHub issue before any work
-4. Create feature branch: `feature/<issue>-<description>`
-5. Write failing tests first
-6. Implement to pass tests
-7. Run `dotnet build --warnaserror && dotnet test`
-8. **BEFORE COMMIT: Re-verify credentials** - Run `./scripts/verify-credentials.sh contributor`
-9. Commit with: `<type>: <description>\n\nRefs #<issue>`
-10. **BEFORE PR: Re-verify credentials** - Run `./scripts/verify-credentials.sh contributor`
-11. Create PR and request review
+3. **BLOCKING: Check for open PR feedback** - Run `gh pr list --author martincjarvis --state open` and check for review comments
+4. **If PR has feedback**: Implement requested changes immediately (skip to new tasks only after all feedback resolved)
+5. Check for GitHub issue before any work
+6. Create feature branch: `feature/<issue>-<description>`
+7. Write failing tests first
+8. Implement to pass tests
+9. Run `dotnet build --warnaserror && dotnet test`
+10. **BEFORE COMMIT: Re-verify credentials** - Run `./scripts/verify-credentials.sh contributor`
+11. Commit with: `<type>: <description>
+
+Refs #<issue>`12. **BEFORE PR: Re-verify credentials** - Run`./scripts/verify-credentials.sh contributor` 13. Create PR and request review 14. **AFTER PR: Monitor for feedback** - Check PR regularly for review comments and respond immediately
 
 ### Commit Types
 
@@ -139,10 +147,12 @@ Reference `docs/design/` for game mechanics specifications (gdd-core.md, gdd-cla
 1. Read these files in order:
    - `CLAUDE.md` and `AGENTS.md` - Project rules and workflows
    - `docs/plans/rules-engine-design.md` - Architecture, design, and progress
-2. Check Epic Status Overview for current progress and next tasks
-3. For completed epics, examine Code Reference paths for implementation patterns
-4. Reference `docs/design/gdd-*.md` for game mechanics details
-5. Always reference the GitHub issue in commits
-6. Use TDD - write failing tests before implementation
-7. Run verification: `dotnet build --warnaserror && dotnet test`
-8. Update progress tracking after completing tasks
+2. **BLOCKING: Check for open PR feedback FIRST** - Run `gh pr list --author martincjarvis --state open` and prioritize addressing any review comments
+3. Check Epic Status Overview for current progress and next tasks
+4. For completed epics, examine Code Reference paths for implementation patterns
+5. Reference `docs/design/gdd-*.md` for game mechanics details
+6. Always reference the GitHub issue in commits
+7. Use TDD - write failing tests before implementation
+8. Run verification: `dotnet build --warnaserror && dotnet test`
+9. Update progress tracking after completing tasks
+10. After creating PR, monitor for feedback and respond immediately