product-management

Draft comprehensive PRDs referencing real code, APIs, and technical constraints.

1|1|Updated May 23, 2025
One-click install
npx skills add https://github.com/GrupoUS/aegiswallet --skill product-management-grupous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-management
Source: https://github.com/GrupoUS/aegiswallet/tree/main/.factory/skills/product-management
Command: npx skills add https://github.com/GrupoUS/aegiswallet --skill product-management-grupous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams draft PRDs, analyze features, synthesize user research, plan roadmaps, and communicate product decisions to stakeholders and engineering teams, grounding artifacts in actual codebase context and API constraints.

Core Features & Use Cases

  • Integrated with codebase: Reference actual code, APIs, and technical constraints in PM artifacts.
  • Context-aware: Tailors outputs to your product architecture and existing tech debt.
  • Flexible templates: Adapts documentation to organizational needs (PRD, spec, roadmaps, decision docs).
  • Version controlled: Artifacts live in git alongside code.
  • Collaborative: Works within existing dev workflows (PRs, issues, docs).
  • Input examples: Use existing product context, feature requests, or user research to produce PRDs and roadmaps.

Quick Start

Provide a PRD outline for a new feature: problem statement, goals, user stories, functional/non-functional requirements, risks, and rollout plan.

Frequently Asked Questions about product-management

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

FAQPage Schema
How do I write a PRD that references actual code and API constraints?

To draft a PRD with code context, provide an outline including problem statement, goals, user stories, functional requirements, risks, and rollout plan. It generates analysis referencing real APIs and technical constraints from your codebase.

What is the best way to plan a product roadmap using existing codebase context?

Planning roadmaps with codebase context involves synthesizing user research and feature requests against technical debt. This Skill tailors roadmap artifacts to your product architecture and existing technical constraints for stakeholder communication.

Can I use git workflows for version controlling PRDs and product specs?

Yes, you can use git workflows for version controlling PRDs. The Skill integrates with existing dev workflows, ensuring artifacts live in git alongside code and supporting collaboration through PRs and issues.

Does this tool support evaluating feature requests against current tech debt?

Yes, it supports evaluating feature requests against tech debt. The Skill performs feature analysis by tailoring outputs to your product architecture and existing technical constraints, grounding decisions in codebase reality.

How do I communicate product decisions to engineering teams using technical constraints?

To communicate product decisions to engineering teams, draft decision docs referencing actual APIs and constraints. The Skill synthesizes product context into artifacts designed for collaboration within existing development workflows.

What templates are available for product management documentation like specs and roadmaps?

Available templates adapt to organizational needs for PRDs, specs, roadmaps, and decision docs. The Skill provides flexible documentation templates customized using your existing product context and feature analysis data.