aigroup-workflow 1.0.1 → 1.1.1

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

@@ -1,263 +0,0 @@
----
-title: "Atlassian Template & Files Creator Expert — Agent Skill for PM"
-description: "Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw."
----
-
-# Atlassian Template & Files Creator Expert
-
-<div class="page-meta" markdown>
-<span class="meta-badge">:material-clipboard-check-outline: Project Management</span>
-<span class="meta-badge">:material-identifier: `atlassian-templates`</span>
-<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/project-management/atlassian-templates/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>
-
-
-Specialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards.
-
----
-
-## Workflows
-
-### Template Creation Process
-1. **Discover**: Interview stakeholders to understand needs
-2. **Analyze**: Review existing content patterns
-3. **Design**: Create template structure and placeholders
-4. **Implement**: Build template with macros and formatting
-5. **Test**: Validate with sample data — confirm template renders correctly in preview before publishing
-6. **Document**: Create usage instructions
-7. **Publish**: Deploy to appropriate space/project via MCP (see MCP Operations below)
-8. **Verify**: Confirm deployment success; roll back to previous version if errors occur
-9. **Train**: Educate users on template usage
-10. **Monitor**: Track adoption and gather feedback
-11. **Iterate**: Refine based on usage
-
-### Template Modification Process
-1. **Assess**: Review change request and impact
-2. **Version**: Create new version, keep old available
-3. **Modify**: Update template structure/content
-4. **Test**: Validate changes don't break existing usage; preview updated template before publishing
-5. **Migrate**: Provide migration path for existing content
-6. **Communicate**: Announce changes to users
-7. **Support**: Assist users with migration
-8. **Archive**: Deprecate old version after transition; confirm deprecated template is unlisted, not deleted
-
-### Blueprint Development
-1. Define blueprint scope and purpose
-2. Design multi-page structure
-3. Create page templates for each section
-4. Configure page creation rules
-5. Add dynamic content (Jira queries, user data)
-6. Test blueprint creation flow end-to-end with a sample space
-7. Verify all macro references resolve correctly before deployment
-8. **HANDOFF TO**: Atlassian Admin for global deployment
-
----
-
-## Confluence Templates Library
-
-See **TEMPLATES.md** for full reference tables and copy-paste-ready template structures. The following summarises the standard types this skill creates and maintains.
-
-### Confluence Template Types
-| Template | Purpose | Key Macros Used |
-|----------|---------|-----------------|
-| **Meeting Notes** | Structured meeting records with agenda, decisions, and action items | `{date}`, `{tasks}`, `{panel}`, `{info}`, `{note}` |
-| **Project Charter** | Org-level project scope, stakeholder RACI, timeline, and budget | `{panel}`, `{status}`, `{timeline}`, `{info}` |
-| **Sprint Retrospective** | Agile ceremony template with What Went Well / Didn't Go Well / Actions | `{panel}`, `{expand}`, `{tasks}`, `{status}` |
-| **PRD** | Feature definition with goals, user stories, functional/non-functional requirements, and release plan | `{panel}`, `{status}`, `{jira}`, `{warning}` |
-| **Decision Log** | Structured option analysis with decision matrix and implementation tracking | `{panel}`, `{status}`, `{info}`, `{tasks}` |
-
-**Standard Sections** included across all Confluence templates:
-- Header panel with metadata (owner, date, status)
-- Clearly labelled content sections with inline placeholder instructions
-- Action items block using `{tasks}` macro
-- Related links and references
-
-### Complete Example: Meeting Notes Template
-
-The following is a copy-paste-ready Meeting Notes template in Confluence storage format (wiki markup):
-
-```
-{panel:title=Meeting Metadata|borderColor=#0052CC|titleBGColor=#0052CC|titleColor=#FFFFFF}
-*Date:* {date}
-*Owner / Facilitator:* @[facilitator name]
-*Attendees:* @[name], @[name]
-*Status:* {status:colour=Yellow|title=In Progress}
-{panel}
-
-h2. Agenda
-# [Agenda item 1]
-# [Agenda item 2]
-# [Agenda item 3]
-
-h2. Discussion & Decisions
-{panel:title=Key Decisions|borderColor=#36B37E|titleBGColor=#36B37E|titleColor=#FFFFFF}
-* *Decision 1:* [What was decided and why]
-* *Decision 2:* [What was decided and why]
-{panel}
-
-{info:title=Notes}
-[Detailed discussion notes, context, or background here]
-{info}
-
-h2. Action Items
-{tasks}
-* [ ] [Action item] — Owner: @[name] — Due: {date}
-* [ ] [Action item] — Owner: @[name] — Due: {date}
-{tasks}
-
-h2. Next Steps & Related Links
-* Next meeting: {date}
-* Related pages: [link]
-* Related Jira issues: {jira:key=PROJ-123}
-```
-
-> Full examples for all other template types (Project Charter, Sprint Retrospective, PRD, Decision Log) and all Jira templates can be generated on request or found in **TEMPLATES.md**.
-
----
-
-## Jira Templates Library
-
-### Jira Template Types
-| Template | Purpose | Key Sections |
-|----------|---------|--------------|
-| **User Story** | Feature requests in As a / I want / So that format | Acceptance Criteria (Given/When/Then), Design links, Technical Notes, Definition of Done |
-| **Bug Report** | Defect capture with reproduction steps | Environment, Steps to Reproduce, Expected vs Actual Behavior, Severity, Workaround |
-| **Epic** | High-level initiative scope | Vision, Goals, Success Metrics, Story Breakdown, Dependencies, Timeline |
-
-**Standard Sections** included across all Jira templates:
-- Clear summary line
-- Acceptance or success criteria as checkboxes
-- Related issues and dependencies block
-- Definition of Done (for stories)
-
----
-
-## Macro Usage Guidelines
-
-**Dynamic Content**: Use macros for auto-updating content (dates, user mentions, Jira queries)
-**Visual Hierarchy**: Use `{panel}`, `{info}`, and `{note}` to create visual distinction
-**Interactivity**: Use `{expand}` for collapsible sections in long templates
-**Integration**: Embed Jira charts and tables via `{jira}` macro for live data
-
----
-
-## Atlassian MCP Integration
-
-**Primary Tools**: Confluence MCP, Jira MCP
-
-### Template Operations via MCP
-
-All MCP calls below use the exact parameter names expected by the Atlassian MCP server. Replace angle-bracket placeholders with real values before executing.
-
-**Create a Confluence page template:**
-```json
-{
-  "tool": "confluence_create_page",
-  "parameters": {
-    "space_key": "PROJ",
-    "title": "Template: Meeting Notes",
-    "body": "<storage-format template content>",
-    "labels": ["template", "meeting-notes"],
-    "parent_id": "<optional parent page id>"
-  }
-}
-```
-
-**Update an existing template:**
-```json
-{
-  "tool": "confluence_update_page",
-  "parameters": {
-    "page_id": "<existing page id>",
-    "version": "<current_version + 1>",
-    "title": "Template: Meeting Notes",
-    "body": "<updated storage-format content>",
-    "version_comment": "v2 — added status macro to header"
-  }
-}
-```
-
-**Create a Jira issue description template (via field configuration):**
-```json
-{
-  "tool": "jira_update_field_configuration",
-  "parameters": {
-    "project_key": "PROJ",
-    "field_id": "description",
-    "default_value": "<template markdown or Atlassian Document Format JSON>"
-  }
-}
-```
-
-**Deploy template to multiple spaces (batch):**
-```json
-// Repeat for each target space key
-{
-  "tool": "confluence_create_page",
-  "parameters": {
-    "space_key": "<SPACE_KEY>",
-    "title": "Template: Meeting Notes",
-    "body": "<storage-format template content>",
-    "labels": ["template"]
-  }
-}
-// After each create, verify:
-{
-  "tool": "confluence_get_page",
-  "parameters": {
-    "space_key": "<SPACE_KEY>",
-    "title": "Template: Meeting Notes"
-  }
-}
-// Assert response status == 200 and page body is non-empty before proceeding to next space
-```
-
-**Validation checkpoint after deployment:**
-- Retrieve the created/updated page and assert it renders without macro errors
-- Check that `{jira}` embeds resolve against the target Jira project
-- Confirm `{tasks}` blocks are interactive in the published view
-- If any check fails: revert using `confluence_update_page` with `version: <current + 1>` and the previous version body
-
----
-
-## Best Practices & Governance
-
-**Org-Specific Standards:**
-- Track template versions with version notes in the page header
-- Mark outdated templates with a `{warning}` banner before archiving; archive (do not delete)
-- Maintain usage guides linked from each template
-- Gather feedback on a quarterly review cycle; incorporate usage metrics before deprecating
-
-**Quality Gates (apply before every deployment):**
-- Example content provided for each section
-- Tested with sample data in preview
-- Version comment added to change log
-- Feedback mechanism in place (comments enabled or linked survey)
-
-**Governance Process**:
-1. Request and justification
-2. Design and review
-3. Testing with pilot users
-4. Documentation
-5. Approval
-6. Deployment (via MCP or manual)
-7. Training
-8. Monitoring
-
----
-
-## Handoff Protocols
-
-See **HANDOFFS.md** for the full handoff matrix. Summary:
-
-| Partner | Receives FROM | Sends TO |
-|---------|--------------|---------|
-| **Senior PM** | Template requirements, reporting templates, executive formats | Completed templates, usage analytics, optimization suggestions |
-| **Scrum Master** | Sprint ceremony needs, team-specific requests, retro format preferences | Sprint-ready templates, agile ceremony structures, velocity tracking templates |
-| **Jira Expert** | Issue template requirements, custom field display needs | Issue description templates, field config templates, JQL query templates |
-| **Confluence Expert** | Space-specific needs, global template requests, blueprint requirements | Configured page templates, blueprint structures, deployment plans |
-| **Atlassian Admin** | Org-wide standards, global deployment requirements, compliance templates | Global templates for approval, usage reports, compliance status |

package/skills/jarvis/engineering-team/docs/skills/project-management/confluence-expert.md

@@ -1,386 +0,0 @@
----
-title: "Atlassian Confluence Expert — Agent Skill for PM"
-description: "Atlassian Confluence expert for creating and managing spaces, knowledge bases, and documentation. Configures space permissions and hierarchies. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw."
----
-
-# Atlassian Confluence Expert
-
-<div class="page-meta" markdown>
-<span class="meta-badge">:material-clipboard-check-outline: Project Management</span>
-<span class="meta-badge">:material-identifier: `confluence-expert`</span>
-<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/project-management/confluence-expert/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>
-
-
-Master-level expertise in Confluence space management, documentation architecture, content creation, macros, templates, and collaborative knowledge management.
-
-## Atlassian MCP Integration
-
-**Primary Tool**: Confluence MCP Server
-
-**Key Operations**:
-
-```
-// Create a new space
-create_space({ key: "TEAM", name: "Engineering Team", description: "Engineering team knowledge base" })
-
-// Create a page under a parent
-create_page({ spaceKey: "TEAM", title: "Sprint 42 Notes", parentId: "123456", body: "<p>Meeting notes in storage-format HTML</p>" })
-
-// Update an existing page (version must be incremented)
-update_page({ pageId: "789012", version: 4, body: "<p>Updated content</p>" })
-
-// Delete a page
-delete_page({ pageId: "789012" })
-
-// Search with CQL
-search({ cql: 'space = "TEAM" AND label = "meeting-notes" ORDER BY lastModified DESC' })
-
-// Retrieve child pages for hierarchy inspection
-get_children({ pageId: "123456" })
-
-// Apply a label to a page
-add_label({ pageId: "789012", label: "archived" })
-```
-
-**Integration Points**:
-- Create documentation for Senior PM projects
-- Support Scrum Master with ceremony templates
-- Link to Jira issues for Jira Expert
-- Provide templates for Template Creator
-
-> **See also**: `MACROS.md` for macro syntax reference, `TEMPLATES.md` for full template library, `PERMISSIONS.md` for permission scheme details.
-
-## Workflows
-
-### Space Creation
-1. Determine space type (Team, Project, Knowledge Base, Personal)
-2. Create space with clear name and description
-3. Set space homepage with overview
-4. Configure space permissions:
-   - View, Edit, Create, Delete
-   - Admin privileges
-5. Create initial page tree structure
-6. Add space shortcuts for navigation
-7. **Verify**: Navigate to the space URL and confirm the homepage loads; check that a non-admin test user sees the correct permission level
-8. **HANDOFF TO**: Teams for content population
-
-### Page Architecture
-**Best Practices**:
-- Use page hierarchy (parent-child relationships)
-- Maximum 3 levels deep for navigation
-- Consistent naming conventions
-- Date-stamp meeting notes
-
-**Recommended Structure**:
-```
-Space Home
-├── Overview & Getting Started
-├── Team Information
-│   ├── Team Members & Roles
-│   ├── Communication Channels
-│   └── Working Agreements
-├── Projects
-│   ├── Project A
-│   │   ├── Overview
-│   │   ├── Requirements
-│   │   └── Meeting Notes
-│   └── Project B
-├── Processes & Workflows
-├── Meeting Notes (Archive)
-└── Resources & References
-```
-
-### Template Creation
-1. Identify repeatable content pattern
-2. Create page with structure and placeholders
-3. Add instructions in placeholders
-4. Format with appropriate macros
-5. Save as template
-6. Share with space or make global
-7. **Verify**: Create a test page from the template and confirm all placeholders render correctly before sharing with the team
-8. **USE**: References for advanced template patterns
-
-### Documentation Strategy
-1. **Assess** current documentation state
-2. **Define** documentation goals and audience
-3. **Organize** content taxonomy and structure
-4. **Create** templates and guidelines
-5. **Migrate** existing documentation
-6. **Train** teams on best practices
-7. **Monitor** usage and adoption
-8. **REPORT TO**: Senior PM on documentation health
-
-### Knowledge Base Management
-**Article Types**:
-- How-to guides
-- Troubleshooting docs
-- FAQs
-- Reference documentation
-- Process documentation
-
-**Quality Standards**:
-- Clear title and description
-- Structured with headings
-- Updated date visible
-- Owner identified
-- Reviewed quarterly
-
-## Essential Macros
-
-> Full macro reference with all parameters: see `MACROS.md`.
-
-### Content Macros
-**Info, Note, Warning, Tip**:
-```
-{info}
-Important information here
-{info}
-```
-
-**Expand**:
-```
-{expand:title=Click to expand}
-Hidden content here
-{expand}
-```
-
-**Table of Contents**:
-```
-{toc:maxLevel=3}
-```
-
-**Excerpt & Excerpt Include**:
-```
-{excerpt}
-Reusable content
-{excerpt}
-
-{excerpt-include:Page Name}
-```
-
-### Dynamic Content
-**Jira Issues**:
-```
-{jira:JQL=project = PROJ AND status = "In Progress"}
-```
-
-**Jira Chart**:
-```
-{jirachart:type=pie|jql=project = PROJ|statType=statuses}
-```
-
-**Recently Updated**:
-```
-{recently-updated:spaces=@all|max=10}
-```
-
-**Content by Label**:
-```
-{contentbylabel:label=meeting-notes|maxResults=20}
-```
-
-### Collaboration Macros
-**Status**:
-```
-{status:colour=Green|title=Approved}
-```
-
-**Task List**:
-```
-{tasks}
-- [ ] Task 1
-- [x] Task 2 completed
-{tasks}
-```
-
-**User Mention**:
-```
-@username
-```
-
-**Date**:
-```
-{date:format=dd MMM yyyy}
-```
-
-## Page Layouts & Formatting
-
-**Two-Column Layout**:
-```
-{section}
-{column:width=50%}
-Left content
-{column}
-{column:width=50%}
-Right content
-{column}
-{section}
-```
-
-**Panel**:
-```
-{panel:title=Panel Title|borderColor=#ccc}
-Panel content
-{panel}
-```
-
-**Code Block**:
-```
-{code:javascript}
-const example = "code here";
-{code}
-```
-
-## Templates Library
-
-> Full template library with complete markup: see `TEMPLATES.md`. Key templates summarised below.
-
-| Template | Purpose | Key Sections |
-|----------|---------|--------------|
-| **Meeting Notes** | Sprint/team meetings | Agenda, Discussion, Decisions, Action Items (tasks macro) |
-| **Project Overview** | Project kickoff & status | Quick Facts panel, Objectives, Stakeholders table, Milestones (Jira macro), Risks |
-| **Decision Log** | Architectural/strategic decisions | Context, Options Considered, Decision, Consequences, Next Steps |
-| **Sprint Retrospective** | Agile ceremony docs | What Went Well (info), What Didn't (warning), Action Items (tasks), Metrics |
-
-## Space Permissions
-
-> Full permission scheme details: see `PERMISSIONS.md`.
-
-### Permission Schemes
-**Public Space**:
-- All users: View
-- Team members: Edit, Create
-- Space admins: Admin
-
-**Team Space**:
-- Team members: View, Edit, Create
-- Team leads: Admin
-- Others: No access
-
-**Project Space**:
-- Stakeholders: View
-- Project team: Edit, Create
-- PM: Admin
-
-## Content Governance
-
-**Review Cycles**:
-- Critical docs: Monthly
-- Standard docs: Quarterly
-- Archive docs: Annually
-
-**Archiving Strategy**:
-- Move outdated content to Archive space
-- Label with "archived" and date
-- Maintain for 2 years, then delete
-- Keep audit trail
-
-**Content Quality Checklist**:
-- [ ] Clear, descriptive title
-- [ ] Owner/author identified
-- [ ] Last updated date visible
-- [ ] Appropriate labels applied
-- [ ] Links functional
-- [ ] Formatting consistent
-- [ ] No sensitive data exposed
-
-## Decision Framework
-
-**When to Escalate to Atlassian Admin**:
-- Need org-wide template
-- Require cross-space permissions
-- Blueprint configuration
-- Global automation rules
-- Space export/import
-
-**When to Collaborate with Jira Expert**:
-- Embed Jira queries and charts
-- Link pages to Jira issues
-- Create Jira-based reports
-- Sync documentation with tickets
-
-**When to Support Scrum Master**:
-- Sprint documentation templates
-- Retrospective pages
-- Team working agreements
-- Process documentation
-
-**When to Support Senior PM**:
-- Executive report pages
-- Portfolio documentation
-- Stakeholder communication
-- Strategic planning docs
-
-## Handoff Protocols
-
-**FROM Senior PM**:
-- Documentation requirements
-- Space structure needs
-- Template requirements
-- Knowledge management strategy
-
-**TO Senior PM**:
-- Documentation coverage reports
-- Content usage analytics
-- Knowledge gaps identified
-- Template adoption metrics
-
-**FROM Scrum Master**:
-- Sprint ceremony templates
-- Team documentation needs
-- Meeting notes structure
-- Retrospective format
-
-**TO Scrum Master**:
-- Configured templates
-- Space for team docs
-- Training on best practices
-- Documentation guidelines
-
-**WITH Jira Expert**:
-- Jira-Confluence linking
-- Embedded Jira reports
-- Issue-to-page connections
-- Cross-tool workflow
-
-## Best Practices
-
-**Organization**:
-- Consistent naming conventions
-- Meaningful labels
-- Logical page hierarchy
-- Related pages linked
-- Clear navigation
-
-**Maintenance**:
-- Regular content audits
-- Remove duplication
-- Update outdated information
-- Archive obsolete content
-- Monitor page analytics
-
-## Analytics & Metrics
-
-**Usage Metrics**:
-- Page views per space
-- Most visited pages
-- Search queries
-- Contributor activity
-- Orphaned pages
-
-**Health Indicators**:
-- Pages without recent updates
-- Pages without owners
-- Duplicate content
-- Broken links
-- Empty spaces
-
-## Related Skills
-
-- **Jira Expert** (`project-management/jira-expert/`) — Jira issue macros and linking complement Confluence docs
-- **Atlassian Templates** (`project-management/atlassian-templates/`) — Template patterns for Confluence content creation

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

@@ -1,62 +0,0 @@
----
-title: "Project Management Skills — Agent Skills & Codex Plugins"
-description: "7 project management skills — project management agent skill and Claude Code plugin for sprints, Jira, and Confluence. Works with Claude Code, Codex CLI, Gemini CLI, and OpenClaw."
----
-
-<div class="domain-header" markdown>
-
-# :material-clipboard-check-outline: Project Management
-
-<p class="domain-count">7 skills in this domain</p>
-
-</div>
-
-<div class="install-banner" markdown>
-<span class="install-label">Install all:</span> <code>claude /plugin install pm-skills</code>
-</div>
-
-<div class="grid cards" markdown>
-
--   **[Atlassian Administrator Expert](atlassian-admin.md)**
-
-    ---
-
-    1. Create user account: admin.atlassian.com > User management > Invite users
-
--   **[Atlassian Template & Files Creator Expert](atlassian-templates.md)**
-
-    ---
-
-    Specialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consist...
-
--   **[Atlassian Confluence Expert](confluence-expert.md)**
-
-    ---
-
-    Master-level expertise in Confluence space management, documentation architecture, content creation, macros, template...
-
--   **[Atlassian Jira Expert](jira-expert.md)**
-
-    ---
-
-    Master-level expertise in Jira configuration, project management, JQL, workflows, automation, and reporting. Handles ...
-
--   **[Project Management Skills](project-management.md)**
-
-    ---
-
-    6 production-ready project management skills with Atlassian MCP integration.
-
--   **[Scrum Master Expert](scrum-master.md)**
-
-    ---
-
-    Data-driven Scrum Master skill combining sprint analytics, probabilistic forecasting, and team development coaching. ...
-
--   **[Senior Project Management Expert](senior-pm.md)**
-
-    ---
-
-    Strategic project management for enterprise software, SaaS, and digital transformation initiatives. Provides portfoli...
-
-</div>