claude-code-arcane 1.0.0

package/skills/senior-pm/assets/project_charter_template.md

@@ -0,0 +1,274 @@
+# Project Charter Template
+
+**Project Name:** [Project Name]  
+**Project ID:** [Unique Identifier]  
+**Prepared By:** [Project Manager Name]  
+**Date:** [Charter Date]  
+**Version:** [Version Number]  
+
+---
+
+## Executive Summary
+
+**One-sentence Project Description:**
+[Clear, concise statement of what the project will deliver and its primary value]
+
+**Strategic Alignment:**
+- Business Objective: [Link to specific business goal/OKR]
+- Strategic Priority: [High/Medium/Low with justification]
+- Portfolio Fit: [How this project fits within broader portfolio strategy]
+
+---
+
+## Project Definition
+
+### Project Purpose & Business Case
+
+**Problem Statement:**
+[Clear articulation of the business problem or opportunity this project addresses]
+
+**Business Justification:**
+- Financial Impact: [ROI, NPV, cost savings, revenue impact]
+- Strategic Benefits: [Market position, competitive advantage, capability building]
+- Risk of NOT Doing: [Consequences of maintaining status quo]
+
+**Expected Business Value:**
+- Quantified Benefits: [Specific metrics and targets]
+- Qualitative Benefits: [Brand, customer satisfaction, employee engagement]
+- Success Metrics: [How success will be measured]
+
+### Scope Definition
+
+**In Scope:**
+- [Specific deliverable 1 with acceptance criteria]
+- [Specific deliverable 2 with acceptance criteria]
+- [Specific deliverable 3 with acceptance criteria]
+
+**Out of Scope:**
+- [Explicitly excluded item 1 - prevents scope creep]
+- [Explicitly excluded item 2 - prevents scope creep]
+- [Future phases or features deferred]
+
+**Key Deliverables:**
+| Deliverable | Description | Acceptance Criteria | Due Date |
+|-------------|-------------|-------------------|----------|
+| [Name] | [Description] | [Measurable criteria] | [Date] |
+| [Name] | [Description] | [Measurable criteria] | [Date] |
+
+---
+
+## Success Criteria
+
+### Primary Success Criteria
+1. **[Criterion 1]:** [Specific, measurable outcome with target value]
+2. **[Criterion 2]:** [Specific, measurable outcome with target value]
+3. **[Criterion 3]:** [Specific, measurable outcome with target value]
+
+### Key Performance Indicators (KPIs)
+| KPI | Baseline | Target | Measurement Method | Review Frequency |
+|-----|----------|--------|-------------------|------------------|
+| [KPI Name] | [Current State] | [Desired State] | [How Measured] | [When Reviewed] |
+
+### Quality Gates
+- **Gate 1:** [Milestone] - [Quality criteria that must be met]
+- **Gate 2:** [Milestone] - [Quality criteria that must be met]
+- **Gate 3:** [Milestone] - [Quality criteria that must be met]
+
+---
+
+## Project Organization & RACI
+
+### Steering Committee
+| Role | Name | Responsibilities |
+|------|------|-----------------|
+| Executive Sponsor | [Name] | Final accountability, funding authority, strategic alignment |
+| Business Owner | [Name] | Business requirements, user acceptance, benefits realization |
+| Technical Owner | [Name] | Technical architecture, standards compliance, technical risk |
+
+### Core Project Team
+| Role | Name | RACI Key | Responsibilities |
+|------|------|----------|-----------------|
+| Project Manager | [Name] | A | Overall project delivery, timeline, budget, risk management |
+| Product Owner | [Name] | R | Requirements definition, backlog prioritization, user stories |
+| Technical Lead | [Name] | R | Technical design, code quality, technical decision-making |
+| QA Lead | [Name] | R | Test strategy, quality assurance, defect management |
+| UI/UX Designer | [Name] | R | User experience design, interface design, usability |
+
+### Extended Stakeholders
+| Stakeholder Group | Representative | Interest Level | Influence Level | Communication Needs |
+|-------------------|----------------|----------------|-----------------|-------------------|
+| [Department/Group] | [Name] | [High/Medium/Low] | [High/Medium/Low] | [Frequency and method] |
+
+### RACI Matrix - Key Decisions
+| Decision/Activity | Project Manager | Product Owner | Tech Lead | QA Lead | Sponsor |
+|-------------------|-----------------|---------------|-----------|---------|---------|
+| Requirements approval | A | R | C | C | I |
+| Technical architecture | A | C | R | C | I |
+| Go-live decision | A | C | C | C | R |
+| Scope changes | A | R | C | C | R |
+
+**RACI Legend:** R=Responsible, A=Accountable, C=Consulted, I=Informed
+
+---
+
+## Timeline & Milestones
+
+### High-Level Timeline
+| Phase | Start Date | End Date | Key Deliverables | Dependencies |
+|-------|------------|----------|-----------------|--------------|
+| Discovery | [Date] | [Date] | Requirements, Architecture | [Dependencies] |
+| Development | [Date] | [Date] | Core Features, Testing | [Dependencies] |
+| Testing | [Date] | [Date] | QA Sign-off, UAT | [Dependencies] |
+| Deployment | [Date] | [Date] | Production Release | [Dependencies] |
+
+### Critical Path Milestones
+1. **[Milestone 1]:** [Date] - [Deliverable and significance]
+2. **[Milestone 2]:** [Date] - [Deliverable and significance]
+3. **[Milestone 3]:** [Date] - [Deliverable and significance]
+
+### Dependencies & Constraints
+**External Dependencies:**
+- [Dependency 1]: [Description, owner, required date]
+- [Dependency 2]: [Description, owner, required date]
+
+**Resource Constraints:**
+- [Constraint 1]: [Description and mitigation plan]
+- [Constraint 2]: [Description and mitigation plan]
+
+---
+
+## Budget & Resources
+
+### Budget Summary
+| Category | Planned Budget | Contingency | Total Authorized |
+|----------|----------------|-------------|------------------|
+| Personnel | $[Amount] | $[Amount] | $[Amount] |
+| Software/Licenses | $[Amount] | $[Amount] | $[Amount] |
+| Hardware/Infrastructure | $[Amount] | $[Amount] | $[Amount] |
+| External Services | $[Amount] | $[Amount] | $[Amount] |
+| **Total** | **$[Total]** | **$[Total]** | **$[Total]** |
+
+### Resource Requirements
+| Role | FTE Required | Duration | Skills Required | Availability |
+|------|--------------|----------|----------------|--------------|
+| [Role] | [FTE] | [Months] | [Key Skills] | [Confirmed/TBD] |
+
+### Funding & Financial Management
+- **Funding Source:** [Department/Budget code]
+- **Budget Authority:** [Who can approve expenditures]
+- **Financial Reporting:** [Frequency and format of budget reports]
+- **Change Control:** [Process for budget change requests]
+
+---
+
+## Risk Management
+
+### High-Level Risk Assessment
+| Risk Category | Probability | Impact | Risk Score | Mitigation Strategy |
+|---------------|-------------|--------|------------|-------------------|
+| Technical | [H/M/L] | [H/M/L] | [1-25] | [High-level strategy] |
+| Resource | [H/M/L] | [H/M/L] | [1-25] | [High-level strategy] |
+| Schedule | [H/M/L] | [H/M/L] | [1-25] | [High-level strategy] |
+| Business | [H/M/L] | [H/M/L] | [1-25] | [High-level strategy] |
+
+### Top 5 Project Risks
+1. **[Risk Title]:** [Description, impact, probability, mitigation plan]
+2. **[Risk Title]:** [Description, impact, probability, mitigation plan]
+3. **[Risk Title]:** [Description, impact, probability, mitigation plan]
+4. **[Risk Title]:** [Description, impact, probability, mitigation plan]
+5. **[Risk Title]:** [Description, impact, probability, mitigation plan]
+
+### Risk Management Process
+- **Risk Identification:** [How risks will be identified and by whom]
+- **Risk Assessment:** [Methodology for probability/impact scoring]
+- **Risk Response:** [Strategies - avoid, mitigate, transfer, accept]
+- **Risk Monitoring:** [Review frequency and reporting process]
+
+---
+
+## Communication & Governance
+
+### Communication Plan
+| Audience | Information Needs | Format | Frequency | Owner |
+|----------|------------------|--------|-----------|-------|
+| Executive Sponsors | Status, risks, decisions needed | Dashboard + Meeting | Weekly | PM |
+| Steering Committee | Progress, issues, change requests | Report + Meeting | Bi-weekly | PM |
+| Project Team | Tasks, blockers, technical updates | Standup + Slack | Daily | Tech Lead |
+| Stakeholders | Feature progress, testing needs | Newsletter | Bi-weekly | PO |
+
+### Decision-Making Framework
+- **Decision Types:** [Operational, tactical, strategic classifications]
+- **Decision Rights:** [Who makes what decisions at what levels]
+- **Escalation Path:** [When and how to escalate decisions upward]
+- **Decision Log:** [How decisions will be recorded and communicated]
+
+### Change Control Process
+1. **Change Request:** [How changes are requested and documented]
+2. **Impact Assessment:** [Analysis of scope, time, cost, quality impacts]
+3. **Approval Authority:** [Who can approve different types/sizes of changes]
+4. **Implementation:** [How approved changes are implemented and communicated]
+
+---
+
+## Quality Management
+
+### Quality Standards & Requirements
+- **Technical Standards:** [Coding standards, security requirements, performance criteria]
+- **Business Standards:** [Acceptance criteria, usability requirements, accessibility]
+- **Process Standards:** [Development methodology, testing approach, documentation]
+
+### Quality Assurance Plan
+- **Code Reviews:** [Process, criteria, tools]
+- **Testing Strategy:** [Unit, integration, system, user acceptance testing]
+- **Quality Gates:** [Go/no-go criteria at each phase]
+- **Defect Management:** [Bug tracking, severity classification, resolution process]
+
+---
+
+## Assumptions & Constraints
+
+### Key Assumptions
+- [Assumption 1 about resources, technology, or business environment]
+- [Assumption 2 about stakeholder availability or external dependencies]
+- [Assumption 3 about market conditions or regulatory environment]
+
+### Project Constraints
+- **Time Constraints:** [Fixed deadlines, seasonal considerations]
+- **Budget Constraints:** [Funding limitations, cost restrictions]
+- **Resource Constraints:** [Team size limits, skill availability]
+- **Technical Constraints:** [System limitations, technology choices]
+- **Regulatory Constraints:** [Compliance requirements, approval processes]
+
+---
+
+## Approval & Sign-off
+
+### Charter Approval
+| Role | Name | Signature | Date |
+|------|------|-----------|------|
+| Executive Sponsor | [Name] | _________________ | [Date] |
+| Business Owner | [Name] | _________________ | [Date] |
+| Project Manager | [Name] | _________________ | [Date] |
+| Technical Owner | [Name] | _________________ | [Date] |
+
+### Project Authorization
+By signing this charter, the undersigned acknowledge they have reviewed and approve:
+- Project scope, objectives, and success criteria
+- Resource allocation and budget authorization
+- Timeline and milestone commitments
+- Risk acceptance and mitigation strategies
+- Communication and governance processes
+
+**Next Steps:**
+1. Distribute approved charter to all stakeholders
+2. Schedule project kick-off meeting
+3. Begin detailed planning and team formation
+4. Establish project tracking and reporting mechanisms
+
+---
+
+**Document Control:**
+- **Template Version:** 2.1
+- **Last Updated:** [Date]
+- **Next Review:** [Date]
+- **Document Owner:** Project Management Office

package/skills/senior-pm/assets/raci_matrix_template.md

@@ -0,0 +1,265 @@
+# RACI Matrix Template
+
+**Project:** [Project Name]  
+**Version:** [Version Number]  
+**Date:** [Creation/Update Date]  
+**Owner:** [Project Manager Name]
+
+---
+
+## RACI Matrix Legend
+
+| Code | Role | Description |
+|------|------|-------------|
+| **R** | **Responsible** | The person(s) who actually performs the work to complete the task |
+| **A** | **Accountable** | The person who is ultimately answerable for the correct completion |
+| **C** | **Consulted** | The person(s) whose opinions are sought and with whom there is two-way communication |
+| **I** | **Informed** | The person(s) who are kept up-to-date on progress, often only one-way communication |
+
+### RACI Best Practices
+- ✅ **One A per activity** - Only one person can be accountable for each task
+- ✅ **At least one R per activity** - Someone must be responsible for doing the work
+- ✅ **Minimize C's** - Too many consulted stakeholders can slow decision-making
+- ✅ **Strategic I's only** - Inform only those who truly need to know
+
+---
+
+## Stakeholder Roster
+
+### Core Project Team
+| Name | Role | Department | Contact | Availability |
+|------|------|------------|---------|--------------|
+| [Name] | Project Manager | PMO | [email] | 100% |
+| [Name] | Product Owner | Product | [email] | 75% |
+| [Name] | Technical Lead | Engineering | [email] | 90% |
+| [Name] | UX Designer | Design | [email] | 50% |
+| [Name] | QA Lead | Quality | [email] | 60% |
+
+### Executive Stakeholders
+| Name | Role | Department | Contact | Decision Authority |
+|------|------|------------|---------|-------------------|
+| [Name] | Executive Sponsor | [Department] | [email] | Budget & Strategic Direction |
+| [Name] | Business Owner | [Department] | [email] | Requirements & Acceptance |
+| [Name] | Technical Owner | [Department] | [email] | Architecture & Standards |
+
+### Extended Stakeholders
+| Name | Role | Department | Contact | Interest Level |
+|------|------|------------|---------|----------------|
+| [Name] | [Role] | [Department] | [email] | High/Medium/Low |
+| [Name] | [Role] | [Department] | [email] | High/Medium/Low |
+
+---
+
+## Project Phase RACI Matrices
+
+### Phase 1: Project Initiation & Planning
+
+| Activity | Project Manager | Executive Sponsor | Business Owner | Product Owner | Technical Lead |
+|----------|-----------------|-------------------|----------------|---------------|----------------|
+| **Business Case Development** | R | A | R | C | C |
+| **Project Charter Creation** | A, R | A | C | C | C |
+| **Stakeholder Analysis** | A, R | C | R | C | I |
+| **Initial Requirements Gathering** | A | I | R | R | C |
+| **High-Level Architecture** | A | I | C | C | R |
+| **Resource Planning** | A, R | A | C | C | C |
+| **Budget Approval** | R | A | C | I | I |
+| **Risk Assessment** | A, R | C | C | C | R |
+| **Project Charter Sign-off** | R | A | A | C | C |
+
+### Phase 2: Design & Development Setup
+
+| Activity | Project Manager | Product Owner | Technical Lead | UX Designer | QA Lead |
+|----------|-----------------|---------------|----------------|-------------|---------|
+| **Requirements Documentation** | A | R | C | C | C |
+| **Technical Architecture** | A | C | R | I | C |
+| **System Design Documentation** | A | C | R | C | C |
+| **UI/UX Design** | A | R | C | R | I |
+| **Database Design** | A | I | R | I | C |
+| **API Specifications** | A | C | R | I | C |
+| **Test Strategy** | A | C | C | I | R |
+| **Development Environment Setup** | A | I | R | I | C |
+| **CI/CD Pipeline Setup** | A | I | R | I | R |
+
+### Phase 3: Development & Implementation
+
+| Activity | Project Manager | Product Owner | Technical Lead | Dev Team | QA Lead |
+|----------|-----------------|---------------|----------------|----------|---------|
+| **Sprint Planning** | R | A | R | R | C |
+| **User Story Development** | A | R | C | C | C |
+| **Code Development** | A | C | R | R | I |
+| **Code Reviews** | I | I | A | R | I |
+| **Unit Testing** | I | I | R | R | C |
+| **Integration Testing** | A | C | R | R | R |
+| **Feature Testing** | A | R | C | I | R |
+| **Bug Triage** | R | A | R | R | R |
+| **Sprint Reviews** | A, R | R | R | R | R |
+
+### Phase 4: Testing & Quality Assurance
+
+| Activity | Project Manager | Product Owner | Technical Lead | QA Lead | Business Owner |
+|----------|-----------------|---------------|----------------|---------|----------------|
+| **Test Plan Creation** | A | C | C | R | C |
+| **System Testing** | A | C | C | R | I |
+| **Performance Testing** | A | C | R | R | I |
+| **Security Testing** | A | I | R | R | I |
+| **User Acceptance Testing** | A | R | C | C | R |
+| **Bug Resolution** | A | C | R | R | I |
+| **Go-Live Readiness** | A | R | R | R | R |
+| **Sign-off Documentation** | R | R | C | R | A |
+
+### Phase 5: Deployment & Launch
+
+| Activity | Project Manager | Technical Lead | DevOps | Business Owner | Support Team |
+|----------|-----------------|----------------|--------|----------------|--------------|
+| **Deployment Planning** | A | R | R | C | C |
+| **Production Deployment** | A | R | R | I | I |
+| **Smoke Testing** | A | R | C | C | R |
+| **Go-Live Communication** | R | C | I | A | I |
+| **User Training** | A | C | I | R | C |
+| **Support Documentation** | A | C | C | C | R |
+| **Monitoring Setup** | A | R | R | I | R |
+| **Launch Retrospective** | A, R | R | C | R | C |
+
+---
+
+## Decision-Making RACI
+
+### Strategic Decisions
+| Decision Type | Project Manager | Executive Sponsor | Business Owner | Technical Owner |
+|---------------|-----------------|-------------------|----------------|-----------------|
+| **Budget Changes >10%** | R | A | C | C |
+| **Scope Changes (Major)** | R | A | R | C |
+| **Timeline Changes >2 weeks** | R | A | R | C |
+| **Technology Platform Changes** | R | C | C | A |
+| **Resource Reallocation** | A, R | A | C | C |
+| **Go/No-Go Decisions** | R | A | R | R |
+
+### Operational Decisions
+| Decision Type | Project Manager | Product Owner | Technical Lead | Team Members |
+|---------------|-----------------|---------------|----------------|--------------|
+| **Sprint Scope** | C | A | R | R |
+| **Technical Implementation** | C | C | A, R | R |
+| **Bug Priority** | A | R | C | C |
+| **Code Standards** | C | C | A, R | R |
+| **Testing Approach** | A | C | R | R |
+| **Daily Task Assignment** | I | C | A | R |
+
+---
+
+## Escalation Paths & Conflict Resolution
+
+### Escalation Matrix
+| Issue Level | Primary Resolver | Escalation To | Timeline | Authority |
+|-------------|------------------|---------------|----------|-----------|
+| **Level 1: Task/Technical** | Team Member → Technical Lead | Product Owner | 24 hours | Technical decisions |
+| **Level 2: Sprint/Feature** | Technical Lead → Product Owner | Project Manager | 48 hours | Feature scope/priority |
+| **Level 3: Project Impact** | Project Manager → Business Owner | Executive Sponsor | 72 hours | Budget/timeline changes |
+| **Level 4: Strategic** | Executive Sponsor → Steering Committee | CEO/Board | 1 week | Strategic direction |
+
+### Conflict Resolution Process
+1. **Direct Resolution** (Level 1)
+   - **Who:** Conflicting parties attempt direct resolution
+   - **Timeline:** 24 hours
+   - **Documentation:** Brief note in project log
+
+2. **Mediated Resolution** (Level 2)  
+   - **Who:** Project Manager facilitates discussion
+   - **Timeline:** 48 hours from escalation
+   - **Documentation:** Decision recorded with rationale
+
+3. **Executive Resolution** (Level 3)
+   - **Who:** Executive Sponsor makes binding decision
+   - **Timeline:** 72 hours from escalation  
+   - **Documentation:** Formal decision memo to all stakeholders
+
+4. **Steering Committee** (Level 4)
+   - **Who:** Full steering committee vote
+   - **Timeline:** Next scheduled meeting (max 1 week)
+   - **Documentation:** Board resolution or meeting minutes
+
+### Communication Protocols
+- **Escalation Notification:** All RACI stakeholders informed within 4 hours
+- **Decision Communication:** Decision communicated to all affected parties within 24 hours
+- **Documentation:** All escalations and resolutions logged in project management system
+
+---
+
+## Communication & Meeting RACI
+
+### Regular Meetings
+| Meeting Type | Frequency | Project Manager | Team | Stakeholders | Sponsor |
+|-------------|-----------|-----------------|------|--------------|---------|
+| **Daily Standup** | Daily | A | R | I | I |
+| **Sprint Planning** | Bi-weekly | A | R | C | I |
+| **Sprint Review** | Bi-weekly | R | R | A | C |
+| **Stakeholder Updates** | Weekly | A, R | C | R | A |
+| **Steering Committee** | Monthly | R | I | C | A |
+
+### Communication Artifacts
+| Artifact | Creator (R) | Approver (A) | Reviewers (C) | Recipients (I) |
+|----------|-------------|-------------|---------------|----------------|
+| **Status Reports** | Project Manager | Business Owner | Team Leads | All Stakeholders |
+| **Risk Register** | Project Manager | Executive Sponsor | Risk Owners | Steering Committee |
+| **Change Requests** | Requestor | Business Owner | Project Manager | Affected Teams |
+| **Decision Log** | Project Manager | Decision Maker | Consulted Parties | All Stakeholders |
+
+---
+
+## Risk & Issue Management RACI
+
+### Risk Management
+| Activity | Project Manager | Risk Owner | Executive Sponsor | Team |
+|----------|-----------------|------------|-------------------|------|
+| **Risk Identification** | A | R | C | R |
+| **Risk Assessment** | A | R | C | C |
+| **Mitigation Planning** | A | R | C | R |
+| **Risk Monitoring** | A | R | I | C |
+| **Risk Escalation** | R | R | A | I |
+
+### Issue Resolution
+| Issue Severity | Reporter (R) | Owner (A) | Resolver (R) | Informed (I) |
+|----------------|-------------|-----------|-------------|-------------|
+| **Critical** | Anyone | Project Manager | Technical Lead | Executive Sponsor |
+| **High** | Team/Stakeholder | Technical Lead | Team Member | Project Manager |
+| **Medium** | Team Member | Team Lead | Team Member | Project Manager |
+| **Low** | Team Member | Team Member | Team Member | Team Lead |
+
+---
+
+## RACI Validation & Maintenance
+
+### Validation Checklist
+- [ ] Every activity has exactly one "A" (Accountable)
+- [ ] Every activity has at least one "R" (Responsible) 
+- [ ] "C" (Consulted) roles are minimized to essential stakeholders
+- [ ] "I" (Informed) includes only those who truly need updates
+- [ ] No person is assigned "A" for more tasks than they can handle
+- [ ] Escalation paths are clear and realistic
+- [ ] Decision rights match organizational authority
+
+### Review & Update Process
+- **Review Frequency:** Every project phase or monthly
+- **Update Triggers:** Team changes, scope changes, organizational changes
+- **Approval Process:** Changes require Project Manager and Executive Sponsor approval
+- **Communication:** RACI updates communicated to all stakeholders within 48 hours
+
+### RACI Health Metrics
+| Metric | Target | Current | Notes |
+|--------|---------|---------|-------|
+| **Decision Speed** | <48 hours | [X] hours | Average time for routine decisions |
+| **Escalation Rate** | <10% | [X]% | Percentage of issues requiring escalation |
+| **Role Clarity** | >90% | [X]% | Stakeholder survey on role understanding |
+| **Conflict Resolution** | <72 hours | [X] hours | Average resolution time |
+
+---
+
+**Document Control:**
+- **Version:** [Version Number]
+- **Last Updated:** [Date]
+- **Next Review:** [Date]  
+- **Approved By:** [Executive Sponsor Name]
+
+**Distribution List:**
+- All Project Stakeholders (as identified in roster)
+- PMO (for template compliance)
+- HR (for role clarity and performance management)