refactor(research): clean up prompts and routing

This commit is contained in:
Alex Verkhovsky 2025-12-06 11:08:15 -07:00
parent e820626cf6
commit 63b1066a10
14 changed files with 19 additions and 19 deletions

View File

@ -77,7 +77,7 @@ For **{{research_topic}}**, I will research:
- Document scope confirmation in research file - Document scope confirmation in research file
- Update frontmatter: `stepsCompleted: [1]` - Update frontmatter: `stepsCompleted: [1]`
- Load: `./step-02-industry-analysis.md` - Load: `./step-02-domain-analysis.md`
## APPEND TO DOCUMENT: ## APPEND TO DOCUMENT:
@ -131,6 +131,6 @@ When user selects 'C', append scope confirmation:
## NEXT STEP: ## 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! Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!

View File

@ -200,6 +200,6 @@ Content is already written to document when generated in step 5. No additional a
## NEXT STEP: ## 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! Remember: Search the web to verify regulatory facts and provide practical implementation considerations!

View File

@ -123,7 +123,7 @@ Search the web: "{{research_topic}} significance importance"
### Research Significance ### 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]_ _Why this research matters now: [Strategic importance with current context]_
_Source: [URL]_ _Source: [URL]_

View File

@ -159,7 +159,7 @@ _Source: [URL]_
**Show analysis and present continue option:** **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:** **Key Customer Behavior Findings:**

View File

@ -154,7 +154,7 @@ Show the generated customer insights and present continue option:
- Append the final content to the research document - Append the final content to the research document
- Update frontmatter: `stepsCompleted: [1, 2]` - Update frontmatter: `stepsCompleted: [1, 2]`
- Load: `./step-03-competitive-analysis.md` - Load: `./step-05-competitive-analysis.md`
## APPEND TO DOCUMENT: ## APPEND TO DOCUMENT:
@ -194,6 +194,6 @@ When user selects 'C', append the content directly to the research document usin
## NEXT STEP: ## 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! Remember: Always emphasize current customer data and rigorous source verification!

View File

@ -170,7 +170,7 @@ _Source: [URL]_
**Show analysis and present continue option:** **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:** **Key Pain Points Findings:**

View File

@ -180,7 +180,7 @@ _Source: [URL]_
**Show analysis and present continue option:** **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:** **Key Decision Findings:**

View File

@ -77,7 +77,7 @@ For **{{research_topic}}**, I will research:
- Document scope confirmation in research file - Document scope confirmation in research file
- Update frontmatter: `stepsCompleted: [1]` - Update frontmatter: `stepsCompleted: [1]`
- Load: `./step-02-technology-stack.md` - Load: `./step-02-technical-overview.md`
## APPEND TO DOCUMENT: ## APPEND TO DOCUMENT:
@ -131,6 +131,6 @@ When user selects 'C', append scope confirmation:
## NEXT STEP: ## 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! Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope!

View File

@ -160,7 +160,7 @@ _Source: [URL]_
**Show analysis and present continue option:** **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:** **Key Technology Stack Findings:**

View File

@ -169,7 +169,7 @@ _Source: [URL]_
**Show analysis and present continue option:** **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:** **Key Integration Patterns Findings:**

View File

@ -155,7 +155,7 @@ Show the generated architectural patterns and present continue option:
- Append the final content to the research document - Append the final content to the research document
- Update frontmatter: `stepsCompleted: [1, 2, 3]` - Update frontmatter: `stepsCompleted: [1, 2, 3]`
- Load: `./step-04-implementation-research.md` - Load: `./step-05-implementation-research.md`
## APPEND TO DOCUMENT: ## APPEND TO DOCUMENT:
@ -196,6 +196,6 @@ When user selects 'C', append the content directly to the research document usin
## NEXT STEP: ## 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! Remember: Always emphasize current architectural data and rigorous source verification!

View File

@ -127,7 +127,7 @@ Search the web: "{{research_topic}} technical significance importance"
### Technical Research Significance ### 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]_ _Technical Importance: [Strategic technical significance with current context]_
_Business Impact: [Business implications of technical research]_ _Business Impact: [Business implications of technical research]_
_Source: [URL]_ _Source: [URL]_