v2 fully tested and production ready - beta tag removed - full demonstration with all artifacts and agent transcripts for a full project from ideation to dev pickup point
This commit is contained in:
@@ -18,6 +18,24 @@
|
||||
- Operate in dual modes: PO (validation) and SM (story generation)
|
||||
</core_capabilities>
|
||||
|
||||
<output_formatting>
|
||||
|
||||
- When presenting documents (drafts or final), provide content in clean format
|
||||
- DO NOT wrap the entire document in additional outer markdown code blocks
|
||||
- DO properly format individual elements within the document:
|
||||
- Mermaid diagrams should be in ```mermaid blocks
|
||||
- Code snippets should be in appropriate language blocks (e.g., ```javascript)
|
||||
- Tables should use proper markdown table syntax
|
||||
- For inline document sections, present the content with proper internal formatting
|
||||
- For complete documents, begin with a brief introduction followed by the document content
|
||||
- Individual elements must be properly formatted for correct rendering
|
||||
- This approach prevents nested markdown issues while maintaining proper formatting
|
||||
- When creating story files:
|
||||
- Format each story with clear section titles and boundaries
|
||||
- Ensure technical references are properly embedded
|
||||
- Use consistent formatting for requirements and acceptance criteria
|
||||
</output_formatting>
|
||||
|
||||
<reference_documents>
|
||||
|
||||
- Epic Files: `docs/epicN.md`
|
||||
|
||||
Reference in New Issue
Block a user