project-steward-reviewer

Name: project-steward-reviewer
Availability: InStock
Author: ylxmf

Apply governance review to proposed changes and output structured rubric findings.

11|1|Updated Mar 3, 2026

Search Tags:#governance #review #rubric #project-health #stakeholders #debt-ledger #long-term-cost

Ready to run

npx skills add https://github.com/ylxmf2005/AgentCorp --skill project-steward-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-steward-reviewer
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/project-steward-reviewer
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill project-steward-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Project Steward Reviewer provides a formal, auditable gate to evaluate long-term implications of changes, ensuring that commitments, costs, and ownership are clearly defined before they become part of the project history.

Core Features & Use Cases

Load and apply the stewardship rubric to changes that affect public surface, architecture, or debt.
Tag findings with rubrics such as Project Fit, Public Surface And Compatibility, Debt Ledger, and Ownership And Maintenance, and generate prioritized, owner-facing guidance.
Produce actionable records that bring long-term costs, ownership, and removal conditions into a human-readable decision trace for maintainers.

Quick Start

Run a review of a proposed change using the stewardship rubric and generate a prioritized findings report before approval.

Frequently Asked Questions about project-steward-reviewer

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

FAQPage Schema

What is a project stewardship review and when do I need it?▼

A project stewardship review is a formal gate to evaluate the long-term implications of changes. You need it during plan or code reviews when a change introduces public surface, dependencies, debt, or architectural boundaries.

How do I apply a governance rubric to evaluate long-term project health?▼

Apply the governance rubric by loading it during change reviews to assess project fit, compatibility, and maintenance. This generates a structured finding with rubric tags, severity assignments, and ownership markings for the proposed change.

How do I track technical debt and ownership during code reviews?▼

Track technical debt and ownership during code reviews by applying the Debt Ledger and Ownership And Maintenance rubrics. This tags findings, assigns severity, and produces a formal decision record detailing removal conditions.

Can I use this stewardship review for changes affecting public API surface?▼

Yes, you can use this stewardship review for changes affecting public API surface. The Public Surface And Compatibility rubric specifically evaluates these changes to ensure commitments and costs are defined before joining project history.

What is the best way to document long-term maintenance costs for stakeholders?▼

The best way to document long-term maintenance costs for stakeholders is to generate a human-readable decision trace. This formal record brings long-term costs, ownership, and removal conditions into a prioritized, owner-facing report.

When should I not use an automated governance review for project changes?▼

You should not use an automated governance review for minor changes that do not affect public surface, dependencies, debt, or architectural boundaries, as the formal rubric evaluation is designed for significant long-term project history decisions.