mirror of
https://github.com/wshobson/agents.git
synced 2026-03-18 09:37:15 +00:00
3802bca865
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
73 lines
2.5 KiB
Markdown
73 lines
2.5 KiB
Markdown
---
|
|
model: sonnet
|
|
---
|
|
|
|
# Standup Notes Generator
|
|
|
|
Generate daily standup notes by reviewing Obsidian vault context and Jira tickets.
|
|
|
|
## Usage
|
|
```
|
|
/standup-notes
|
|
```
|
|
|
|
## Prerequisites
|
|
|
|
- Enable the **mcp-obsidian** provider with read/write access to the target vault.
|
|
- Configure the **atlassian** provider with Jira credentials that can query the team's backlog.
|
|
- Optional: connect calendar integrations if you want meetings to appear automatically.
|
|
|
|
## Process
|
|
|
|
1. **Gather Context from Obsidian**
|
|
- Use `mcp__mcp-obsidian__obsidian_get_recent_changes` to find recently modified files
|
|
- Use `mcp__mcp-obsidian__obsidian_get_recent_periodic_notes` to get recent daily notes
|
|
- Look for project updates, completed tasks, and ongoing work
|
|
|
|
2. **Check Jira Tickets**
|
|
- Use `mcp__atlassian__searchJiraIssuesUsingJql` to find tickets assigned to current user (fall back to asking the user for updates if the Atlassian connector is unavailable)
|
|
- Filter for:
|
|
- In Progress tickets (current work)
|
|
- Recently resolved/closed tickets (yesterday's accomplishments)
|
|
- Upcoming/todo tickets (today's planned work)
|
|
|
|
3. **Generate Standup Notes**
|
|
Format:
|
|
```
|
|
Morning!
|
|
Yesterday:
|
|
|
|
• [Completed tasks from Jira and Obsidian notes]
|
|
• [Key accomplishments and milestones]
|
|
|
|
Today:
|
|
|
|
• [In-progress Jira tickets]
|
|
• [Planned work from tickets and notes]
|
|
• [Meetings from calendar/notes]
|
|
|
|
Note: [Any blockers, dependencies, or important context]
|
|
```
|
|
|
|
4. **Write to Obsidian**
|
|
- Create file in `Standup Notes/YYYY-MM-DD.md` format (or summarize in the chat if the Obsidian connector is disabled)
|
|
- Use `mcp__mcp-obsidian__obsidian_append_content` to write the generated notes when available
|
|
|
|
## Implementation Steps
|
|
|
|
1. Get current user info from Atlassian
|
|
2. Search for recent Obsidian changes (last 2 days)
|
|
3. Query Jira for:
|
|
- `assignee = currentUser() AND (status CHANGED FROM "In Progress" TO "Done" DURING (-1d, now()) OR resolutiondate >= -1d)`
|
|
- `assignee = currentUser() AND status = "In Progress"`
|
|
- `assignee = currentUser() AND status in ("To Do", "Open") AND (sprint in openSprints() OR priority in (High, Highest))`
|
|
4. Parse and categorize findings
|
|
5. Generate formatted standup notes
|
|
6. Save to Obsidian vault
|
|
|
|
## Context Extraction Patterns
|
|
|
|
- Look for keywords: "completed", "finished", "deployed", "released", "fixed", "implemented"
|
|
- Extract meeting notes and action items
|
|
- Identify blockers or dependencies mentioned
|
|
- Pull sprint goals and objectives |