assess

Produce a numbered findings assessment with evidence-backed observations and file references.

1|Updated Apr 11, 2026

Search Tags:#codebase #evidence #assessment #investigate #phase-based #findings

Ready to run

npx skills add https://github.com/bkudria/cc-plugins --skill assess-bkudria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: assess
Source: https://github.com/bkudria/cc-plugins/tree/main/plugins/triage/skills/assess
Command: npx skills add https://github.com/bkudria/cc-plugins --skill assess-bkudria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate a scope for problems and opportunities and produce a structured, numbered findings assessment that can be consumed by other skills such as iterate.

Core Features & Use Cases

Structured findings: generate a numbered list of observations that describe problems and opportunities with concrete evidence.
Phase-driven workflow: follows Scope Resolution, Scope Interview (fallback), Exploration Planning, Investigation, and Synthesis to organize work.
Evidence-backed reporting: each finding includes file paths, line numbers, or explicit values to support conclusions. Use cases include analyzing a codebase, auditing configuration, reviewing a feature, or documenting findings for future action via /iterate.

Quick Start

Run a scope assessment on the provided project and generate a numbered findings report.

Frequently Asked Questions about assess

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate a codebase for problems and generate an evidence-backed assessment?▼

To investigate a codebase, run a structured assessment that follows a phase-driven workflow of scope resolution, planning, investigation, and synthesis to produce numbered findings with concrete file references.

What is a phase-based codebase investigation and when do I need it?▼

A phase-based codebase investigation is a structured process that resolves scope, plans exploration, investigates evidence, and synthesizes findings. You need it when auditing configurations or reviewing features to produce actionable, evidence-backed reports.

How do I structure code review findings with concrete file references?▼

To structure code review findings, use a numbered assessment format where each observation includes explicit evidence such as file paths, line numbers, or explicit values to support conclusions for later action.

Can I use a structured findings assessment for configuration audits and feature reviews?▼

Yes, you can use a structured findings assessment for configuration audits and feature reviews because it applies to any defined scope, generating evidence-backed observations that describe problems and opportunities for future action.

What's the best way to document codebase problems for future iteration?▼

The best way to document codebase problems for future iteration is generating a numbered findings assessment with concrete file references, which can be directly consumed by downstream skills to act upon the evidence-backed observations.

What happens if scope resolution fails during a codebase assessment?▼

If scope resolution fails during a codebase assessment, the workflow falls back to a scope interview phase to gather the necessary boundaries and context before proceeding to exploration planning and investigation.