formatter updates
This commit is contained in:
@@ -351,25 +351,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
||||
|
||||
```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
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
|
||||
- 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
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
agent:
|
||||
name: Sarah
|
||||
id: po
|
||||
title: Product Owner
|
||||
icon: 📝
|
||||
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
|
||||
customization:
|
||||
|
||||
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
|
||||
customization: null
|
||||
persona:
|
||||
role: Technical Product Owner & Process Steward
|
||||
style: Meticulous, analytical, detail-oriented, systematic, collaborative
|
||||
identity: Product Owner who validates artifacts cohesion and coaches significant changes
|
||||
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
|
||||
|
||||
core_principles:
|
||||
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
|
||||
- Clarity & Actionability for Development - Make requirements unambiguous and testable
|
||||
@@ -381,21 +378,18 @@ persona:
|
||||
- User Collaboration for Validation - Seek input at critical checkpoints
|
||||
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
|
||||
- Documentation Ecosystem Integrity - Maintain consistency across all documents
|
||||
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
|
||||
- "*create-doc {template}" - Create doc (no template = show available templates)
|
||||
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
|
||||
- "*shard-doc {document}" - Break down document into actionable parts
|
||||
- "*correct-course" - Analyze and suggest project course corrections
|
||||
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
|
||||
- "*create-story" - Create user story from requirements (task brownfield-create-story)
|
||||
- "*exit" - Say Goodbye, You are no longer this Agent
|
||||
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
|
||||
- '*create-doc {template}" - Create doc (no template = show available templates)'
|
||||
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
|
||||
- '*shard-doc {document}" - Break down document into actionable parts'
|
||||
- '*correct-course" - Analyze and suggest project course corrections'
|
||||
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
|
||||
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
|
||||
- '*exit" - Say Goodbye, You are no longer this Agent'
|
||||
dependencies:
|
||||
tasks:
|
||||
- execute-checklist
|
||||
@@ -1757,6 +1751,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
|
||||
|
||||
1. **Establish Context**
|
||||
|
||||
- Understand the problem space or opportunity area
|
||||
- Identify any constraints or parameters
|
||||
- Determine session goals (divergent exploration vs. focused ideation)
|
||||
@@ -1773,6 +1768,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
1. **"What If" Scenarios**
|
||||
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
|
||||
|
||||
- What if we had unlimited resources?
|
||||
- What if this problem didn't exist?
|
||||
- What if we approached this from a child's perspective?
|
||||
@@ -1780,6 +1776,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
2. **Analogical Thinking**
|
||||
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
|
||||
|
||||
- "How might this work like [X] but for [Y]?"
|
||||
- Nature-inspired solutions (biomimicry)
|
||||
- Cross-industry pattern matching
|
||||
@@ -1787,6 +1784,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
3. **Reversal/Inversion**
|
||||
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
|
||||
|
||||
- What if we did the exact opposite?
|
||||
- How could we make this problem worse? (then reverse)
|
||||
- Start from the end goal and work backward
|
||||
@@ -1803,6 +1801,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
1. **SCAMPER Method**
|
||||
[[LLM: Guide through each SCAMPER prompt systematically.]]
|
||||
|
||||
- **S** = Substitute: What can be substituted?
|
||||
- **C** = Combine: What can be combined or integrated?
|
||||
- **A** = Adapt: What can be adapted from elsewhere?
|
||||
@@ -1813,6 +1812,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
2. **Six Thinking Hats**
|
||||
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
|
||||
|
||||
- White Hat: Facts and information
|
||||
- Red Hat: Emotions and intuition
|
||||
- Black Hat: Caution and critical thinking
|
||||
@@ -1839,6 +1839,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
1. **"Yes, And..." Building**
|
||||
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
|
||||
|
||||
- Accept the premise of each idea
|
||||
- Add to it with "Yes, and..."
|
||||
- Build chains of connected ideas
|
||||
@@ -1846,40 +1847,43 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
2. **Brainwriting/Round Robin**
|
||||
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
|
||||
|
||||
- Generate ideas from stakeholder perspectives
|
||||
- Build on previous ideas in rounds
|
||||
- Combine unrelated ideas
|
||||
- Cross-pollinate concepts
|
||||
|
||||
3. **Random Stimulation**
|
||||
[[LLM: Use random words, images, or concepts as creative triggers.]]
|
||||
- Random word association
|
||||
- Picture/metaphor inspiration
|
||||
- Forced connections between unrelated items
|
||||
- Constraint-based creativity
|
||||
[[LLM: Use random words, images, or concepts as creative triggers.]]
|
||||
- Random word association
|
||||
- Picture/metaphor inspiration
|
||||
- Forced connections between unrelated items
|
||||
- Constraint-based creativity
|
||||
|
||||
#### Deep Exploration Techniques
|
||||
|
||||
1. **Five Whys**
|
||||
[[LLM: Dig deeper into root causes and underlying motivations.]]
|
||||
- Why does this problem exist? → Answer → Why? (repeat 5 times)
|
||||
- Uncover hidden assumptions
|
||||
- Find root causes, not symptoms
|
||||
- Identify intervention points
|
||||
[[LLM: Dig deeper into root causes and underlying motivations.]]
|
||||
|
||||
- Why does this problem exist? → Answer → Why? (repeat 5 times)
|
||||
- Uncover hidden assumptions
|
||||
- Find root causes, not symptoms
|
||||
- Identify intervention points
|
||||
|
||||
2. **Morphological Analysis**
|
||||
[[LLM: Break down into parameters and systematically explore combinations.]]
|
||||
- List key parameters/dimensions
|
||||
- Identify possible values for each
|
||||
- Create combination matrix
|
||||
- Explore unusual combinations
|
||||
[[LLM: Break down into parameters and systematically explore combinations.]]
|
||||
|
||||
- List key parameters/dimensions
|
||||
- Identify possible values for each
|
||||
- Create combination matrix
|
||||
- Explore unusual combinations
|
||||
|
||||
3. **Provocation Technique (PO)**
|
||||
[[LLM: Make deliberately provocative statements to jar thinking.]]
|
||||
- PO: Cars have square wheels
|
||||
- PO: Customers pay us to take products
|
||||
- PO: The problem solves itself
|
||||
- Extract useful ideas from provocations
|
||||
[[LLM: Make deliberately provocative statements to jar thinking.]]
|
||||
- PO: Cars have square wheels
|
||||
- PO: Customers pay us to take products
|
||||
- PO: The problem solves itself
|
||||
- Extract useful ideas from provocations
|
||||
|
||||
### 3. Technique Selection Guide
|
||||
|
||||
@@ -1920,16 +1924,19 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
|
||||
|
||||
1. **Warm-up Phase** (5-10 min)
|
||||
|
||||
- Start with accessible techniques
|
||||
- Build creative confidence
|
||||
- Establish "no judgment" atmosphere
|
||||
|
||||
2. **Divergent Phase** (20-30 min)
|
||||
|
||||
- Use expansion techniques
|
||||
- Generate quantity over quality
|
||||
- Encourage wild ideas
|
||||
|
||||
3. **Convergent Phase** (15-20 min)
|
||||
|
||||
- Group and categorize ideas
|
||||
- Identify patterns and themes
|
||||
- Select promising directions
|
||||
@@ -2165,53 +2172,65 @@ Present these numbered options to the user:
|
||||
|
||||
```markdown
|
||||
## Research Objective
|
||||
|
||||
[Clear statement of what this research aims to achieve]
|
||||
|
||||
## Background Context
|
||||
|
||||
[Relevant information from project brief, brainstorming, or other inputs]
|
||||
|
||||
## Research Questions
|
||||
|
||||
### Primary Questions (Must Answer)
|
||||
|
||||
1. [Specific, actionable question]
|
||||
2. [Specific, actionable question]
|
||||
...
|
||||
...
|
||||
|
||||
### Secondary Questions (Nice to Have)
|
||||
|
||||
1. [Supporting question]
|
||||
2. [Supporting question]
|
||||
...
|
||||
...
|
||||
|
||||
## Research Methodology
|
||||
|
||||
### Information Sources
|
||||
|
||||
- [Specific source types and priorities]
|
||||
|
||||
### Analysis Frameworks
|
||||
|
||||
- [Specific frameworks to apply]
|
||||
|
||||
### Data Requirements
|
||||
|
||||
- [Quality, recency, credibility needs]
|
||||
|
||||
## Expected Deliverables
|
||||
|
||||
### Executive Summary
|
||||
|
||||
- Key findings and insights
|
||||
- Critical implications
|
||||
- Recommended actions
|
||||
|
||||
### Detailed Analysis
|
||||
|
||||
[Specific sections needed based on research type]
|
||||
|
||||
### Supporting Materials
|
||||
|
||||
- Data tables
|
||||
- Comparison matrices
|
||||
- Source documentation
|
||||
|
||||
## Success Criteria
|
||||
|
||||
[How to evaluate if research achieved its objectives]
|
||||
|
||||
## Timeline and Priority
|
||||
|
||||
[If applicable, any time constraints or phasing]
|
||||
```
|
||||
|
||||
@@ -7670,28 +7689,33 @@ Ask the user if they want to work through the checklist:
|
||||
Now that you've completed the checklist, generate a comprehensive validation report that includes:
|
||||
|
||||
1. Executive Summary
|
||||
|
||||
- Overall architecture readiness (High/Medium/Low)
|
||||
- Critical risks identified
|
||||
- Key strengths of the architecture
|
||||
- Project type (Full-stack/Frontend/Backend) and sections evaluated
|
||||
|
||||
2. Section Analysis
|
||||
|
||||
- Pass rate for each major section (percentage of items passed)
|
||||
- Most concerning failures or gaps
|
||||
- Sections requiring immediate attention
|
||||
- Note any sections skipped due to project type
|
||||
|
||||
3. Risk Assessment
|
||||
|
||||
- Top 5 risks by severity
|
||||
- Mitigation recommendations for each
|
||||
- Timeline impact of addressing issues
|
||||
|
||||
4. Recommendations
|
||||
|
||||
- Must-fix items before development
|
||||
- Should-fix items for better quality
|
||||
- Nice-to-have improvements
|
||||
|
||||
5. AI Implementation Readiness
|
||||
|
||||
- Specific concerns for AI agent implementation
|
||||
- Areas needing additional clarification
|
||||
- Complexity hotspots to address
|
||||
|
||||
Reference in New Issue
Block a user