project-assessment-evidencelisted

# Project Assessment Evidence (WHAT) Use this skill before scoring a project assessment. It turns scattered project knowledge into a structured evidence map. This skill is intentionally interactive. Evidence can be outside ClickUp and outside the repository. Ask for source locations instead of assuming where they live. ## Default behavior 1. Ask the user for the systems of record and evidence locations. 2. Collect source links, paths, owners, dates, and freshness for each evidence item. 3. Mark evidence quality: Direct, Indirect, Interview-only, Stale, Missing, or Not applicable. 4. Record confidence for each evidence item: High, Medium, Low, or Not assessed. 5. Do not score indicators. Return the evidence map to **`project-assessment`**, **`technical-unit-assessment`**, or **`management-unit-assessment`**. ## Evidence intake questions Ask only the questions relevant to the assessment scope, but cover each required source class before scoring. ### Scope and systems - What project, product, platform, squad, or delivery scope is being assessed? - What period should evidence cover? - What are the official systems of record? - Which sources should be considered authoritative when sources conflict? ### Delivery and management evidence - Where is the project board or backlog? - Where are epics, stories, tasks, bugs, incidents, and subtasks tracked? - Where are sprint plans, delivery reports, retrospectives, risks, and OIRs? - Where are PRDs, TRDs, ADRs, decisions, agreeme