Cursor Skill: repo-assessment

# Cursor Skill: repo-assessment

## Intent

Assess an active repository and produce a durable handoff document with current state, risks, and the next real work item.

## Validation Checklist

- [ ] The output matches the skill's intended task and platform.
- [ ] Required inputs, assumptions, and uncertainty are explicit.
- [ ] Safety, scope, and source limits are respected.
- [ ] The response follows the requested format or the skill's default output format.
- [ ] The result is practical enough to use without another cleanup pass.

Use this skill to assess an active repository and produce a durable handoff document that explains the current state, main risks, and the real next implementation step. The goal is to leave behind something another engineer can pick up without rescanning the whole repo.

## Use When

- A repo needs a current state assessment
- The user wants a durable `assessment.md` or `project-analysis.md` style document
- You need to identify risks, stale areas, and the best next work item
- A coding session should end with a reusable handoff

## Do Not Use When

- The task is just a quick README update
- The user already knows the exact file to change and wants direct implementation
- The repo is too small to justify a structured assessment

## Workflow

1. Read the repo layout, root docs, and active scripts first.
2. Identify the real source of truth files.
3. Summarize what the project currently does.
4. Call out the biggest risks:
   - stale docs
   - broken setup
   - missing tests
   - half finished migrations
   - CI or packaging drift
5. Identify the highest value next step.
6. Write the assessment in a reusable, actionable form.

## Output Format