Update tech stack documentation based on dependency changes and technical evolution
User Request: $ARGUMENTS
pwdstat -f "%Sm" .agents/rules/2-tech-stack.mdc 2>/dev/null || echo "No existing document"git diff HEAD~10 HEAD -- package.json 2>/dev/null | grep -E "^[+-]" | head -20 || echo "No recent changes"Update the existing Tech Stack Documentation to reflect current technical state, dependency changes, new tools adoption, and infrastructure evolution. Maintain technical accuracy while documenting all changes.
Think deeply about technical evolution in the codebase.
Analyze for:
Extended thinking helps identify cascading dependency updates, understand version compatibility issues, and recognize architectural implications of technical changes.
# Compare current vs documented dependencies
# Check for version mismatches
# Identify new configuration files
# Detect new tool configurations
Ask targeted questions about:
Update incrementally:
1. Which major dependencies have been updated?
Review your recent dependency changes:
a) Framework upgrades (Next.js, React, etc.) with breaking changes
b) Tool updates (TypeScript, ESLint, etc.) requiring config changes
c) New dependencies added for features or development
d) Removed packages that are no longer needed
e) All of the above - Major technical overhaul
2. Have you changed your package manager or Node version?
a) Same setup - No changes to tooling
b) Node upgrade - Updated Node.js version
c) Package manager switch - Changed from npm/yarn/pnpm
d) Monorepo adoption - Moved to workspace setup
3. Have your deployment or hosting arrangements changed?
Current deployment is documented as: [show from existing doc]
a) Same platform - Just configuration updates
b) Platform migration - Moved to different provider
c) Architecture change - Serverless, containers, etc.
d) Multi-region - Expanded geographic deployment
4. Database or storage changes?
a) Version upgrade - Same DB, newer version
b) Migration - Switched database systems
c) New caching - Added Redis, Memcached, etc.
d) Storage addition - New file storage, CDN
e) No changes - Same setup as before
5. New development tools or practices?
Select all that apply:
6. External service integrations?
Have you added or changed:
a) Payment processing - New or updated provider
b) Authentication - Different auth service
c) Email/SMS - Communication service changes
d) Monitoring - New error tracking or analytics
e) APIs - Additional third-party integrations
f) None - Same external services
7. Security tool adoption?
// ❌ Outdated
"next": "^13.0.0"
// ✅ Current and precise
"next": "14.2.5"
When adding major new tools:
### [New Tool Category]
**Tool:** [Name] [Version]
**Purpose:** [Why it was adopted]
**Configuration:** [Key settings]
**Integration:** [How it connects with other tools]
package.json changes
# Compare all dependencies
# Note version changes
# Identify new packages
Configuration files
Development scripts
Infrastructure files
# Check current dependencies vs documented
diff <(jq -r '.dependencies | keys[]' package.json | sort) \
<(grep -E '^\*\*.*:' .agents/rules/2-tech-stack.mdc | cut -d: -f1 | sed 's/\*//g' | sort)
# Review recent dependency commits
git log --oneline --grep="dep" --since="30 days ago"
# Check for new config files
find . -name "*.config.*" -newer .agents/rules/2-tech-stack.mdc 2>/dev/null
Think deeply about: "What technical decisions drove these changes? How do version updates affect the overall architecture? What new capabilities do these tools enable?"
Follow incremental approach:
<!-- Version update example -->
**Before:** React 18.2.0
**After:** React 18.3.1 - Includes new compiler optimizations
<!-- New tool example -->
### Code Quality Tools
**New Addition:**
- **Biome:** 1.8.3 - Replaced ESLint and Prettier
- Faster performance (10x)
- Single configuration file
- Built-in formatting
# Optional backup
cp .agents/rules/2-tech-stack.mdc .agents/rules/2-tech-stack.backup.md
# Save updated document
# Overwrite .agents/rules/2-tech-stack.mdc
.mdc).agents/rules/2-tech-stack.mdc (overwrites)