workflows added to sub items in plan project phase. updated single action checks to be ifs on the action.

This commit is contained in:
Brian Madison
2025-10-05 11:32:45 -05:00
parent aefe72fd60
commit 33d893bef2
26 changed files with 935 additions and 404 deletions

View File

@@ -186,8 +186,9 @@ Write 1-3 bullet points about project success:
```xml
<step n="2" goal="Validate input">
<action>Load validation criteria</action>
<check>If validation fails:</check>
<goto step="1">Return to previous step</goto>
<check if="validation fails">
<goto step="1">Return to previous step</goto>
</check>
<template-output>validated_data</template-output>
</step>
```
@@ -257,26 +258,47 @@ _Generated on {{date}}_
</step>
```
### Branching and Goto
### Conditional Execution
**Single Action (use `action if=""`):**
```xml
<step n="6" goal="Load context">
<action if="file exists">Load existing document</action>
<action if="new project">Initialize from template</action>
</step>
```
**Multiple Actions (use `<check if="">...</check>`):**
```xml
<step n="7" goal="Validate">
<action>Check requirements</action>
<check>If incomplete:</check>
<goto step="2">Return to gathering</goto>
<check>If complete:</check>
<continue>Proceed</continue>
<check if="incomplete">
<action>Log validation errors</action>
<goto step="2">Return to gathering</goto>
</check>
<check if="complete">
<action>Mark as validated</action>
<continue>Proceed</continue>
</check>
</step>
```
**When to use which:**
- **`<action if="">`** - Single conditional action (cleaner, more concise)
- **`<check if="">...</check>`** - Multiple items under same condition (explicit scope)
### Loops
```xml
<step n="8" goal="Refine">
<loop max="5">
<action>Generate solution</action>
<check>If criteria met:</check>
<break>Exit loop</break>
<check if="criteria met">
<break>Exit loop</break>
</check>
</loop>
</step>
```
@@ -286,7 +308,8 @@ _Generated on {{date}}_
**Execution:**
- `<action>` - Required action
- `<check>` - Conditional check
- `<action if="condition">` - Single conditional action (inline)
- `<check if="condition">...</check>` - Conditional block for multiple items (requires closing tag)
- `<ask>` - User prompt
- `<goto>` - Jump to step
- `<invoke-workflow>` - Call another workflow
@@ -370,8 +393,9 @@ Check requirements against goals.
<step n="3" goal="Verify">
<action>Run tests</action>
<check>If tests fail:</check>
<goto step="2">Fix issues</goto>
<check if="tests fail">
<goto step="2">Fix issues</goto>
</check>
</step>
</workflow>
```
@@ -414,6 +438,40 @@ Check requirements against goals.
3. **Set limits** - "3-5 items maximum"
4. **Explain why** - Context helps AI make better decisions
### Conditional Execution Best Practices
**✅ DO:**
- Use `<action if="">` for single conditional actions
- Use `<check if="">...</check>` for blocks with multiple items
- Always close `<check>` tags explicitly
- Keep conditions simple and readable
**❌ DON'T:**
- Wrap single actions in `<check>` blocks (unnecessarily verbose)
- Forget to close `<check>` tags
- Nest too many levels (makes logic hard to follow)
**Examples:**
```xml
<!-- ✅ Good: Single action -->
<action if="file exists">Load configuration</action>
<!-- ❌ Avoid: Unnecessary wrapper for single action -->
<check if="file exists">
<action>Load configuration</action>
</check>
<!-- ✅ Good: Multiple actions in block -->
<check if="validation fails">
<action>Log error details</action>
<action>Notify user</action>
<goto step="1">Retry input</goto>
</check>
```
### Common Pitfalls
- **Missing critical headers** - Always include workflow engine references
@@ -421,6 +479,8 @@ Check requirements against goals.
- **Too many steps** - Combine related actions
- **No checkpoints** - Add `<template-output>` tags
- **Vague instructions** - Be explicit about expectations
- **Unclosed check tags** - Always close `<check if="">...</check>` blocks
- **Wrong conditional pattern** - Use `<action if="">` for single items, `<check if="">` for blocks
## Web Bundles