project-assessmentlisted

# Project Assessment (WHAT) Use this skill when the user asks for a project assessment, maturity assessment, delivery audit, technical assessment, management assessment, quality indicator review, or improvement roadmap. This is a router skill. Keep it focused on assessment flow, gates, and delegation. Use the unit-specific skills for scoring details. ## Default guardrails 1. Apply **`output-handshake`** before producing any final assessment report, scorecard, action plan, or executive summary: ask where the artifact should live and confirm human review. 2. Apply **`project-assessment-evidence`** before scoring. Evidence may live in repositories, boards, docs, spreadsheets, dashboards, incidents, PRs, meetings, interviews, Slack, emails, or any other project system. Ask the user where to find each source. 3. Never assign a score without evidence. If evidence is missing, mark the indicator as **Not assessed** or score it with **Low confidence** and state the assumption explicitly. 4. Keep sensitive details out of reusable artifacts. Redact secrets, credentials, private customer data, and unnecessary personal data. 5. Do not mention client-specific reference examples or internal audit links in generated outputs. Use only abstracted patterns. ## Assessment flow 1. **Intake** - Ask the assessment purpose: baseline, periodic review, due diligence, quality improvement, delivery health check, AI-readiness review, or internal audit support. - Ask the assessment period and