rb-where-are-we

Generate an evidence-backed HTML status report from repository data.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/richardmbailey/rb-skills --skill rb-where-are-we
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rb-where-are-we
Source: https://github.com/richardmbailey/rb-skills/tree/main/rb-where-are-we
Command: npx skills add https://github.com/richardmbailey/rb-skills --skill rb-where-are-we

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill solves the problem of project ambiguity by generating a comprehensive, evidence-based HTML report that clearly defines the current state, health, and trajectory of a software project.

Core Features & Use Cases

  • Evidence-Based Reporting: Automatically aggregates data from git history, project plans, and code health metrics to provide an objective status overview.
  • Progressive Disclosure: Structures information from a high-level executive summary down to granular technical evidence.
  • Use Case: Use this when you need to provide stakeholders with a professional, verifiable status update that covers project goals, current phase, risks, and next steps without manually compiling disparate sources.

Quick Start

Invoke the rb-where-are-we skill to generate a comprehensive HTML status report for the current project directory.

Frequently Asked Questions about rb-where-are-we

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

FAQPage Schema
How do I generate an evidence-backed project status report from a git repository?

To generate an evidence-backed project status report from a git repository, you can use this skill to automatically aggregate git history, project plans, and code health metrics into a comprehensive HTML overview.

What is the best way to create a verifiable software project health check for stakeholders?

A verifiable software project health check for stakeholders is an objective status overview that aggregates local repository data and code metrics to provide structured, deterministic validation of current project trajectory.

Can I automate technical auditing and stakeholder communication for my software project?

Yes, you can automate technical auditing and stakeholder communication by generating a structured HTML report that applies progressive disclosure, moving from an executive summary down to granular technical evidence.

Do I need external dependencies to produce a deterministic project status report?

No, you do not need external dependencies to produce a deterministic project status report, as this skill operates using local repository data and internal scripts to validate project health without external integrations.

How does a project status report handle progressive disclosure for technical auditing scenarios?

Project status reports handle progressive disclosure for technical auditing scenarios by structuring information hierarchically, starting with high-level project goals and risks before detailing granular technical evidence.

When should I not use an automated HTML status report for project management?

You should not use an automated HTML status report for project management if your project lacks local repository data or git history, as the tool relies on deterministic validation from these existing sources.