project-status

Scan workspace artifacts and report project phase, blockers, and next actions.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/bbolek-ap/new-ai-native --skill project-status-bbolek-ap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-status
Source: https://github.com/bbolek-ap/new-ai-native/tree/main/.claude/skills/project-status
Command: npx skills add https://github.com/bbolek-ap/new-ai-native --skill project-status-bbolek-ap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inventory existing project artifacts across all output folders and report current elaboration phase, completed work, missing artifacts, and recommended next steps. Use when the user asks "where are we?", "what's the project status?", "what should I do next?", or at the start of a new session to orient.

Core Features & Use Cases

  • Inventory and audit across .project/ folders to enumerate meetings, formal docs, intake records, module definitions, architecture docs, ADRs, WBS, estimates, and delivery artifacts.
  • Phase determination: assess which elaboration phase the project has reached and identify gaps to unlock the next steps.
  • Risk and blockers: surface missing artifacts, conflicting ADRs, and dependencies to inform planning.

Quick Start

Ask the AI to generate a current project-status report for this workspace.

Frequently Asked Questions about project-status

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

FAQPage Schema
How do I check the current project status and identify our elaboration phase?

You can generate a project status report by scanning workspace artifacts to inventory files, determine the elaboration phase, and summarize recommended next actions. This reflects completed work, missing artifacts, and blockers.

What is the best way to inventory project artifacts and find missing ADRs?

Inventory project artifacts by scanning `.project/` folders to enumerate meetings, formal docs, ADRs, and WBS. This surfaces missing artifacts, conflicting ADRs, and dependencies to inform risk warnings and planning.

Can I determine what I should do next based on existing workspace files?

Yes, you can determine next actions by auditing existing workspace files to assess the elaboration phase. The scan identifies gaps in module definitions, architecture docs, and delivery artifacts to unlock subsequent steps.

Does project status scanning work without external dependencies or components?

Yes, project status scanning works without external dependencies or components. It relies on internal workspace scanning to locate `.project/` folders, inventory artifacts, and determine technology stack decision status.

Why do I need a workspace scan to orient a new session?

A workspace scan orients a new session by inventorying existing project artifacts, determining the elaboration phase, and surfacing blockers. This provides immediate context on completed work and recommended next actions.

How do I surface risk warnings and blockers from conflicting architecture decisions?

Surface risk warnings by scanning artifact inventories to identify missing files, conflicting ADRs, and unresolved dependencies. This highlights blockers across architecture docs and module definitions to inform planning.