product-manager-agent-authoring

Assess code changes against project goals, scope, and architecture.

Updated May 12, 2026
One-click install
npx skills add https://github.com/RorySullivan1/claudeBrain --skill product-manager-agent-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager-agent-authoring
Source: https://github.com/RorySullivan1/claudeBrain/tree/main/.claude/skills/product-manager-agent-authoring
Command: npx skills add https://github.com/RorySullivan1/claudeBrain --skill product-manager-agent-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns code changes with the project's goals, scope, and architecture by providing a project-wide, read-only assessment rather than line-by-line diffs.

Core Features & Use Cases

  • Read-only, project-altitude assessor that anchors on CLAUDE.md, README, DECISIONS.md, roadmaps, and architecture to judge fit with the project.
  • Produces a prioritized assessment of changes, highlighting scope alignment, design consistency, maintainability, and potential tradeoffs.
  • Applicable to pull requests, architecture changes, and feature proposals to surface impact across the whole system without mutating code.
  • Output is a concise report that helps maintainers decide what to fix now, what to track as debt, and what to defer.

Quick Start

Provide a project-wide assessment for a given change or PR against the project's goals and architecture.

Frequently Asked Questions about product-manager-agent-authoring

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

FAQPage Schema
How do I assess if a pull request aligns with project architecture and scope?

To assess pull request alignment, evaluate the code changes against project goals, scope, and architecture. The assessment reads relevant project docs like CLAUDE.md and README to surface impact, tradeoffs, and design-consistency without mutating code.

What is project-wide code change assessment for feature proposals?

Project-wide code change assessment is a read-only evaluation that anchors on roadmaps and DECISIONS.md to judge fit. It produces a prioritized report highlighting scope alignment, maintainability, and potential tradeoffs for feature proposals.

How to evaluate architectural refactoring impact across the entire codebase?

Evaluate architectural refactoring impact by applying a project-altitude assessor to surface system-wide effects. It checks design consistency and risk tradeoffs against architecture docs, outputting actionable recommendations without modifying the codebase.

Can I use this for prioritizing technical debt from feature proposals?

Yes, you can use this for prioritizing technical debt. The output report helps maintainers decide what to fix immediately, what to track as debt, and what to defer based on scope alignment and maintainability tradeoffs.

Does the code review assessment modify repository files?

No, the code review assessment does not modify repository files. It operates as a read-only evaluation, analyzing pull requests and architecture changes to deliver a concise report without mutating any code.