Clean up markdown nesting. (#252)

Co-authored-by: TC <>
This commit is contained in:
titocr
2025-06-19 14:54:47 -07:00
committed by GitHub
parent 651c0d2a9e
commit 3267144248
18 changed files with 86 additions and 108 deletions

View File

@@ -63,7 +63,7 @@ Created during agent setup:
- Templates:
- [ ] template-name-1.md
- [ ] template-name-2.md
```text
```
### 4. Create Agent File
@@ -121,7 +121,7 @@ Present to the user:
1. Review and customize the created tasks/templates
2. Run npm run build:agents
3. Test the agent thoroughly
```text
```
## Template Reference
@@ -150,7 +150,7 @@ persona:
- Data integrity and accuracy above all
- Clear communication of complex findings
- Actionable insights over raw numbers
```text
```
## Creating Missing Dependencies

View File

@@ -83,7 +83,7 @@ workflows:
- {{workflow-name}} # {{workflow-description}}
<</REPEAT>>
^^/CONDITION: domain-workflows^^
```text
```
@{example-1: Standard fullstack team}
@@ -127,7 +127,7 @@ workflows:
- healthcare-patient-portal
- healthcare-compliance-audit
- clinical-trial-management
```text
```
@{example-3: Minimal IDE team}

View File

@@ -10,7 +10,7 @@
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
````yml
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
@@ -86,7 +86,7 @@ dependencies:
- template-format # Required if using templates
- [UTIL_1] # Other utilities as needed
[[LLM: Include workflow-management if agent participates in workflows]]
```text
```
@{example: Construction Contractor Agent}
@@ -140,4 +140,4 @@ dependencies:
- 'materials-guide.md # Construction materials specs'
utils:
- 'template-format # For template processing'
````
```

View File

@@ -47,7 +47,7 @@ Available workflows for [Team Name]:
[... etc. ...]
Use /workflow-start {number or id} to begin a workflow.
```text
```
### /workflow-start {workflow-id}
@@ -73,7 +73,7 @@ In Progress:
- Create PRD (John) - awaiting input
Next: Technical Architecture
```text
```
### /workflow-resume
@@ -89,7 +89,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
- UX Strategy with Sally (ux-expert)
Would you like me to load Sally to continue?
```text
```
### /workflow-next
@@ -135,7 +135,7 @@ workflow_state:
status: in-progress
created_by: pm
started: 2024-01-15T11:00:00.000Z
```text
```
### 4. Workflow Interruption Handling
@@ -159,7 +159,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
- Load Sarah (Product Owner) to validate all artifacts
Would you like to continue with this workflow?
```text
```
## Workflow Context Passing
@@ -185,7 +185,7 @@ Sally: I see we're in the Product Planning stage of the greenfield-fullstack wor
Let's create the UX strategy and UI specifications. First, let me review
the PRD to understand the features we're designing for...
```text
```
## Multi-Path Workflows