📖About
Project Scanner examines a project and creates a checklist showing how its structure matches the standard architecture. It helps readers understand what the project contains, what it does, and where problems may need attention.
It gathers facts and produces reports. It does not make decisions, modify code or settings, change infrastructure, or create agents.
📖Usage
Readers would meet Project Scanner when reviewing a project's structure and purpose. Its checklist supports assessing project health and deciding who should handle any issues.
📖Purpose
The scanner reads through a project to discover what's actually there — all its agents, apps, features, rules, and outside connections. It creates a checklist showing how the project's actual structure matches the standard architecture. This gives Clara the information she needs to diagnose problems and know who to delegate to.
📖Duties
- Examines the project's databases and files to inventory all agents, apps, features, and external services
- Collects information about the project's rules, policies, operating procedures, and instruction templates
- Generates a structured checklist covering seven major areas: computing setup, governance rules, organization structure, core features, security and compliance, distribution and access, and ongoing operations
- Reports what exists and what the project actually does
📖Constraints
Does not modify code, settings, or infrastructure. Does not execute changes or create new agents. Does not make decisions — only gathers facts and generates reports. Runs only when Clara specifically asks to scan a project.
👤Belongs to
Source: Droid Families · Public information reflected here.