Files
agents/tools/context-save.md
Seth Hobson 3802bca865 Refine plugin marketplace for launch readiness
Plugin Scope Improvements:
- Remove language-specialists plugin (not task-focused)
- Split specialized-domains into 5 focused plugins:
  * blockchain-web3 - Smart contract development only
  * quantitative-trading - Financial modeling and trading only
  * payment-processing - Payment gateway integration only
  * game-development - Unity and Minecraft only
  * accessibility-compliance - WCAG auditing only
- Split business-operations into 3 focused plugins:
  * business-analytics - Metrics and reporting only
  * hr-legal-compliance - HR and legal docs only
  * customer-sales-automation - Support and sales workflows only
- Fix infrastructure-devops scope:
  * Remove database concerns (db-migrate, database-admin)
  * Remove observability concerns (observability-engineer)
  * Move slo-implement to incident-response
  * Focus purely on container orchestration (K8s, Docker, Terraform)
- Fix customer-sales-automation scope:
  * Remove content-marketer (unrelated to customer/sales workflows)

Marketplace Statistics:
- Total plugins: 27 (was 22)
- Tool coverage: 100% (42/42 tools referenced)
- Fat plugins removed: 3 (language-specialists, specialized-domains, business-operations)
- All plugins now have clear, focused tasks

Model Migration:
- Migrate all 42 tools from claude-sonnet-4-0/opus-4-1 to model: sonnet
- Migrate all 15 workflows from claude-opus-4-1 to model: sonnet
- Use short model syntax consistent with agent files

Documentation Updates:
- Update README.md with refined plugin structure
- Update plugin descriptions to be task-focused
- Remove anthropomorphic and marketing language
- Improve category organization (now 16 distinct categories)

Ready for October 9, 2025 @ 9am PST launch
2025-10-08 20:54:29 -04:00

70 lines
1.9 KiB
Markdown

---
model: sonnet
---
Save current project context for future agent coordination:
[Extended thinking: This tool uses the context-manager agent to capture and preserve project state, decisions, and patterns. This enables better continuity across sessions and improved agent coordination.]
## Context Capture Process
Use Task tool with subagent_type="context-manager" to save comprehensive project context.
Prompt: "Save comprehensive project context for: $ARGUMENTS. Capture:
1. **Project Overview**
- Project goals and objectives
- Key architectural decisions
- Technology stack and dependencies
- Team conventions and patterns
2. **Current State**
- Recently implemented features
- Work in progress
- Known issues and technical debt
- Performance baselines
3. **Design Decisions**
- Architectural choices and rationale
- API design patterns
- Database schema decisions
- Security implementations
4. **Code Patterns**
- Coding conventions used
- Common patterns and abstractions
- Testing strategies
- Error handling approaches
5. **Agent Coordination History**
- Which agents worked on what
- Successful agent combinations
- Agent-specific context and findings
- Cross-agent dependencies
6. **Future Roadmap**
- Planned features
- Identified improvements
- Technical debt to address
- Performance optimization opportunities
Save this context in a structured format that can be easily restored and used by future agent invocations."
## Context Storage
The context will be saved to `.claude/context/` with:
- Timestamp-based versioning
- Structured JSON/Markdown format
- Easy restoration capabilities
- Context diffing between versions
## Usage Scenarios
This saved context enables:
- Resuming work after breaks
- Onboarding new team members
- Maintaining consistency across agent invocations
- Preserving architectural decisions
- Tracking project evolution
Context to save: $ARGUMENTS