Compare commits

..

No commits in common. "79648dfde2cf819c2d4754c1b55d230ba81fb1b7" and "4409df7c0f43ec74bb8c58852101b40613b163cb" have entirely different histories.

2 changed files with 7 additions and 13 deletions

View File

@ -70,22 +70,14 @@ This file contains the BMAD PRD philosophy, standards, and validation criteria t
**If PRD path provided as invocation parameter:**
- Use provided path
**If no PRD path provided, auto-discover:**
- Search `{planning_artifacts}` for files matching `*prd*.md`
- Also check for sharded PRDs: `{planning_artifacts}/*prd*/*.md`
**If no PRD path provided:**
"**PRD Validation Workflow**
**If exactly ONE PRD found:**
- Use it automatically
- Inform user: "Found PRD: {discovered_path} — using it for validation."
Which PRD would you like to validate?
**If MULTIPLE PRDs found:**
- List all discovered PRDs with numbered options
- "I found multiple PRDs. Which one would you like to validate?"
- Wait for user selection
Please provide the path to the PRD file you want to validate."
**If NO PRDs found:**
- "I couldn't find any PRD files in {planning_artifacts}. Please provide the path to the PRD file you want to validate."
- Wait for user to provide PRD path.
**Wait for user to provide PRD path.**
### 3. Validate PRD Exists and Load

View File

@ -60,4 +60,6 @@ Load and read full config from {main_config} and resolve:
"**Validate Mode: Validating an existing PRD against BMAD standards.**"
Prompt for PRD path: "Which PRD would you like to validate? Please provide the path to the PRD.md file."
Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)