aigroup-workflow 1.0.0

package/skills/jarvis/engineering-team/docs/skills/product-team/ux-researcher-designer.md

@@ -0,0 +1,430 @@
+---
+title: "UX Researcher & Designer — Agent Skill for Product Teams"
+description: "UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw."
+---
+
+# UX Researcher & Designer
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-lightbulb-outline: Product</span>
+<span class="meta-badge">:material-identifier: `ux-researcher-designer`</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ux-researcher-designer/SKILL.md">Source</a></span>
+</div>
+
+<div class="install-banner" markdown>
+<span class="install-label">Install:</span> <code>claude /plugin install product-skills</code>
+</div>
+
+
+Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.
+
+---
+
+## Table of Contents
+
+- [Trigger Terms](#trigger-terms)
+- [Workflows](#workflows)
+  - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)
+  - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)
+  - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)
+  - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)
+- [Tool Reference](#tool-reference)
+- [Quick Reference Tables](#quick-reference-tables)
+- [Knowledge Base](#knowledge-base)
+
+---
+
+## Trigger Terms
+
+Use this skill when you need to:
+
+- "create user persona"
+- "generate persona from data"
+- "build customer journey map"
+- "map user journey"
+- "plan usability test"
+- "design usability study"
+- "analyze user research"
+- "synthesize interview findings"
+- "identify user pain points"
+- "define user archetypes"
+- "calculate research sample size"
+- "create empathy map"
+- "identify user needs"
+
+---
+
+## Workflows
+
+### Workflow 1: Generate User Persona
+
+**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.
+
+**Steps:**
+
+1. **Prepare user data**
+
+   Required format (JSON):
+   ```json
+   [
+     {
+       "user_id": "user_1",
+       "age": 32,
+       "usage_frequency": "daily",
+       "features_used": ["dashboard", "reports", "export"],
+       "primary_device": "desktop",
+       "usage_context": "work",
+       "tech_proficiency": 7,
+       "pain_points": ["slow loading", "confusing UI"]
+     }
+   ]
+   ```
+
+2. **Run persona generator**
+   ```bash
+   # Human-readable output
+   python scripts/persona_generator.py
+
+   # JSON output for integration
+   python scripts/persona_generator.py json
+   ```
+
+3. **Review generated components**
+
+   | Component | What to Check |
+   |-----------|---------------|
+   | Archetype | Does it match the data patterns? |
+   | Demographics | Are they derived from actual data? |
+   | Goals | Are they specific and actionable? |
+   | Frustrations | Do they include frequency counts? |
+   | Design implications | Can designers act on these? |
+
+4. **Validate persona**
+
+   - Show to 3-5 real users: "Does this sound like you?"
+   - Cross-check with support tickets
+   - Verify against analytics data
+
+5. **Reference:** See `references/persona-methodology.md` for validity criteria
+
+---
+
+### Workflow 2: Create Journey Map
+
+**Situation:** You need to visualize the end-to-end user experience for a specific goal.
+
+**Steps:**
+
+1. **Define scope**
+
+   | Element | Description |
+   |---------|-------------|
+   | Persona | Which user type |
+   | Goal | What they're trying to achieve |
+   | Start | Trigger that begins journey |
+   | End | Success criteria |
+   | Timeframe | Hours/days/weeks |
+
+2. **Gather journey data**
+
+   Sources:
+   - User interviews (ask "walk me through...")
+   - Session recordings
+   - Analytics (funnel, drop-offs)
+   - Support tickets
+
+3. **Map the stages**
+
+   Typical B2B SaaS stages:
+   ```
+   Awareness → Evaluation → Onboarding → Adoption → Advocacy
+   ```
+
+4. **Fill in layers for each stage**
+
+   ```
+   Stage: [Name]
+   ├── Actions: What does user do?
+   ├── Touchpoints: Where do they interact?
+   ├── Emotions: How do they feel? (1-5)
+   ├── Pain Points: What frustrates them?
+   └── Opportunities: Where can we improve?
+   ```
+
+5. **Identify opportunities**
+
+   Priority Score = Frequency × Severity × Solvability
+
+6. **Reference:** See `references/journey-mapping-guide.md` for templates
+
+---
+
+### Workflow 3: Plan Usability Test
+
+**Situation:** You need to validate a design with real users.
+
+**Steps:**
+
+1. **Define research questions**
+
+   Transform vague goals into testable questions:
+
+   | Vague | Testable |
+   |-------|----------|
+   | "Is it easy to use?" | "Can users complete checkout in <3 min?" |
+   | "Do users like it?" | "Will users choose Design A or B?" |
+   | "Does it make sense?" | "Can users find settings without hints?" |
+
+2. **Select method**
+
+   | Method | Participants | Duration | Best For |
+   |--------|--------------|----------|----------|
+   | Moderated remote | 5-8 | 45-60 min | Deep insights |
+   | Unmoderated remote | 10-20 | 15-20 min | Quick validation |
+   | Guerrilla | 3-5 | 5-10 min | Rapid feedback |
+
+3. **Design tasks**
+
+   Good task format:
+   ```
+   SCENARIO: "Imagine you're planning a trip to Paris..."
+   GOAL: "Book a hotel for 3 nights in your budget."
+   SUCCESS: "You see the confirmation page."
+   ```
+
+   Task progression: Warm-up → Core → Secondary → Edge case → Free exploration
+
+4. **Define success metrics**
+
+   | Metric | Target |
+   |--------|--------|
+   | Completion rate | >80% |
+   | Time on task | <2× expected |
+   | Error rate | <15% |
+   | Satisfaction | >4/5 |
+
+5. **Prepare moderator guide**
+
+   - Think-aloud instructions
+   - Non-leading prompts
+   - Post-task questions
+
+6. **Reference:** See `references/usability-testing-frameworks.md` for full guide
+
+---
+
+### Workflow 4: Synthesize Research
+
+**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.
+
+**Steps:**
+
+1. **Code the data**
+
+   Tag each data point:
+   - `[GOAL]` - What they want to achieve
+   - `[PAIN]` - What frustrates them
+   - `[BEHAVIOR]` - What they actually do
+   - `[CONTEXT]` - When/where they use product
+   - `[QUOTE]` - Direct user words
+
+2. **Cluster similar patterns**
+
+   ```
+   User A: Uses daily, advanced features, shortcuts
+   User B: Uses daily, complex workflows, automation
+   User C: Uses weekly, basic needs, occasional
+
+   Cluster 1: A, B (Power Users)
+   Cluster 2: C (Casual User)
+   ```
+
+3. **Calculate segment sizes**
+
+   | Cluster | Users | % | Viability |
+   |---------|-------|---|-----------|
+   | Power Users | 18 | 36% | Primary persona |
+   | Business Users | 15 | 30% | Primary persona |
+   | Casual Users | 12 | 24% | Secondary persona |
+
+4. **Extract key findings**
+
+   For each theme:
+   - Finding statement
+   - Supporting evidence (quotes, data)
+   - Frequency (X/Y participants)
+   - Business impact
+   - Recommendation
+
+5. **Prioritize opportunities**
+
+   | Factor | Score 1-5 |
+   |--------|-----------|
+   | Frequency | How often does this occur? |
+   | Severity | How much does it hurt? |
+   | Breadth | How many users affected? |
+   | Solvability | Can we fix this? |
+
+6. **Reference:** See `references/persona-methodology.md` for analysis framework
+
+---
+
+## Tool Reference
+
+### persona_generator.py
+
+Generates data-driven personas from user research data.
+
+| Argument | Values | Default | Description |
+|----------|--------|---------|-------------|
+| format | (none), json | (none) | Output format |
+
+**Sample Output:**
+
+```
+============================================================
+PERSONA: Alex the Power User
+============================================================
+
+📝 A daily user who primarily uses the product for work purposes
+
+Archetype: Power User
+Quote: "I need tools that can keep up with my workflow"
+
+👤 Demographics:
+  • Age Range: 25-34
+  • Location Type: Urban
+  • Tech Proficiency: Advanced
+
+🎯 Goals & Needs:
+  • Complete tasks efficiently
+  • Automate workflows
+  • Access advanced features
+
+😤 Frustrations:
+  • Slow loading times (14/20 users)
+  • No keyboard shortcuts
+  • Limited API access
+
+💡 Design Implications:
+  → Optimize for speed and efficiency
+  → Provide keyboard shortcuts and power features
+  → Expose API and automation capabilities
+
+📈 Data: Based on 45 users
+    Confidence: High
+```
+
+**Archetypes Generated:**
+
+| Archetype | Signals | Design Focus |
+|-----------|---------|--------------|
+| power_user | Daily use, 10+ features | Efficiency, customization |
+| casual_user | Weekly use, 3-5 features | Simplicity, guidance |
+| business_user | Work context, team use | Collaboration, reporting |
+| mobile_first | Mobile primary | Touch, offline, speed |
+
+**Output Components:**
+
+| Component | Description |
+|-----------|-------------|
+| demographics | Age range, location, occupation, tech level |
+| psychographics | Motivations, values, attitudes, lifestyle |
+| behaviors | Usage patterns, feature preferences |
+| needs_and_goals | Primary, secondary, functional, emotional |
+| frustrations | Pain points with evidence |
+| scenarios | Contextual usage stories |
+| design_implications | Actionable recommendations |
+| data_points | Sample size, confidence level |
+
+---
+
+## Quick Reference Tables
+
+### Research Method Selection
+
+| Question Type | Best Method | Sample Size |
+|---------------|-------------|-------------|
+| "What do users do?" | Analytics, observation | 100+ events |
+| "Why do they do it?" | Interviews | 8-15 users |
+| "How well can they do it?" | Usability test | 5-8 users |
+| "What do they prefer?" | Survey, A/B test | 50+ users |
+| "What do they feel?" | Diary study, interviews | 10-15 users |
+
+### Persona Confidence Levels
+
+| Sample Size | Confidence | Use Case |
+|-------------|------------|----------|
+| 5-10 users | Low | Exploratory |
+| 11-30 users | Medium | Directional |
+| 31+ users | High | Production |
+
+### Usability Issue Severity
+
+| Severity | Definition | Action |
+|----------|------------|--------|
+| 4 - Critical | Prevents task completion | Fix immediately |
+| 3 - Major | Significant difficulty | Fix before release |
+| 2 - Minor | Causes hesitation | Fix when possible |
+| 1 - Cosmetic | Noticed but not problematic | Low priority |
+
+### Interview Question Types
+
+| Type | Example | Use For |
+|------|---------|---------|
+| Context | "Walk me through your typical day" | Understanding environment |
+| Behavior | "Show me how you do X" | Observing actual actions |
+| Goals | "What are you trying to achieve?" | Uncovering motivations |
+| Pain | "What's the hardest part?" | Identifying frustrations |
+| Reflection | "What would you change?" | Generating ideas |
+
+---
+
+## Knowledge Base
+
+Detailed reference guides in `references/`:
+
+| File | Content |
+|------|---------|
+| `persona-methodology.md` | Validity criteria, data collection, analysis framework |
+| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |
+| `example-personas.md` | 3 complete persona examples with data |
+| `usability-testing-frameworks.md` | Test planning, task design, analysis |
+
+---
+
+## Validation Checklist
+
+### Persona Quality
+- [ ] Based on 20+ users (minimum)
+- [ ] At least 2 data sources (quant + qual)
+- [ ] Specific, actionable goals
+- [ ] Frustrations include frequency counts
+- [ ] Design implications are specific
+- [ ] Confidence level stated
+
+### Journey Map Quality
+- [ ] Scope clearly defined (persona, goal, timeframe)
+- [ ] Based on real user data, not assumptions
+- [ ] All layers filled (actions, touchpoints, emotions)
+- [ ] Pain points identified per stage
+- [ ] Opportunities prioritized
+
+### Usability Test Quality
+- [ ] Research questions are testable
+- [ ] Tasks are realistic scenarios, not instructions
+- [ ] 5+ participants per design
+- [ ] Success metrics defined
+- [ ] Findings include severity ratings
+
+### Research Synthesis Quality
+- [ ] Data coded consistently
+- [ ] Patterns based on 3+ data points
+- [ ] Findings include evidence
+- [ ] Recommendations are actionable
+- [ ] Priorities justified
+
+## Related Skills
+
+- **UI Design System** (`product-team/ui-design-system/`) — Research findings inform design system decisions
+- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — Customer interview analysis complements persona research

package/skills/jarvis/engineering-team/docs/skills/project-management/atlassian-admin.md

@@ -0,0 +1,245 @@
+---
+title: "Atlassian Administrator Expert — Agent Skill for PM"
+description: "Atlassian Administrator for managing and organizing Atlassian products (Jira, Confluence, Bitbucket, Trello), users, permissions, security. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw."
+---
+
+# Atlassian Administrator Expert
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-clipboard-check-outline: Project Management</span>
+<span class="meta-badge">:material-identifier: `atlassian-admin`</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/project-management/atlassian-admin/SKILL.md">Source</a></span>
+</div>
+
+<div class="install-banner" markdown>
+<span class="install-label">Install:</span> <code>claude /plugin install pm-skills</code>
+</div>
+
+
+## Workflows
+
+### User Provisioning
+1. Create user account: `admin.atlassian.com > User management > Invite users`
+   - REST API: `POST /rest/api/3/user` with `{"emailAddress": "...", "displayName": "...","products": [...]}`
+2. Add to appropriate groups: `admin.atlassian.com > User management > Groups > [group] > Add members`
+3. Assign product access (Jira, Confluence) via `admin.atlassian.com > Products > [product] > Access`
+4. Configure default permissions per group scheme
+5. Send welcome email with onboarding info
+6. **NOTIFY**: Relevant team leads of new member
+7. **VERIFY**: Confirm user appears active at `admin.atlassian.com/o/{orgId}/users` and can log in
+
+### User Deprovisioning
+1. **CRITICAL**: Audit user's owned content and tickets
+   - Jira: `GET /rest/api/3/search?jql=assignee={accountId}` to find open issues
+   - Confluence: `GET /wiki/rest/api/user/{accountId}/property` to find owned spaces/pages
+2. Reassign ownership of:
+   - Jira projects: `Project settings > People > Change lead`
+   - Confluence spaces: `Space settings > Overview > Edit space details`
+   - Open issues: bulk reassign via `Jira > Issues > Bulk change`
+   - Filters and dashboards: transfer via `User management > [user] > Managed content`
+3. Remove from all groups: `admin.atlassian.com > User management > [user] > Groups`
+4. Revoke product access
+5. Deactivate account: `admin.atlassian.com > User management > [user] > Deactivate`
+   - REST API: `DELETE /rest/api/3/user?accountId={accountId}`
+6. **VERIFY**: Confirm `GET /rest/api/3/user?accountId={accountId}` returns `"active": false`
+7. Document deprovisioning in audit log
+8. **USE**: Jira Expert to reassign any remaining issues
+
+### Group Management
+1. Create groups: `admin.atlassian.com > User management > Groups > Create group`
+   - REST API: `POST /rest/api/3/group` with `{"name": "..."}`
+   - Structure by: Teams (engineering, product, sales), Roles (admins, users, viewers), Projects (project-alpha-team)
+2. Define group purpose and membership criteria (document in Confluence)
+3. Assign default permissions per group
+4. Add users to appropriate groups
+5. **VERIFY**: Confirm group members via `GET /rest/api/3/group/member?groupName={name}`
+6. Regular review and cleanup (quarterly)
+7. **USE**: Confluence Expert to document group structure
+
+### Permission Scheme Design
+**Jira Permission Schemes** (`Jira Settings > Issues > Permission Schemes`):
+- **Public Project**: All users can view, members can edit
+- **Team Project**: Team members full access, stakeholders view
+- **Restricted Project**: Named individuals only
+- **Admin Project**: Admins only
+
+**Confluence Permission Schemes** (`Confluence Admin > Space permissions`):
+- **Public Space**: All users view, space members edit
+- **Team Space**: Team-specific access
+- **Personal Space**: Individual user only
+- **Restricted Space**: Named individuals and groups
+
+**Best Practices**:
+- Use groups, not individual permissions
+- Principle of least privilege
+- Regular permission audits
+- Document permission rationale
+
+### SSO Configuration
+1. Choose identity provider (Okta, Azure AD, Google)
+2. Configure SAML settings: `admin.atlassian.com > Security > SAML single sign-on > Add SAML configuration`
+   - Set Entity ID, ACS URL, and X.509 certificate from IdP
+3. Test SSO with admin account (keep password login active during test)
+4. Test with regular user account
+5. Enable SSO for organization
+6. Enforce SSO: `admin.atlassian.com > Security > Authentication policies > Enforce SSO`
+7. Configure SCIM for auto-provisioning: `admin.atlassian.com > User provisioning > [IdP] > Enable SCIM`
+8. **VERIFY**: Confirm SSO flow succeeds and audit logs show `saml.login.success` events
+9. Monitor SSO logs: `admin.atlassian.com > Security > Audit log > filter: SSO`
+
+### Marketplace App Management
+1. Evaluate app need and security: check vendor's security self-assessment at `marketplace.atlassian.com`
+2. Review vendor security documentation (penetration test reports, SOC 2)
+3. Test app in sandbox environment
+4. Purchase or request trial: `admin.atlassian.com > Billing > Manage subscriptions`
+5. Install app: `admin.atlassian.com > Products > [product] > Apps > Find new apps`
+6. Configure app settings per vendor documentation
+7. Train users on app usage
+8. **VERIFY**: Confirm app appears in `GET /rest/plugins/1.0/` and health check passes
+9. Monitor app performance and usage; review annually for continued need
+
+### System Performance Optimization
+**Jira** (`Jira Settings > System`):
+- Archive old projects: `Project settings > Archive project`
+- Reindex: `Jira Settings > System > Indexing > Full re-index`
+- Clean up unused workflows and schemes: `Jira Settings > Issues > Workflows`
+- Monitor queue/thread counts: `Jira Settings > System > System info`
+
+**Confluence** (`Confluence Admin > Configuration`):
+- Archive inactive spaces: `Space tools > Overview > Archive space`
+- Remove orphaned pages: `Confluence Admin > Orphaned pages`
+- Monitor index and cache: `Confluence Admin > Cache management`
+
+**Monitoring Cadence**:
+- Daily health checks: `admin.atlassian.com > Products > [product] > Health`
+- Weekly performance reports
+- Monthly capacity planning
+- Quarterly optimization reviews
+
+### Integration Setup
+**Common Integrations**:
+- **Slack**: `Jira Settings > Apps > Slack integration` — notifications for Jira and Confluence
+- **GitHub/Bitbucket**: `Jira Settings > Apps > DVCS accounts` — link commits to issues
+- **Microsoft Teams**: `admin.atlassian.com > Apps > Microsoft Teams`
+- **Zoom**: Available via Marketplace app `zoom-for-jira`
+- **Salesforce**: Via Marketplace app `salesforce-connector`
+
+**Configuration Steps**:
+1. Review integration requirements and OAuth scopes needed
+2. Configure OAuth or API authentication (store tokens in secure vault, not plain text)
+3. Map fields and data flows
+4. Test integration thoroughly with sample data
+5. Document configuration in Confluence runbook
+6. Train users on integration features
+7. **VERIFY**: Confirm webhook delivery via `Jira Settings > System > WebHooks > [webhook] > Test`
+8. Monitor integration health via app-specific dashboards
+
+## Global Configuration
+
+### Jira Global Settings (`Jira Settings > Issues`)
+**Issue Types**: Create and manage org-wide issue types; define issue type schemes; standardize across projects
+**Workflows**: Create global workflow templates via `Workflows > Add workflow`; manage workflow schemes
+**Custom Fields**: Create org-wide custom fields at `Custom fields > Add custom field`; manage field configurations and context
+**Notification Schemes**: Configure default notification rules; create custom notification schemes; manage email templates
+
+### Confluence Global Settings (`Confluence Admin`)
+**Blueprints & Templates**: Create org-wide templates at `Configuration > Global Templates and Blueprints`; manage blueprint availability
+**Themes & Appearance**: Configure org branding at `Configuration > Themes`; customize logos and colors
+**Macros**: Enable/disable macros at `Configuration > Macro usage`; configure macro permissions
+
+### Security Settings (`admin.atlassian.com > Security`)
+**Authentication**:
+- Password policies: `Security > Authentication policies > Edit`
+- Session timeout: `Security > Session duration`
+- API token management: `Security > API token controls`
+
+**Data Residency**: Configure data location at `admin.atlassian.com > Data residency > Pin products`
+
+**Audit Logs**: `admin.atlassian.com > Security > Audit log`
+- Enable comprehensive logging; export via `GET /admin/v1/orgs/{orgId}/audit-log`
+- Retain per policy (minimum 7 years for SOC 2/GDPR compliance)
+
+## Governance & Policies
+
+### Access Governance
+- Quarterly review of all user access: `admin.atlassian.com > User management > Export users`
+- Verify user roles and permissions; remove inactive users
+- Limit org admins to 2–3 individuals; audit admin actions monthly
+- Require MFA for all admins: `Security > Authentication policies > Require 2FA`
+
+### Naming Conventions
+**Jira**: Project keys 3–4 uppercase letters (PROJ, WEB); issue types Title Case; custom fields prefixed (CF: Story Points)
+**Confluence**: Spaces use Team/Project prefix (TEAM: Engineering); pages descriptive and consistent; labels lowercase, hyphen-separated
+
+### Change Management
+**Major Changes**: Announce 2 weeks in advance; test in sandbox; create rollback plan; execute during off-peak; post-implementation review
+**Minor Changes**: Announce 48 hours in advance; document in change log; monitor for issues
+
+## Disaster Recovery
+
+### Backup Strategy
+**Jira & Confluence**: Daily automated backups; weekly manual verification; 30-day retention; offsite storage
+- Trigger manual backup: `Jira Settings > System > Backup system` / `Confluence Admin > Backup and Restore`
+
+**Recovery Testing**: Quarterly recovery drills; document procedures; measure RTO and RPO
+
+### Incident Response
+**Severity Levels**:
+- **P1 (Critical)**: System down — respond in 15 min
+- **P2 (High)**: Major feature broken — respond in 1 hour
+- **P3 (Medium)**: Minor issue — respond in 4 hours
+- **P4 (Low)**: Enhancement — respond in 24 hours
+
+**Response Steps**:
+1. Acknowledge and log incident
+2. Assess impact and severity
+3. Communicate status to stakeholders
+4. Investigate root cause (check `admin.atlassian.com > Products > [product] > Health` and Atlassian Status Page)
+5. Implement fix
+6. **VERIFY**: Confirm resolution via affected user test and health check
+7. Post-mortem and lessons learned
+
+## Metrics & Reporting
+
+**System Health**: Active users (daily/weekly/monthly), storage utilization, API rate limits, integration health, response times
+- Export via: `GET /admin/v1/orgs/{orgId}/users` for user counts; product-specific analytics dashboards
+
+**Usage Analytics**: Most active projects/spaces, content creation trends, user engagement, search patterns
+**Compliance Metrics**: User access review completion, security audit findings, failed login attempts, API token usage
+
+## Decision Framework & Handoff Protocols
+
+**Escalate to Atlassian Support**: System outage, performance degradation org-wide, data loss/corruption, license/billing issues, complex migrations
+
+**Delegate to Product Experts**:
+- Jira Expert: Project-specific configuration
+- Confluence Expert: Space-specific settings
+- Scrum Master: Team workflow needs
+- Senior PM: Strategic planning input
+
+**Involve Security Team**: Security incidents, unusual access patterns, compliance audit preparation, new integration security review
+
+**TO Jira Expert**: New global workflows, custom fields, permission schemes, or automation capabilities available
+**TO Confluence Expert**: New global templates, space permission schemes, blueprints, or macros configured
+**TO Senior PM**: Usage analytics, capacity planning insights, cost optimization, security compliance status
+**TO Scrum Master**: Team access provisioned, board configuration options, automation rules, integrations enabled
+**FROM All Roles**: User access requests, permission changes, app installation requests, configuration support, incident reports
+
+## Atlassian MCP Integration
+
+**Primary Tools**: Jira MCP, Confluence MCP
+
+**Admin Operations**:
+- User and group management via API
+- Bulk permission updates
+- Configuration audits
+- Usage reporting
+- System health monitoring
+- Automated compliance checks
+
+**Integration Points**:
+- Support all roles with admin capabilities
+- Enable Jira Expert with global configurations
+- Provide Confluence Expert with template management
+- Ensure Senior PM has visibility into org health
+- Enable Scrum Master with team provisioning