@gonzih/skills-product 1.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 gonzih
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,51 @@
+# @gonzih/skills-product
+
+Claude Code skill suite for product managers and product owners. Four skills, one install.
+
+## Install
+
+```bash
+npx @gonzih/skills-product
+```
+
+Or install globally:
+
+```bash
+npm install -g @gonzih/skills-product
+```
+
+Restart Claude Code after installing.
+
+## Skills
+
+### `/prd-writer`
+Write a Product Requirements Document from a feature description. Produces a complete PRD with problem statement, target users, user stories, success metrics, scope, and open questions.
+
+```
+/prd-writer Add a dark mode toggle to the settings page
+```
+
+### `/user-story-generator`
+Generate a full sprint's worth of user stories with acceptance criteria from a feature description. Stories are sized, prioritized, and packaged into a suggested sprint plan.
+
+```
+/user-story-generator User authentication with SSO support
+```
+
+### `/roadmap-builder`
+Build a quarterly roadmap from a list of initiatives. Organizes work into themes, applies RICE prioritization, and maps dependencies between initiatives.
+
+```
+/roadmap-builder Q2 goals: improve onboarding, launch API v2, reduce churn
+```
+
+### `/release-notes`
+Write polished release notes from a raw list of changes. Rewrites implementation details into user-facing language, categorizes changes, and adds a narrative header.
+
+```
+/release-notes v2.4.0 - fixed login bug, added CSV export, deprecated v1 API
+```
+
+## License
+
+MIT

package/install.js

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { copyFileSync, mkdirSync, existsSync } from 'fs';
+import { join } from 'path';
+import { homedir } from 'os';
+
+const skillsDir = join(homedir(), '.claude', 'skills');
+const skills = ['prd-writer', 'user-story-generator', 'roadmap-builder', 'release-notes'];
+
+for (const skill of skills) {
+  const dest = join(skillsDir, skill);
+  if (!existsSync(dest)) mkdirSync(dest, { recursive: true });
+  copyFileSync(new URL(`./skills/${skill}/SKILL.md`, import.meta.url).pathname, join(dest, 'SKILL.md'));
+  console.log(`✓ Installed /${skill}`);
+}
+console.log('\nSkills installed! Restart Claude Code to use them.');

package/package.json

@@ -0,0 +1,33 @@
+{
+  "name": "@gonzih/skills-product",
+  "version": "1.0.0",
+  "description": "Claude Code skill suite for product managers and product owners",
+  "type": "module",
+  "bin": {
+    "skills-product": "./install.js"
+  },
+  "scripts": {
+    "postinstall": "node install.js"
+  },
+  "files": [
+    "skills/",
+    "install.js",
+    "README.md",
+    "LICENSE"
+  ],
+  "keywords": [
+    "claude",
+    "claude-code",
+    "skills",
+    "product-management",
+    "prd",
+    "user-stories",
+    "roadmap",
+    "release-notes"
+  ],
+  "author": "gonzih",
+  "license": "MIT",
+  "engines": {
+    "node": ">=18"
+  }
+}

package/skills/prd-writer/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: prd-writer
+description: Write a Product Requirements Document with problem statement, user stories, success metrics, scope, and open questions.
+triggers: ["write a PRD", "product requirements document", "write requirements for"]
+---
+
+# PRD Writer
+
+## What this skill does
+Generates a structured Product Requirements Document (PRD) from a feature or product description. Covers the problem being solved, target users, user stories, measurable success metrics, in/out of scope, and open questions that need resolution before work begins.
+
+## How to invoke
+/prd-writer [feature or product description]
+
+## Workflow steps
+
+### Step 1 — Gather context
+Ask clarifying questions if the description is vague: Who are the target users? What problem does this solve? Are there any known constraints or existing systems involved? If the description is sufficiently detailed, proceed directly.
+
+### Step 2 — Draft the PRD
+Produce a document with the following sections:
+- **Overview** — One-paragraph summary of the feature and its purpose
+- **Problem Statement** — What pain point or opportunity is being addressed, and why it matters now
+- **Target Users** — Personas or segments who will use this feature
+- **User Stories** — Written as "As a [user], I want to [action] so that [benefit]", covering the primary flows
+- **Success Metrics** — Quantifiable outcomes (e.g., conversion rate, error rate, time-on-task) with baseline and target values where possible
+- **Scope** — Explicit list of what is in scope and what is explicitly out of scope for this version
+- **Open Questions** — Unresolved decisions, dependencies, or assumptions that need answers before development begins
+
+### Step 3 — Review and refine
+Invite the user to review the draft. Offer to expand any section, add technical constraints, or adjust the tone for the intended audience (engineering, executive, or external stakeholder).
+
+## Example outputs
+A complete PRD markdown document, typically 400–800 words, ready to paste into Notion, Confluence, or a GitHub issue. Sections are clearly headed and the open questions section flags blockers proactively.

package/skills/release-notes/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: release-notes
+description: Write polished release notes from a list of changes with user-facing framing, what changed, and why it matters.
+triggers: ["write release notes", "release notes for", "changelog for release"]
+---
+
+# Release Notes
+
+## What this skill does
+Transforms a raw list of changes (commits, tickets, or a changelog dump) into polished, user-facing release notes. Focuses on what changed and why it matters to the user — not internal implementation details. Adapts tone to match the audience (end users, developers, or enterprise customers).
+
+## How to invoke
+/release-notes [version number or release name, list of changes]
+
+## Workflow steps
+
+### Step 1 — Categorize changes
+Group changes into standard release note categories: **New Features**, **Improvements**, **Bug Fixes**, **Deprecations**, and **Breaking Changes**. Discard internal-only changes (refactors, test updates, CI changes) unless they affect observable behavior.
+
+### Step 2 — Reframe for users
+Rewrite each change from the user's perspective. Replace implementation language ("refactored the auth module") with benefit language ("Sign-in is now 40% faster"). For bug fixes, describe what was broken and what the experience is like now. For breaking changes, clearly state what will stop working and what users must do.
+
+### Step 3 — Write the release header
+Produce a short (2–3 sentence) summary paragraph for the release that highlights the most significant changes and the overall theme of the release (e.g., "performance quarter", "enterprise readiness"). Include the version number and release date.
+
+### Step 4 — Format and finalize
+Assemble the full release notes document with the header, categorized changes, and any migration notes for breaking changes. Offer a short version (one-liner per change) and a detailed version (with context) if the audience or channel requires different lengths.
+
+## Example outputs
+A formatted release notes document with a narrative header, categorized bullet points written in plain language, and a migration guide section if breaking changes are present. Suitable for a changelog page, email announcement, or in-app notification.

package/skills/roadmap-builder/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: roadmap-builder
+description: Build a quarterly roadmap with themes, initiatives, prioritization rationale, and a dependency map.
+triggers: ["build a roadmap", "quarterly roadmap", "product roadmap"]
+---
+
+# Roadmap Builder
+
+## What this skill does
+Constructs a structured quarterly roadmap from a list of initiatives, goals, or feature ideas. Organizes work into themes, applies a prioritization framework, surfaces dependencies between initiatives, and produces a format suitable for sharing with leadership, engineering, or customers.
+
+## How to invoke
+/roadmap-builder [list of initiatives, goals, or context about the product and quarter]
+
+## Workflow steps
+
+### Step 1 — Establish context
+Identify the planning horizon (default: one quarter), the primary audience for the roadmap (internal team, executives, customers), and any fixed constraints such as hard deadlines, compliance requirements, or team capacity. Ask for clarification if these are not provided.
+
+### Step 2 — Define themes
+Group initiatives into 2–4 strategic themes that reflect the product's goals for the quarter (e.g., "Reliability", "Growth", "Developer Experience"). Each theme should have a one-sentence rationale explaining why it matters this quarter.
+
+### Step 3 — Prioritize initiatives
+Apply an explicit prioritization framework — default to RICE (Reach, Impact, Confidence, Effort) unless the user specifies another (MoSCoW, Value vs. Effort, etc.). For each initiative, provide:
+- **Theme** — Which theme it belongs to
+- **Initiative** — Brief name and description
+- **Priority** — High / Medium / Low with a one-line rationale
+- **Rough size** — S / M / L / XL
+- **Quarter placement** — Now / Next / Later, or specific month
+
+### Step 4 — Map dependencies
+Identify initiatives that must be completed before others can start. Produce a simple dependency list (e.g., "Initiative B requires Initiative A to be complete") and flag any critical path items that could block the quarter's goals.
+
+## Example outputs
+A roadmap document with a theme overview, a prioritized initiative table, and a dependency list. Optionally formatted as a now/next/later grid. Suitable for presenting in a planning meeting or embedding in a strategy doc.

package/skills/user-story-generator/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: user-story-generator
+description: Generate a full sprint's worth of user stories with acceptance criteria from a feature description.
+triggers: ["generate user stories", "write user stories", "break into stories"]
+---
+
+# User Story Generator
+
+## What this skill does
+Takes a feature description and produces a prioritized backlog of user stories sized for a sprint, each with a clear title, narrative, and acceptance criteria. Stories follow standard Agile conventions and are scoped to be independently shippable where possible.
+
+## How to invoke
+/user-story-generator [feature description]
+
+## Workflow steps
+
+### Step 1 — Decompose the feature
+Identify the distinct user-facing capabilities implied by the feature description. Group them by user type or workflow stage. Flag any that are likely epics (too large for a single story) and break them down further.
+
+### Step 2 — Write the stories
+For each story, produce:
+- **Story ID** — Sequential identifier (e.g., US-01)
+- **Title** — Short imperative phrase (e.g., "Filter search results by date range")
+- **Narrative** — "As a [persona], I want to [goal] so that [benefit]"
+- **Acceptance Criteria** — Bulleted list of testable conditions using Given/When/Then or plain-language checklist format
+- **Story Points** — Rough estimate using Fibonacci (1, 2, 3, 5, 8) with a brief rationale
+- **Dependencies** — Any other stories or external work this story depends on
+
+### Step 3 — Prioritize and package
+Order stories by business value and dependency chain. Group into a suggested sprint plan that fits a standard 2-week sprint (assume ~30–40 points of velocity unless the user specifies otherwise). Highlight the MVP slice — the minimum set of stories that delivers end-to-end value.
+
+## Example outputs
+A numbered backlog of 8–15 user stories in a table or structured list, with each story fully specified and a sprint grouping at the end. Output is ready to copy into Jira, Linear, or any sprint planning tool.