scan

Analyze a codebase to generate architecture, requirements, and test plan documents.

11|Updated Feb 18, 2026

Search Tags:#architecture #documentation #codebase #requirements #test plan #scan

Ready to run

npx skills add https://github.com/pillip/claude-dev-kit --skill scan-pillip

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scan
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/scan
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill scan-pillip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze an existing codebase and generate context documents (architecture, requirements, and test plan) for downstream skills.

Core Features & Use Cases

Generates standalone context artifacts that guide downstream skill execution.
Produces documents aligned with sprint workflows (PRD digest, requirements, architecture, test plans, and issues).
Supports parallel subagents to accelerate discovery and planning.

Quick Start

Run the scan workflow on your project root to generate architecture, requirements, and test-plan context documents.

Frequently Asked Questions about scan

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

FAQPage Schema

How do I generate architecture and requirements documentation from an existing codebase?▼

To generate architecture and requirements documentation from an existing codebase, you can run a scan workflow on your project root to analyze the code and produce structured context documents like PRD digests and test plans.

What is the best way to create a test plan from source code for downstream workflows?▼

Creating a test plan from source code for downstream workflows involves analyzing the codebase to extract structured context artifacts, automatically producing a test plan document that aligns with sprint execution and quality checks.

Can I use codebase scanning to generate documentation for projects of varying sizes and configurations?▼

Yes, codebase scanning targets projects of varying sizes and configurations, generating architecture, requirements, and test plan documents with clear sources and confidence tagging to support different project structures.

How does codebase analysis handle discovery and planning for large repositories?▼

Codebase analysis handles discovery and planning for large repositories by supporting parallel subagents, which accelerate the scanning process to quickly produce the required architecture and requirements artifacts.

What specific context artifacts are produced when turning a codebase into documentation?▼

Turning a codebase into documentation produces specific context artifacts including prd_digest.md, requirements.md, architecture.md, test_plan.md, issues.md, and STATUS.md to guide downstream skill execution.

Does the generated architecture documentation include confidence tagging for downstream skills?▼

Yes, the generated architecture documentation includes clear sources and confidence tagging, ensuring downstream skills have verified context artifacts for sprint workflows and quality checks.