Update hardcoded year references from 2025 to 2026 (#91)

- Update "current year is 2025" to 2026 in 4 research agents
- Update year ranges to 2024-2026 for content searches in deepen-plan
  and create-agent-skills workflows
- Change "currency" to "recency" for clarity in domain expertise skill
This commit is contained in:
Trevin Chow
2026-01-20 16:33:37 -08:00
committed by GitHub
parent 87138ea974
commit 215445b5d0
8 changed files with 12 additions and 12 deletions

View File

@@ -94,7 +94,7 @@ Each workflow = one complete task type that users actually do.
Run multiple web searches to ensure coverage:
**Search 1: Current ecosystem**
- "best {domain} libraries 2024 2025"
- "best {domain} libraries 2024 2025 2026"
- "popular {domain} frameworks comparison"
- "{domain} tech stack recommendations"
@@ -466,7 +466,7 @@ Ask: "Could a user build a professional {domain thing} from scratch through ship
- [ ] Platform-specific considerations included?
- [ ] "When to use X vs Y" guidance provided?
- [ ] Common pitfalls documented?
- [ ] Current as of 2024-2025?
- [ ] Current as of 2024-2026?
- [ ] Workflows actually execute tasks (not just reference knowledge)?
- [ ] Each workflow specifies which references to read?
@@ -564,7 +564,7 @@ Review entire skill:
Domain expertise skill is complete when:
- [ ] Comprehensive research completed (5+ web searches)
- [ ] All sources verified for currency (2024-2025)
- [ ] All sources verified for recency (2024-2026)
- [ ] Knowledge organized by domain areas (not arbitrary)
- [ ] Essential principles in SKILL.md (always loaded)
- [ ] Intake routes to appropriate workflows

View File

@@ -52,7 +52,7 @@ Options:
If research requested:
- Use Context7 MCP to fetch current library documentation
- Or use WebSearch for recent API documentation
- Focus on 2024-2025 sources
- Focus on 2024-2026 sources
- Store findings for use in content generation
## Step 3: Decide Structure

View File

@@ -108,7 +108,7 @@ Check:
### For Integration Skills
WebSearch for recent changes:
```
"[service name] API changes 2025"
"[service name] API changes 2026"
"[service name] breaking changes"
"[service name] deprecated endpoints"
```
@@ -188,9 +188,9 @@ which {tool} && {tool} --version
```
**WebSearch patterns:**
- Breaking changes: "{service} breaking changes 2025"
- Breaking changes: "{service} breaking changes 2026"
- Deprecations: "{service} deprecated API"
- Current best practices: "{framework} best practices 2025"
- Current best practices: "{framework} best practices 2026"
</verification_shortcuts>
<success_criteria>