chore: make websearch prompts year-agnostic

This commit is contained in:
mq-bot 2025-12-03 10:49:35 +00:00
parent e4e1e7d6dc
commit cfd72f3840
4 changed files with 11 additions and 11 deletions

View File

@ -176,7 +176,7 @@ I see {{epic_count}} epics with {{story_count}} total stories.
<check if="user_accepts_starter">
<action>Get current starter command and options:
<WebSearch>{{starter_name}} CLI command options flags latest 2025</WebSearch>
<WebSearch>{{starter_name}} CLI command options flags latest</WebSearch>
</action>
<action>Document the initialization command:
@ -327,7 +327,7 @@ Let's work through the remaining {{remaining_count}} decisions."
<check if="decision_involves_specific_technology">
<action>Verify current stable version:
<WebSearch>{{technology}} latest stable version 2025</WebSearch>
<WebSearch>{{technology}} latest stable version</WebSearch>
<WebSearch>{{technology}} current LTS version</WebSearch>
</action>

View File

@ -123,7 +123,7 @@ test('should validate PDF report', async () => {
const { content } = await readPDF({ filePath: downloadPath });
// content.text is extracted text from all pages
expect(content.text).toContain('Financial Report Q4 2025');
expect(content.text).toContain('Financial Report Q4 2024');
expect(content.text).toContain('Total Revenue:');
// Validate page count

View File

@ -121,9 +121,9 @@ If UX specification was loaded, consider UX requirements when selecting starter:
Use WebSearch to find current, maintained starter templates:
```
WebSearch: {{primary_technology}} starter template CLI create command latest 2025
WebSearch: {{primary_technology}} boilerplate generator latest options 2025
WebSearch: {{primary_technology}} production-ready starter best practices 2025
WebSearch: {{primary_technology}} starter template CLI create command latest
WebSearch: {{primary_technology}} boilerplate generator latest options
WebSearch: {{primary_technology}} production-ready starter best practices
```
### 4. Investigate Top Starter Options
@ -134,7 +134,7 @@ For each promising starter found, investigate details:
WebSearch: {{starter_name}} default setup technologies included latest
WebSearch: {{starter_name}} project structure file organization
WebSearch: {{starter_name}} production deployment capabilities
WebSearch: {{starter_name}} recent updates maintenance status 2025
WebSearch: {{starter_name}} recent updates maintenance status
```
### 5. Analyze What Each Starter Provides
@ -200,7 +200,7 @@ This is a great starting point that follows best practices and saves us from mak
If user shows interest in a starter, get the exact current commands:
```
WebSearch: {{starter_name}} CLI command options flags latest 2025
WebSearch: {{starter_name}} CLI command options flags latest
WebSearch: {{starter_name}} create new project command examples
```

View File

@ -163,9 +163,9 @@ What feels right to you?"
If decision involves specific technology:
```
WebSearch: {{technology}} latest stable version 2025
WebSearch: {{technology}} latest stable version
WebSearch: {{technology}} current LTS version
WebSearch: {{technology}} production readiness 2025
WebSearch: {{technology}} production readiness
```
**Get User Input:**