fix wording in create-epics-and-stories doc discovery continuation
This commit is contained in:
parent
ff0517f4d0
commit
f0520c39d9
|
|
@ -90,7 +90,7 @@ Search for required documents using these patterns (sharded means a large docume
|
|||
1. `{planning_artifacts}/*ux*.md` (whole document)
|
||||
2. `{planning_artifacts}/*ux*/index.md` (sharded version)
|
||||
|
||||
Before proceeding, Ask the user if there are any other documents, or if what you have found is all there is [Yes/No]. Wait for user confirmation. Once confirmed, create the {outputFile} from the {epicsTemplate} and in the front matter list the files in the array of `inputDocuments: []`.
|
||||
Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {outputFile} from the {epicsTemplate} and in the front matter list the files in the array of `inputDocuments: []`.
|
||||
|
||||
### 3. Extract Functional Requirements (FRs)
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ startMessage: |
|
|||
|
||||
IMPORTANT Changes with Version Alpha.22 - PLEASE READ THIS if upgrading from earlier Alpha Versions:
|
||||
|
||||
1. The BMad Core default output folder has changed from docs to `_bmad-output`. `docs`
|
||||
1. The BMad Core default output folder has changed from `docs` to `_bmad-output`. `docs`
|
||||
is meant for long-term artifacts, which you can always decide to move content to.
|
||||
|
||||
2. If utilizing the BMad Method Module (BMM) please be aware of the following important recent changes:
|
||||
|
|
@ -37,7 +37,7 @@ endMessage: |
|
|||
|
||||
✨ BMAD IS READY TO USE!
|
||||
|
||||
ONE FINAL NOTE WITH VERSION Alpha.20: Phase 4 (Implementation) is still in the process of
|
||||
ONE FINAL NOTE WITH VERSION Alpha.22: Phase 4 (Implementation) is still in the process of
|
||||
being migrated to the improved workflow progressive disclosure system.
|
||||
Along with this, the full conversion to the new path locations for content being searched
|
||||
may possibly be incomplete. If you run a workflow that relies on finding input documents
|
||||
|
|
|
|||
Loading…
Reference in New Issue