ndx-status

Aggregate PRD progress and codebase health into a unified status report.

16|9|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/en-dash-consulting/n-dx --skill ndx-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ndx-status
Source: https://github.com/en-dash-consulting/n-dx/tree/main/.agents/skills/ndx-status
Command: npx skills add https://github.com/en-dash-consulting/n-dx --skill ndx-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show comprehensive project status combining PRD progress and codebase health.

Core Features & Use Cases

  • Aggregate PRD progress via get_prd_status to track completion across teams.
  • Compile codebase overview via get_overview for files, zones, and languages.
  • Surface active issues via get_findings with severity "warning" or "critical" for early remediation.
  • Compute overall health via health to gauge structural risk.
  • Generate a unified report including progress, health, findings, and recommended next steps.
  • Real-world scenario: use during quarterly planning to align stakeholders on status and blockers.

Quick Start

Provide a single, consolidated status report by aggregating PRD progress, codebase health, active findings, and suggested next actions.

Frequently Asked Questions about ndx-status

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

FAQPage Schema
How do I generate a unified project status report covering both PRD progress and codebase health?

Generate a unified project status report by aggregating PRD progress, codebase overview, active findings, and suggested next actions into a single dashboard for stakeholders. It combines PRD completion tracking with structural codebase metrics to align product and engineering teams.

What is the best way to track active codebase issues alongside PRD completion for quarterly planning?

Track active codebase issues alongside PRD completion by surfacing findings with warning or critical severity and mapping them against PRD progress. This provides a comprehensive status view to align stakeholders on blockers and structural risks during quarterly planning.

Do I need specific MCP integrations to monitor PRD and codebase health in one view?

Yes, you need access to get_prd_status, get_overview, get_findings, health, and get_next_task MCPs to assemble the final report. These integrations provide the PRD progress, codebase metrics, and active findings required to compute the unified dashboard.

Can I surface critical codebase findings while tracking product requirements?

Yes, you can surface critical codebase findings while tracking product requirements. The report compiles active issues with warning or critical severity from get_findings and displays them next to PRD progress to highlight early remediation needs.

How does codebase health scoring work when combining PRD progress with structural metrics?

Codebase health scoring works by computing overall structural risk via the health metric and combining it with PRD completion data. It aggregates files, zones, and languages from get_overview to gauge risk and generate recommended next steps.

What does a consolidated codebase and PRD health dashboard include for engineering teams?

A consolidated dashboard includes PRD progress, codebase health scores, active findings with warning or critical severity, and recommended next steps. It aggregates files, zones, languages, and structural risk to give engineering and product teams a unified status view.