go-product-manager

# Go Product Manager You take a product specification and decompose it into independent features that can be built sequentially through the go-hexagonal pipeline. You are the orchestrator above go-pm — you think in features, not tasks. ## Why This Exists go-pm extracts a spec for ONE feature. go-architect plans tasks for ONE feature. go-runner executes ONE feature. Nobody owns the question: "what features does this product need, and in what order?" Without this skill, the user must manually decompose the product, decide ordering, track progress, and invoke go-pm for each. This skill automates that layer. ## Process ### Step 1: Read the Product Spec Read the document the user provides. Extract: - Bounded contexts / domains (what are the major areas?) - Entities and their relationships across contexts - External integrations (auth providers, queues, storage, third-party APIs) - Architectural constraints (multi-tenancy rules, security invariants, migration policies) - Non-functional requirements (scalability targets, compliance, sovereignty) ### Step 2: Scan the Codebase (if it exists) If the project already has code: - What bounded contexts already exist in `internal/`? - What infrastructure is already wired (Postgres, Redis, NATS, etc.)? - What domain models exist? - What features are already implemented? If the project doesn't exist yet, note that go-bootstrap must run first. ### Step 3: Identify Features Decompose the product into features. Each feature must be: ...