Compare commits
4 Commits
44b84d9a13
...
e9eb5d31be
| Author | SHA1 | Date |
|---|---|---|
|
|
e9eb5d31be | |
|
|
9d00f69680 | |
|
|
2a30b47c91 | |
|
|
3dd37bc94d |
|
|
@ -15,12 +15,14 @@ main_config: '{project-root}/_bmad/bmm/config.yaml'
|
|||
### 1. Identify Environments
|
||||
|
||||
- Use your file listing/system capabilities to examine the `{project-root}/_bmad-output/` directory.
|
||||
- Identify all subdirectories within this path. Each subdirectory represents an available environment (ignore hidden directories starting with `.`).
|
||||
- Identify all subdirectories within this path. Each subdirectory represents an available environment, EXCEPT:
|
||||
- Ignore hidden directories starting with `.`
|
||||
- Ignore standard BMAD artifact directories: `planning-artifacts`, `implementation-artifacts`, `test-artifacts`, `knowledge`, `docs`, `assets`
|
||||
- The root `_bmad-output/` directory itself represents the `default (root)` unset environment.
|
||||
|
||||
### 2. Output Results
|
||||
|
||||
1. Display a formatted bulleted list of the existing environments you found.
|
||||
2. Clearly indicate the `default (root)` environment.
|
||||
1. Display a formatted numbered list of the existing environments you found.
|
||||
2. Clearly indicate the `default (root)` environment (usually [0]).
|
||||
3. Check if there is an active environment currently set. Read `{project-root}/{{bmadFolderName}}/.current_project`. If it exists, indicate which environment from the list is currently active (e.g. by adding `(ACTIVE)` next to the bullet point).
|
||||
4. Inform the user that they can switch to another environment or create a new one using the `/set-project <env_name>` command.
|
||||
|
|
|
|||
|
|
@ -24,14 +24,29 @@ Load and read full config from {main_config} and resolve variables and artifact
|
|||
2. **Wait for Input (If Missing)**: If the user did NOT provide a project name:
|
||||
- Use your file listing capabilities to examine the `{project-root}/_bmad-output/` directory.
|
||||
- Output: A formatted list of the existing environments (subdirectories) you found, explicitly noting the `default (root)` environment.
|
||||
- Ask the user: "Please select an existing environment from the list above, or type a new name to create one. Enter `CLEAR` to reset to root."
|
||||
*(Exclude hidden directories and standard BMAD artifact folders like `planning-artifacts`, `implementation-artifacts`, `test-artifacts`, `knowledge`, `docs`, `assets`)*
|
||||
- Present options in a numbered list format and ask the user to select by number or type a new project name:
|
||||
```
|
||||
Select a project environment:
|
||||
[0] default (root) - Current location for standard artifacts
|
||||
[1] project-name-1
|
||||
[2] project-name-2
|
||||
...
|
||||
|
||||
Enter a number to select, type a new project name, or enter 'CLEAR' to reset to root:
|
||||
```
|
||||
- **Wait for Input.**
|
||||
3. **Process Input**: Once a project name is established:
|
||||
- **Case: CLEAR**:
|
||||
- Delete file: `{project-root}/{{bmadFolderName}}/.current_project`
|
||||
- Output: "✅ Project context cleared. Artifacts will go to root `_bmad-output/`."
|
||||
- **HALT**
|
||||
- **Case: Path Provided**:
|
||||
- **Case: Numeric Selection**: If input is a number (0, 1, 2, etc.):
|
||||
- Map the number to the corresponding environment from your earlier listing
|
||||
- If number 0, treat as "CLEAR" case above
|
||||
- If valid number but out of range, show error and ask again
|
||||
- If valid selection, use that environment name as the path
|
||||
- **Case: Path Provided** (text input):
|
||||
- **1. Cleanup**: Remove leading/trailing slashes and any occurrences of `_bmad-output/`.
|
||||
- **2. Validate Existence**: Check if `{project-root}/_bmad-output/<sanitized_path>` exists on the file system.
|
||||
- **If it DOES NOT exist**:
|
||||
|
|
|
|||
|
|
@ -373,6 +373,7 @@ _This comprehensive research document serves as an authoritative reference on {{
|
|||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section
|
||||
- Append the complete document to the research file
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
|
||||
- Complete the domain research workflow
|
||||
|
|
@ -380,7 +381,7 @@ _This comprehensive research document serves as an authoritative reference on {{
|
|||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the complete comprehensive research document using the full structure above.
|
||||
When user selects 'C', append the complete comprehensive research document using the full structure above. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
|
|
|
|||
|
|
@ -389,13 +389,14 @@ _This comprehensive market research document serves as an authoritative market r
|
|||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
|
||||
- Complete the market research workflow
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 4.
|
||||
When user selects 'C', append the content directly to the research document using the structure from step 4. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
|
|
|
|||
|
|
@ -416,6 +416,7 @@ _This comprehensive technical research document serves as an authoritative techn
|
|||
|
||||
#### If 'C' (Complete Research):
|
||||
|
||||
- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section
|
||||
- Append the complete technical document to the research file
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
|
||||
- Complete the technical research workflow
|
||||
|
|
@ -423,7 +424,7 @@ _This comprehensive technical research document serves as an authoritative techn
|
|||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
When user selects 'C', append the complete comprehensive technical research document using the full structure above.
|
||||
When user selects 'C', append the complete comprehensive technical research document using the full structure above. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue