80 lines
2.6 KiB
Markdown
80 lines
2.6 KiB
Markdown
# Create Document from Template (YAML Driven)
|
|
|
|
## CRITICAL: Mandatory Elicitation Format
|
|
|
|
**When `elicit: true`, ALWAYS use this exact format:**
|
|
|
|
1. Present section content
|
|
2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
|
|
3. Present numbered options 1-9:
|
|
- **Option 1:** Always "Proceed to next section"
|
|
- **Options 2-9:** Select 8 methods from data/elicitation-methods
|
|
- End with: "Select 1-9 or just type your question/feedback:"
|
|
|
|
**NEVER ask yes/no questions or use any other format.**
|
|
|
|
## Processing Flow
|
|
|
|
1. **Parse YAML template** - Load template metadata and sections
|
|
2. **Set preferences** - Show current mode (Interactive), confirm output file
|
|
3. **Process each section:**
|
|
- Skip if condition unmet
|
|
- Check agent permissions (owner/editors) - note if section is restricted to specific agents
|
|
- Draft content using section instruction
|
|
- Present content + detailed rationale
|
|
- **IF elicit: true** → MANDATORY 1-9 options format
|
|
- Save to file if possible
|
|
4. **Continue until complete**
|
|
|
|
## Detailed Rationale Requirements
|
|
|
|
When presenting section content, ALWAYS include rationale that explains:
|
|
|
|
- Trade-offs and choices made (what was chosen over alternatives and why)
|
|
- Key assumptions made during drafting
|
|
- Interesting or questionable decisions that need user attention
|
|
- Areas that might need validation
|
|
|
|
## Elicitation Results Flow
|
|
|
|
After user selects elicitation method (2-9):
|
|
|
|
1. Execute method from data/elicitation-methods
|
|
2. Present results with insights
|
|
3. Offer options:
|
|
- **1. Apply changes and update section**
|
|
- **2. Return to elicitation menu**
|
|
- **3. Ask any questions or engage further with this elicitation**
|
|
|
|
## Agent Permissions
|
|
|
|
When processing sections with agent permission fields:
|
|
|
|
- **owner**: Note which agent role initially creates/populates the section
|
|
- **editors**: List agent roles allowed to modify the section
|
|
- **readonly**: Mark sections that cannot be modified after creation
|
|
|
|
**For sections with restricted access:**
|
|
|
|
- Include a note in the generated document indicating the responsible agent
|
|
- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
|
|
|
|
## YOLO Mode
|
|
|
|
User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
|
|
|
## CRITICAL REMINDERS
|
|
|
|
**❌ NEVER:**
|
|
|
|
- Ask yes/no questions for elicitation
|
|
- Use any format other than 1-9 numbered options
|
|
- Create new elicitation methods
|
|
|
|
**✅ ALWAYS:**
|
|
|
|
- Use exact 1-9 format when elicit: true
|
|
- Select options 2-9 from data/elicitation-methods only
|
|
- Provide detailed rationale explaining decisions
|
|
- End with "Select 1-9 or just type your question/feedback:"
|