Add project-intelligence plugin — process-based project analysis

[dutchdutchdutch]

Summary

Adds a new project-intelligence plugin that surfaces patterns in any team's work — code, documents, designs, or compliance artifacts. While existing plugins are role-based (coaching PMs, legal, finance on how to do their job), project-intelligence is process-based — it observes what's actually happening and answers: "What's the state of this project right now?"

Designed to supplement, not duplicate existing role plugins. Skills that overlapped with existing plugins were removed or slimmed down (DRY).

What's included

8 input skills (modular collectors):

Skill	What It Does
story-flow	Diagnoses why stories exceed cycle time targets
quality-check	Domain-agnostic quality gate checking
activity-audit	Compares reported status against actual activity
risk-tracker	Detects risk patterns: recurrence, cascades, accumulation
schedule-forecast	Quantitative completion forecasting with confidence bands
dependency-readiness	Staleness-first dependency verification
stakeholder-signoff	Approval tracking with enablement verification
change-summary	Iteration summaries and review deltas (feedback loop closure)

2 aggregator skills (synthesis):

Skill	What It Does
release-readiness	Cross-skill go/no-go synthesis with traffic lights
sprint-retro-input	Comparative retrospective analysis with evidence

2 agents (delegated signal detection):

Agent	Purpose
git-activity	Commit pattern detection for activity-audit
document-activity	Document revision pattern detection (template)

Relationship to existing plugins

Project Intelligence Skill	Related Role Plugin	How They Differ
stakeholder-signoff	stakeholder-comms	Comms teaches how to communicate; signoff checks if it was effective
risk-tracker	legal-risk-assessment	Legal uses severity/likelihood scoring; this detects emerging patterns
change-summary	roadmap-management	Role plugins generate release notes; this tracks what changed since your last review
schedule-forecast	roadmap-management	Roadmap is strategic; this is mathematical

Design principles

• Domain-agnostic — Examples span software, legal, creative, compliance, hardware, marketing
• Artifact-driven — Reads actual work products, not self-reported status
• Composable — Input skills work standalone or feed into aggregators
• Tool-agnostic — Uses ~~connector placeholders, graceful fallback to manual input
• DRY — Explicitly defers to role plugins where they already cover a capability