← Aivana CIO Decision TwinCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Aivana CIO Decision Twin
Snapshot Sep 30, 2026 · 23:16 UTC · version 0.1.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "project-portfolio-intelligence",
"description": "Assess project and portfolio health, including status, schedule, budget, milestones, resources, dependencies, risk and prioritization. Use for PMO reviews, steering committee preparation and portfolio decisions. Use when the user needs project portfolio intelligence for CIO decision support.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 146
}
],
"skill_md_contents": "---\nname: project-portfolio-intelligence\ndescription: Assess project and portfolio health, including status, schedule, budget, milestones, resources, dependencies, risk and prioritization. Use for PMO reviews, steering committee preparation and portfolio decisions. Use when the user needs project portfolio intelligence for CIO decision support.\n---\n\n# Project Portfolio Intelligence\n\n## Mission\n\nApply the [shared decision contract](../autonomous-cio-orchestrator/references/decision-contract.md)\nfor source-bound trade-offs, immutable claim IDs, scoring limits, and a concise first page.\n\nTurn project fragments into a portfolio-level view of delivery confidence, risk concentration, critical decisions and prioritization.\n\n## Inputs\n\nAccept project lists, status reports, milestone tables, RAID logs, budget notes, staffing plans, dependency registers, steering notes, backlog summaries and delivery KPIs.\n\n## Workflow\n\n1. Normalize projects by objective, owner, status, timeline, budget, resources, milestones and dependencies.\n2. Detect schedule risk, budget risk, scope drift, resource bottlenecks and unresolved decisions.\n3. Identify cross-project dependencies, duplicated work, sequencing conflicts and single points of failure.\n4. Score each project as Green, Amber or Red using evidence, urgency, impact and confidence.\n5. Recommend stop, continue, accelerate, re-scope or escalate actions where justified.\n6. Build a portfolio narrative for PMO and executive steering.\n\n## Output Format\n\n- Executive Summary\n- Portfolio Health\n- Red / Amber / Green Project Table\n- Critical Milestones\n- Budget & Resource Risks\n- Cross-Project Dependencies\n- Prioritization Recommendations\n- Decisions Needed\n- Evidence & Assumptions\n- Missing Data\n- Next 24h / 7d / 30d Actions\n\n## Guardrails\n\nDo not fabricate project metrics. If dates, budgets or owners are missing, mark the assessment as lower confidence.\n"
}SHA-256: 3cd4e4e0c91896600af838adae1d63dc71c86d971209e7b609e959c436f6e661