refactor(research): clean up prompts and routing
This commit is contained in:
Alex Verkhovsky
parent
e820626cf6
commit
63b1066a10
|
|
@ -77,7 +77,7 @@ For **{{research_topic}}**, I will research:
|
|||
|
||||
- Document scope confirmation in research file
|
||||
- Update frontmatter: `stepsCompleted: [1]`
|
||||
- Load: `./step-02-industry-analysis.md`
|
||||
- Load: `./step-02-domain-analysis.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
|
|
@ -131,6 +131,6 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-02-industry-analysis.md` to begin industry analysis.
|
||||
After user selects 'C', load `./step-02-domain-analysis.md` to begin industry analysis.
|
||||
|
||||
Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!
|
||||
|
|
|
|||
|
|
@ -200,6 +200,6 @@ Content is already written to document when generated in step 5. No additional a
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-04-technical-trends.md` to analyze technical trends and innovations in the domain.
|
||||
After user selects 'C' and content is saved to document, load `./step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
|
||||
|
||||
Remember: Search the web to verify regulatory facts and provide practical implementation considerations!
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@ Search the web: "{{research_topic}} significance importance"
|
|||
|
||||
### Research Significance
|
||||
|
||||
[Compelling narrative about why {{research_topic}} research is critical in current]
|
||||
[Compelling narrative about why {{research_topic}} research is critical right now]
|
||||
_Why this research matters now: [Strategic importance with current context]_
|
||||
_Source: [URL]_
|
||||
|
||||
|
|
|
|||
|
|
@ -159,7 +159,7 @@ _Source: [URL]_
|
|||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer behavior analysis** for customer patterns for {{research_topic}}.
|
||||
"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
|
||||
|
||||
**Key Customer Behavior Findings:**
|
||||
|
||||
|
|
|
|||
|
|
@ -154,7 +154,7 @@ Show the generated customer insights and present continue option:
|
|||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2]`
|
||||
- Load: `./step-03-competitive-analysis.md`
|
||||
- Load: `./step-05-competitive-analysis.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
|
|
@ -194,6 +194,6 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-03-competitive-analysis.md` to focus on competitive landscape analysis.
|
||||
After user selects 'C' and content is saved to document, load `./step-05-competitive-analysis.md` to focus on competitive landscape analysis.
|
||||
|
||||
Remember: Always emphasize current customer data and rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -170,7 +170,7 @@ _Source: [URL]_
|
|||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer pain points analysis** for customer challenges for {{research_topic}}.
|
||||
"I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
|
||||
|
||||
**Key Pain Points Findings:**
|
||||
|
||||
|
|
|
|||
|
|
@ -180,7 +180,7 @@ _Source: [URL]_
|
|||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer decision processes analysis** for customer decision-making for {{research_topic}}.
|
||||
"I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
|
||||
|
||||
**Key Decision Findings:**
|
||||
|
||||
|
|
|
|||
|
|
@ -173,4 +173,4 @@ Market research workflow complete. User may:
|
|||
- Conduct additional competitive research on specific companies
|
||||
- Combine market research with other research types for comprehensive insights
|
||||
|
||||
Congratulations on completing comprehensive market research ! 🎉
|
||||
Congratulations on completing comprehensive market research! 🎉
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ For **{{research_topic}}**, I will research:
|
|||
|
||||
- Document scope confirmation in research file
|
||||
- Update frontmatter: `stepsCompleted: [1]`
|
||||
- Load: `./step-02-technology-stack.md`
|
||||
- Load: `./step-02-technical-overview.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
|
|
@ -131,6 +131,6 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-02-technology-stack.md` to begin technology stack analysis.
|
||||
After user selects 'C', load `./step-02-technical-overview.md` to begin technology stack analysis.
|
||||
|
||||
Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope!
|
||||
|
|
|
|||
|
|
@ -160,7 +160,7 @@ _Source: [URL]_
|
|||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **technology stack analysis** for the technology landscape for {{research_topic}}.
|
||||
"I've completed **technology stack analysis** of the technology landscape for {{research_topic}}.
|
||||
|
||||
**Key Technology Stack Findings:**
|
||||
|
||||
|
|
|
|||
|
|
@ -169,7 +169,7 @@ _Source: [URL]_
|
|||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **integration patterns analysis** for system integration approaches for {{research_topic}}.
|
||||
"I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}.
|
||||
|
||||
**Key Integration Patterns Findings:**
|
||||
|
||||
|
|
|
|||
|
|
@ -155,7 +155,7 @@ Show the generated architectural patterns and present continue option:
|
|||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Load: `./step-04-implementation-research.md`
|
||||
- Load: `./step-05-implementation-research.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
|
|
@ -196,6 +196,6 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-04-implementation-research.md` to focus on implementation approaches and technology adoption.
|
||||
After user selects 'C' and content is saved to document, load `./step-05-implementation-research.md` to focus on implementation approaches and technology adoption.
|
||||
|
||||
Remember: Always emphasize current architectural data and rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ Conduct comprehensive implementation research with emphasis on practical impleme
|
|||
### 1. Begin Implementation Research
|
||||
|
||||
Start with implementation research approach:
|
||||
"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis .
|
||||
"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis.
|
||||
|
||||
**Implementation Research Focus:**
|
||||
|
||||
|
|
@ -235,4 +235,4 @@ Technical research workflow complete. User may:
|
|||
- Combine technical research with other research types for comprehensive insights
|
||||
- Move forward with implementation based on technical insights
|
||||
|
||||
Congratulations on completing comprehensive technical research ! 🎉
|
||||
Congratulations on completing comprehensive technical research! 🎉
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@ Search the web: "{{research_topic}} technical significance importance"
|
|||
|
||||
### Technical Research Significance
|
||||
|
||||
[Compelling technical narrative about why {{research_topic}} research is critical in current]
|
||||
[Compelling technical narrative about why {{research_topic}} research is critical right now]
|
||||
_Technical Importance: [Strategic technical significance with current context]_
|
||||
_Business Impact: [Business implications of technical research]_
|
||||
_Source: [URL]_
|
||||
|
|
|
|||
Loading…
Reference in New Issue