Skill: Value Stream and Constraint Analysis

Capability Domain: Process Engineering
Technology Stack: Theory of Constraints, DevOps Three Ways

Recipe

1. Read Scope Contract views. Anchor the five stages to those events, not a hardcoded GitLab/Jira set.
2. GitHub-org default join key: issue number / PR number / project item content (never timestamp proximity).
   - Biz: github_issues opened (Projects v2 github_project_items only after the GraphQL poller is real).
   - Dev: github_pull_requests opened → merged; commits in window.
   - Test: github_workflow_runs start → first conclusion=success.
   - Sec: security-gate job inside that run, or a dedicated scan workflow.
   - Ops: deploy github_workflow_runs start → complete.
3. If gitlab/jira views exist in the contract, use those events instead/in addition — do not invent joins across sources without an explicit key.
4. Feature-type issues (cycle-time cohort), not "every GitHub issue":
   - Include: labels feature, enhancement, status-done; titles W\d+:, DIAGRAM W\d+:, [area:tool], BPE-\d+ / MIN-\d+ / DSP-\d+ / DTA-\d+, scenario LOG1.1:.
   - Exclude: plain bug with none of those signals.
   - Classify in Python after Athena returns rows.
5. Hand off ranking to skill Cycle Impact Scoring (people×touch + downstream×wait). This skill maps stages; it does not rank by p90 alone.

Pitfalls

• Joining on timestamp proximity or on repo only.
• Ranking with GitLab pipeline data when the lake only has GitHub views.
• Empty cycle time because backfill used default state=open.