Patrickjbagley/productManagerSkillandRules
Cursor rule
Documentation folder structure — productBrief, audienceProfiles, designDetails, features, specDocs, productRequirementsDocs, images. Use when creating or editing docs.
Patrickjbagley/productManagerSkillandRules
Cursor rule
Product philosophy and strategy — understand before acting, clarity over speed, outcomes over outputs. Always apply when discussing product, features, or requirements.
Patrickjbagley/productManagerSkillandRules
Skill Claude CodeCodex
Reviews PRD and spec for consistency, completeness, and clarity; optionally compares against uploaded mocks, wireframes, or fat-marker sketches and flags design inconsistencies. Use when the user wants a design or document review before implementation, or when running the feature-builder workflow after PRD and spec…
Patrickjbagley/productManagerSkillandRules
Skill Claude CodeCodex
Keeps the project's document library consistent after new or changed PRDs and specs. Discovers or uses the project's index, README, feature/capability pages, and spec listings; proposes and applies updates so new docs are discoverable. Use when new docs are added or changed and the user wants index and related pages…
Patrickjbagley/productManagerSkillandRules
Skill Claude CodeCodex
Scaffolds the standard documentation folder structure (README, productBrief, audienceProfiles, designDetails, features, specDocs, productRequirementsDocs, images). Use when setting up docs in a new repo or when the user asks to create the doc structure. When adding a new feature page, use the feature-template.md…
Patrickjbagley/productManagerSkillandRules
Skill Claude CodeCodex
End-to-end feature development from discovery through PRD, spec, design review, doc library cleanup, and optional implementation. Orchestrates sub-skills in phases with confirmation gates. Use when building a new feature or making significant feature changes and you want the full workflow.
Patrickjbagley/productManagerSkillandRules
Skill Claude CodeCodex
Produces a Product Requirements Document (PRD) from problem context. Use when the user needs a PRD written or updated, or when building a feature and a PRD is the next deliverable. Works standalone or as part of the feature-builder workflow.
Patrickjbagley/productManagerSkillandRules
Skill Claude CodeCodex
Produces a Spec Doc (feature summary, problems, audience, features, success metrics, and user flows). Use when the user needs a spec document written or updated, or when a PRD exists and the next deliverable is a spec. Works standalone or as part of the feature-builder workflow.