project-bro

Analyze software project state from docs and architecture files.

8|3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ydnikolaev/antigravity-factory --skill project-bro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-bro
Source: https://github.com/ydnikolaev/antigravity-factory/tree/main/.agent/skills/project-bro
Command: npx skills add https://github.com/ydnikolaev/antigravity-factory --skill project-bro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly understand the current state of a software project by reading docs, architecture context, and code, to answer questions like "where are we?" and "what's next?"

Core Features & Use Cases

  • Read artifact statuses from project/docs/ARTIFACT_REGISTRY.md
  • Compare roadmap against actual progress to identify gaps
  • Scan the codebase structure and key files to summarize the current state
  • Use during project health checks, onboarding, and planning sessions

Quick Start

Activate the skill with a natural prompt, for example: activate bro or project-bro. Then ask questions like: Where are we? What's left to do? What needs attention next?

Frequently Asked Questions about project-bro

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

FAQPage Schema
How do I analyze a software project to determine its current state and roadmap progress?

To analyze a software project, read the architecture directory, roadmap, and artifact registry to synthesize statuses, identify progress gaps, and determine next steps for project health checks.

What is the best way to identify gaps between a project roadmap and actual codebase progress?

Identify roadmap gaps by comparing planned milestones against actual artifact statuses read from the artifact registry and codebase structure, summarizing project state and highlighting remaining tasks.

Can I use project documentation to summarize architecture risks and next steps for a project health check?

Yes, you can use project documentation to summarize architecture risks and next steps by reading the architecture directory and artifact registry to synthesize concise project state reports.

What file formats and docs are required to generate a project state summary for onboarding?

Generating a project state summary requires reading project/docs/ARTIFACT_REGISTRY.md, project/docs/roadmap.md, and files within the project/docs/architecture/ directory to analyze artifacts.

How does an artifact registry help track software project status during planning sessions?

An artifact registry tracks software project status by providing a centralized record of artifact states, which can be analyzed alongside roadmap documents to identify gaps and guide planning.

When do I need to scan the codebase structure to synthesize project status?

Scan the codebase structure to synthesize project status during project health checks, roadmap reviews, and architecture discussions when you need to identify gaps and determine immediate next steps.