claude-mpm 5.4.55__py3-none-any.whl → 5.4.85__py3-none-any.whl

claude_mpm/skills/bundled/pm/pm-ticketing-integration/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: pm-ticketing-integration
+version: "1.0.0"
+description: Ticket-driven development protocol
+when_to_use: ticket IDs mentioned, issue URLs, work tracking
+category: pm-workflow
+tags: [tickets, integration, workflow, pm-required]
+---
+
+# Ticketing Integration Protocol
+
+## Detection Rules
+
+PM detects ticket context from:
+- Ticket ID patterns: `PROJ-123`, `#123`, `MPM-456`, `JJF-62`
+- Ticket URLs: `github.com/.../issues/123`, `linear.app/.../issue/XXX`
+- Explicit references: "work on ticket", "implement issue", "fix bug #123"
+- Session start context (first user message with ticket reference)
+
+## CRITICAL ENFORCEMENT
+
+**PM MUST NEVER use these tools directly - ALWAYS delegate to ticketing agent:**
+
+- ❌ PM using WebFetch on ticket URLs → Delegate to ticketing
+- ❌ PM using `mcp__mcp-ticketer__*` tools → Delegate to ticketing
+- ❌ PM using ANY tools to access tickets → ONLY delegate to ticketing agent
+
+**Delegation Rule**: ALL ticket operations must be delegated to ticketing agent.
+
+## TICKET-DRIVEN DEVELOPMENT PROTOCOL (TkDD)
+
+**When ticket detected** (PROJ-123, #123, ticket URLs, "work on ticket"):
+
+### PM MUST Execute This Workflow
+
+**1. Work Start** → Delegate to ticketing:
+```
+Task:
+  agent: "ticketing"
+  task: "Start work on ticket {ticket_id}"
+  acceptance_criteria:
+    - Transition ticket to 'in_progress'
+    - Add comment: "Work started by Claude MPM"
+    - Confirm state change
+```
+
+**2. Each Phase** → Comment with deliverables:
+```
+Task:
+  agent: "ticketing"
+  task: "Update ticket {ticket_id} with progress"
+  context: |
+    Phase completed: {phase_name}
+    Deliverables: {deliverable_summary}
+  acceptance_criteria:
+    - Add comment with phase completion details
+    - Include links to commits/PRs if applicable
+```
+
+**3. Work Complete** → Transition to done/closed:
+```
+Task:
+  agent: "ticketing"
+  task: "Complete ticket {ticket_id}"
+  context: |
+    Work summary: {summary}
+    QA verification: {qa_evidence}
+    Files changed: {file_list}
+  acceptance_criteria:
+    - Transition to 'done' or 'closed'
+    - Add comprehensive completion comment
+    - Link PR if created
+```
+
+**4. Blockers** → Comment blocker details:
+```
+Task:
+  agent: "ticketing"
+  task: "Report blocker on ticket {ticket_id}"
+  context: |
+    Blocker: {blocker_description}
+    Impact: {impact}
+    Waiting on: {dependency}
+  acceptance_criteria:
+    - Update ticket state to 'blocked'
+    - Add blocker details in comment
+    - Notify relevant stakeholders if applicable
+```
+
+## Documentation Routing with Ticket Context
+
+### When Ticket Context Provided
+
+When user starts session with ticket reference:
+- PM delegates to ticketing agent to attach work products
+- Research findings → Attached as comments to ticket
+- Specifications → Attached as files or formatted comments
+- Still create local docs as backup in `{docs_path}/`
+- All agent delegations include ticket context
+
+### When NO Ticket Context
+
+- All documentation goes to `{docs_path}/` (default: `docs/research/`)
+- No ticket attachment operations
+- Named with pattern: `{topic}-{date}.md`
+
+## Ticket Context Propagation
+
+When ticket is detected, PM includes ticket context in all delegations:
+
+```
+Task:
+  agent: "{any_agent}"
+  task: "{task_description}"
+  context: |
+    Ticket: {ticket_id}
+    Ticket summary: {summary_from_ticketing_agent}
+    {other_context}
+  acceptance_criteria:
+    {criteria}
+```
+
+This ensures all agents know work is ticket-driven and can reference it.
+
+## Example TkDD Workflow
+
+```
+User: "Work on ticket PROJ-123"
+    ↓
+PM delegates to ticketing: Get ticket details
+    ↓
+PM delegates to ticketing: Transition to 'in_progress', comment "Work started"
+    ↓
+PM delegates to research: Investigate approach (with ticket context)
+    ↓
+PM delegates to ticketing: Comment "Research phase complete: {findings}"
+    ↓
+PM delegates to engineer: Implement feature (with ticket context)
+    ↓
+PM delegates to ticketing: Comment "Implementation complete: {files}"
+    ↓
+PM delegates to QA: Verify implementation
+    ↓
+PM delegates to ticketing: Transition to 'done', comment "Work complete: {summary}"
+```
+
+## Violation Prevention
+
+**Circuit Breaker**: PM using ticket tools directly triggers:
+- Violation #1: ⚠️ WARNING - Must delegate immediately
+- Violation #2: 🚨 ESCALATION - Session flagged for review
+- Violation #3: ❌ FAILURE - Session non-compliant
+
+This enforcement ensures PM maintains pure coordination role.

claude_mpm/skills/bundled/pm/pm-verification-protocols/SKILL.md

@@ -0,0 +1,198 @@
+---
+name: pm-verification-protocols
+version: "1.0.0"
+description: QA verification gate and evidence requirements
+when_to_use: verification needed, QA delegation, evidence collection
+category: pm-workflow
+tags: [qa, verification, evidence, pm-required]
+---
+
+# QA Verification Gate Protocol
+
+## 🔴 MANDATORY QA VERIFICATION GATE
+
+**CRITICAL**: PM MUST delegate to QA BEFORE claiming work complete. NO completion claim without QA verification evidence.
+
+### When QA Gate Applies
+
+ALL implementation work:
+- UI features
+- Local server UI
+- API endpoints
+- Bug fixes
+- Full-stack features
+- Test modifications
+
+### QA Gate Enforcement
+
+**BLOCKING**: PM CANNOT claim "done/complete/ready/working/fixed" without QA evidence
+
+**CORRECT SEQUENCE**:
+```
+Implementation
+  → PM delegates to QA
+  → PM WAITS for evidence
+  → PM reports WITH QA verification
+```
+
+## Verification Requirements by Work Type
+
+| Work Type | QA Agent | Required Evidence | Forbidden Claim |
+|-----------|----------|-------------------|-----------------|
+| **Local Server UI** | web-qa | Chrome DevTools MCP (navigate, snapshot, screenshot, console) | "Page loads correctly" |
+| **Deployed Web UI** | web-qa | Playwright/Chrome DevTools (screenshots + console logs) | "UI works" |
+| **API/Server** | api-qa | HTTP responses + logs | "API deployed" |
+| **Database** | data-engineer | Schema queries + data samples | "DB ready" |
+| **Local Backend** | local-ops | lsof + curl + pm2 status | "Running on localhost" |
+| **CLI Tools** | Engineer/Ops | Command output + exit codes | "Tool installed" |
+
+## Forbidden Phrases (CIRCUIT BREAKER VIOLATION)
+
+**❌ NEVER say these without QA evidence:**
+- "production-ready"
+- "page loads correctly"
+- "UI is working"
+- "should work"
+- "looks good"
+- "seems fine"
+- "it works"
+- "all set"
+- "ready for users"
+- "deployment successful"
+
+**✅ ALWAYS say this instead:**
+```
+"[Agent] verified with [tool/method]: [specific evidence]"
+```
+
+## Evidence Quality Standards
+
+### Good Evidence
+
+**Specific details**:
+- File paths and line numbers
+- URLs and endpoints tested
+- HTTP status codes
+- Test counts and pass/fail results
+- Console log excerpts
+- Screenshots with annotations
+
+**Measurable outcomes**:
+- "12 tests passed, 0 failed"
+- "HTTP 200 OK response"
+- "Server listening on port 3000"
+- "No console errors found"
+
+**Agent attribution**:
+- "web-qa verified with Playwright"
+- "api-qa tested endpoints"
+- "local-ops confirmed process running"
+
+**Reproducible steps**:
+- "Navigate to /login, enter credentials, click submit"
+- "curl http://localhost:3000/api/health"
+- "lsof -i :3000 shows node process"
+
+### Insufficient Evidence (VIOLATIONS)
+
+**Vague claims**:
+- "works"
+- "looks good"
+- "should be fine"
+
+**No measurements**:
+- "deployed successfully" (without health check)
+- "UI updated" (without verification)
+
+**PM assessment**:
+- PM saying "I checked and it works"
+- PM making claims without delegation
+
+**Not reproducible**:
+- "tested it" (no steps)
+- "verified" (no method)
+
+## Required Evidence by Claim Type
+
+| Claim Type | Required Evidence | Example |
+|------------|------------------|---------|
+| **Implementation Complete** | • Engineer confirmation<br>• Files changed (paths)<br>• Git commit (hash/branch)<br>• Summary | `Engineer: Added OAuth2 auth. Files: src/auth/oauth2.js (new, 245 lines), src/routes/auth.js (+87). Commit: abc123.` |
+| **Deployed Successfully** | • Ops confirmation<br>• Live URL<br>• Health check (HTTP status)<br>• Deployment logs<br>• Process status | `Ops: Deployed to https://app.example.com. Health: HTTP 200. Logs: Server listening on :3000. Process: lsof shows node listening.` |
+| **Bug Fixed** | • QA bug reproduction (before)<br>• Engineer fix (files changed)<br>• QA verification (after)<br>• Regression tests | `QA: Bug reproduced (HTTP 401). Engineer: Fixed session.js (+12-8). QA: Now HTTP 200, 24 tests passed.` |
+
+## Browser State Verification (MANDATORY)
+
+**CRITICAL RULE**: PM MUST NOT assert browser/UI state without Chrome DevTools MCP evidence.
+
+When verifying local server UI or browser state, PM MUST:
+1. Delegate to web-qa agent
+2. web-qa MUST use Chrome DevTools MCP tools (NOT assumptions)
+3. Collect actual evidence (snapshots, screenshots, console logs)
+
+### Chrome DevTools MCP Tools (via web-qa only)
+
+Available tools:
+- `mcp__chrome-devtools__navigate_page` - Navigate to URL
+- `mcp__chrome-devtools__take_snapshot` - Get page content/DOM state
+- `mcp__chrome-devtools__take_screenshot` - Visual verification
+- `mcp__chrome-devtools__list_console_messages` - Check for errors
+- `mcp__chrome-devtools__list_network_requests` - Verify API calls
+
+### Required Evidence for UI Verification
+
+✅ **CORRECT**: web-qa verified with Chrome DevTools:
+```
+- navigate_page: http://localhost:3000 → HTTP 200
+- take_snapshot: Page shows login form with email/password fields
+- take_screenshot: [screenshot shows rendered UI]
+- list_console_messages: No errors found
+- list_network_requests: GET /api/config → 200 OK
+```
+
+❌ **WRONG**: "The page loads correctly at localhost:3000"
+(No Chrome DevTools evidence - CIRCUIT BREAKER VIOLATION)
+
+### Local Server UI Verification Template
+
+```
+Task:
+  agent: "web-qa"
+  task: "Verify local server UI at http://localhost:3000"
+  acceptance_criteria:
+    - Navigate to page (mcp__chrome-devtools__navigate_page)
+    - Take page snapshot (mcp__chrome-devtools__take_snapshot)
+    - Take screenshot (mcp__chrome-devtools__take_screenshot)
+    - Check console for errors (mcp__chrome-devtools__list_console_messages)
+    - Verify network requests (mcp__chrome-devtools__list_network_requests)
+```
+
+## Example Good Report
+
+```
+Work complete: User authentication feature implemented
+
+Implementation: Engineer added OAuth2 authentication using Auth0.
+Changed files: src/auth.js, src/routes/auth.js, src/middleware/session.js
+Commit: abc123
+
+Deployment: Ops deployed to https://app.example.com
+Health check: HTTP 200 OK, Server logs show successful startup
+
+Testing: QA verified end-to-end authentication flow
+- Login with email/password: PASSED
+- OAuth2 token management: PASSED
+- Session persistence: PASSED
+- Logout functionality: PASSED
+
+All acceptance criteria met. Feature is ready for users.
+```
+
+## Circuit Breaker Enforcement
+
+**Circuit Breaker #8**: QA Verification Gate
+- **Trigger**: PM claims completion without QA delegation
+- **Action**: BLOCK - Delegate to QA now
+- **Enforcement Levels**:
+  - Violation #1: ⚠️ WARNING - Must delegate immediately
+  - Violation #2: 🚨 ESCALATION - Session flagged for review
+  - Violation #3: ❌ FAILURE - Session non-compliant