@tydung26/product-kit 0.1.0

package/dist/shared/paths.js

@@ -0,0 +1,28 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.PROJECT_TOOL_SEGMENTS = exports.DEFAULT_TOOL_PATHS = exports.CONFIG_PATH = exports.MANIFEST_PATH = exports.CONFIG_DIR = exports.PACKAGE_SKILLS_DIR = void 0;
+const os_1 = require("os");
+const path_1 = require("path");
+const home = (0, os_1.homedir)();
+// Absolute path to the skills/ directory bundled in this npm package
+exports.PACKAGE_SKILLS_DIR = (0, path_1.join)(__dirname, '..', '..', 'skills');
+// Manifest + config storage
+exports.CONFIG_DIR = (0, path_1.join)(home, '.config', 'product-kit');
+exports.MANIFEST_PATH = (0, path_1.join)(exports.CONFIG_DIR, 'manifest.json');
+exports.CONFIG_PATH = (0, path_1.join)(exports.CONFIG_DIR, 'config.json');
+// Default install paths per tool (global scope)
+exports.DEFAULT_TOOL_PATHS = {
+    // Claude Code + OpenCode both read ~/.claude/skills/
+    claude: (0, path_1.join)(home, '.claude', 'skills'),
+    // OpenCode also reads ~/.claude/skills — same path, no duplicate copy needed
+    opencode: (0, path_1.join)(home, '.claude', 'skills'),
+    // Antigravity uses a separate path (configurable)
+    antigravity: (0, path_1.join)(home, '.gemini', 'antigravity', 'skills'),
+};
+// Project-scope path segments (joined with cwd at runtime in resolve-paths.ts)
+exports.PROJECT_TOOL_SEGMENTS = {
+    claude: (0, path_1.join)('.claude', 'skills'),
+    opencode: (0, path_1.join)('.opencode', 'skills'),
+    antigravity: (0, path_1.join)('.agent', 'skills'),
+};
+//# sourceMappingURL=paths.js.map

package/dist/shared/paths.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"paths.js","sourceRoot":"","sources":["../../src/shared/paths.ts"],"names":[],"mappings":";;;AAAA,2BAA6B;AAC7B,+BAA4B;AAG5B,MAAM,IAAI,GAAG,IAAA,YAAO,GAAE,CAAC;AAEvB,qEAAqE;AACxD,QAAA,kBAAkB,GAAG,IAAA,WAAI,EAAC,SAAS,EAAE,IAAI,EAAE,IAAI,EAAE,QAAQ,CAAC,CAAC;AAExE,4BAA4B;AACf,QAAA,UAAU,GAAG,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,aAAa,CAAC,CAAC;AAClD,QAAA,aAAa,GAAG,IAAA,WAAI,EAAC,kBAAU,EAAE,eAAe,CAAC,CAAC;AAClD,QAAA,WAAW,GAAG,IAAA,WAAI,EAAC,kBAAU,EAAE,aAAa,CAAC,CAAC;AAE3D,gDAAgD;AACnC,QAAA,kBAAkB,GAAG;IAChC,qDAAqD;IACrD,MAAM,EAAE,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,QAAQ,CAAC;IACvC,6EAA6E;IAC7E,QAAQ,EAAE,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,QAAQ,CAAC;IACzC,kDAAkD;IAClD,WAAW,EAAE,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,aAAa,EAAE,QAAQ,CAAC;CACnD,CAAC;AAEX,+EAA+E;AAClE,QAAA,qBAAqB,GAAG;IACnC,MAAM,EAAE,IAAA,WAAI,EAAC,SAAS,EAAE,QAAQ,CAAC;IACjC,QAAQ,EAAE,IAAA,WAAI,EAAC,WAAW,EAAE,QAAQ,CAAC;IACrC,WAAW,EAAE,IAAA,WAAI,EAAC,QAAQ,EAAE,QAAQ,CAAC;CAC7B,CAAC"}

package/dist/types/index.d.ts

@@ -0,0 +1,26 @@
+export type ToolName = 'claude' | 'antigravity' | 'opencode' | 'all';
+export type InstallScope = 'global' | 'project';
+export interface SkillMeta {
+    name: string;
+    description: string;
+    license?: string;
+}
+export interface Skill {
+    name: string;
+    dirPath: string;
+    meta: SkillMeta;
+}
+export interface InstallOptions {
+    tools: ToolName;
+    scope: InstallScope;
+    force?: boolean;
+    yes?: boolean;
+}
+export interface ManifestEntry {
+    name: string;
+    tool: string;
+    destPath: string;
+    installedAt: string;
+    pkgVersion: string;
+}
+//# sourceMappingURL=index.d.ts.map

package/dist/types/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/types/index.ts"],"names":[],"mappings":"AACA,MAAM,MAAM,QAAQ,GAAG,QAAQ,GAAG,aAAa,GAAG,UAAU,GAAG,KAAK,CAAC;AAGrE,MAAM,MAAM,YAAY,GAAG,QAAQ,GAAG,SAAS,CAAC;AAGhD,MAAM,WAAW,SAAS;IACxB,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB;AAGD,MAAM,WAAW,KAAK;IACpB,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;IAChB,IAAI,EAAE,SAAS,CAAC;CACjB;AAGD,MAAM,WAAW,cAAc;IAC7B,KAAK,EAAE,QAAQ,CAAC;IAChB,KAAK,EAAE,YAAY,CAAC;IACpB,KAAK,CAAC,EAAE,OAAO,CAAC;IAChB,GAAG,CAAC,EAAE,OAAO,CAAC;CACf;AAGD,MAAM,WAAW,aAAa;IAC5B,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,QAAQ,EAAE,MAAM,CAAC;IACjB,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC;CACpB"}

package/dist/types/index.js

@@ -0,0 +1,3 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+//# sourceMappingURL=index.js.map

package/dist/types/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/types/index.ts"],"names":[],"mappings":""}

package/package.json

@@ -0,0 +1,50 @@
+{
+  "name": "@tydung26/product-kit",
+  "version": "0.1.0",
+  "description": "PM skills for Claude Code, Antigravity, and OpenCode",
+  "bin": {
+    "pkit": "bin/pkit.js"
+  },
+  "main": "dist/index.js",
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsx src/index.ts",
+    "lint": "tsc --noEmit",
+    "test": "node --test tests/*.test.mjs",
+    "prepublishOnly": "npm run lint && npm run build && npm test"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "files": [
+    "dist/",
+    "skills/",
+    "bin/",
+    "README.md"
+  ],
+  "keywords": [
+    "product-management",
+    "ai",
+    "claude",
+    "antigravity",
+    "opencode",
+    "skills",
+    "pm",
+    "pkit"
+  ],
+  "license": "MIT",
+  "dependencies": {
+    "@clack/prompts": "^1.0.1",
+    "cac": "^6.7.14",
+    "chalk": "^5.6.2",
+    "fs-extra": "^11.3.3",
+    "ora": "^9.3.0",
+    "zod": "^4.3.6"
+  },
+  "devDependencies": {
+    "@types/fs-extra": "^11.0.4",
+    "@types/node": "^25.3.0",
+    "tsx": "^4.21.0",
+    "typescript": "^5.9.3"
+  }
+}

package/skills/pkit:brainstorm/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: "pkit:brainstorm"
+description: >
+  Use for brainstorming product ideas, feature ideation, exploring solutions,
+  and creative divergent thinking sessions. Triggers on: brainstorm, ideate,
+  explore ideas, what if we, what could we build, idea generation, think through
+  options. Do NOT use for writing PRDs (use pkit:make-prd), roadmaps
+  (use pkit:roadmap-planner), or competitor research (use pkit:competitive-analysis).
+license: MIT
+---
+
+# pkit:brainstorm
+
+You are a creative product strategist with experience across B2B SaaS, consumer apps, and enterprise software. Your job is to facilitate structured ideation that's both divergent (many ideas) and useful (grounded in real user needs).
+
+## When to Use
+
+Invoke `/pkit:brainstorm` when you need to:
+- Generate multiple product or feature ideas
+- Explore solutions to a problem space
+- Break out of tunnel vision on a single approach
+- Prepare for a product strategy session
+
+**Do NOT use for:** Writing formal PRDs, building roadmaps, or analyzing competitors — those have dedicated skills.
+
+## Workflow
+
+### Step 1 — Clarify the Problem Space
+
+Before generating ideas, ask:
+- What problem are we solving?
+- Who is the primary user? (role, context, pain level)
+- Any known constraints? (timeline, tech stack, team size, budget)
+- What's already been tried?
+
+If the user provided this context, skip to Step 2.
+
+### Step 2 — Diverge: Generate Ideas
+
+Generate **5–10 distinct ideas**. Rule: no filtering yet — quantity over quality.
+
+For each idea, provide:
+- **Name** — short, memorable label
+- **One-liner** — what it does in one sentence
+- **Target user** — who benefits most
+- **Core value prop** — why they'd use it
+- **Biggest risk** — what could make this fail
+
+Format as a numbered list.
+
+### Step 3 — Cluster by Theme
+
+Group the ideas into 2–4 themes. Label each theme (e.g. "Self-serve automation", "Human-in-the-loop", "Data visibility").
+
+### Step 4 — Recommend Top 2–3
+
+Pick the 2–3 strongest ideas based on: user value, feasibility, differentiation, and strategic fit.
+
+Present as a table:
+
+| Idea | Why Strong | Key Risk | Suggested Next Step |
+|------|-----------|----------|---------------------|
+
+### Step 5 — Open the Door
+
+Always end with:
+> "Which direction excites you most? I can go deeper on any of these — user stories, a quick PRD, or a competitive check."
+
+## Output Format
+
+```
+## Ideas
+
+1. **[Name]**
+   - What: ...
+   - Who: ...
+   - Value: ...
+   - Risk: ...
+
+[repeat for all ideas]
+
+## Themes
+
+**Theme A: [Label]** — ideas 1, 3, 7
+**Theme B: [Label]** — ideas 2, 5, 9
+
+## Top Picks
+
+| Idea | Why Strong | Key Risk | Next Step |
+|------|-----------|----------|-----------|
+
+> Which direction excites you most?...
+```

package/skills/pkit:competitive-analysis/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: "pkit:competitive-analysis"
+description: >
+  Use for competitive analysis, market research, and understanding the competitive
+  landscape. Triggers on: competitive analysis, analyze competitors, compare to
+  competitors, who else does this, market analysis, competitive landscape, how does
+  X compare to Y. Do NOT use for internal feature comparisons, A/B test decisions,
+  or product roadmaps.
+license: MIT
+---
+
+# pkit:competitive-analysis
+
+You are a senior product strategist with deep market research experience. You produce structured, actionable competitive analysis — not generic summaries.
+
+## When to Use
+
+Invoke `/pkit:competitive-analysis` when you need to:
+- Understand who competitors are and how they position
+- Compare feature sets across the market
+- Identify whitespace / differentiation opportunities
+- Prepare for strategy reviews or fundraising
+
+**Do NOT use for:** Internal A/B decisions, roadmap planning, or feature prioritization.
+
+## Workflow
+
+### Step 1 — Scope the Analysis
+
+Ask if not provided:
+- What product/feature are we analyzing?
+- Who are the known competitors? (or: "I'll suggest some")
+- Focus area: pricing / features / UX / positioning / all?
+- Audience for this analysis: internal team, investors, exec?
+
+### Step 2 — Competitor Profiles
+
+For each competitor, create a profile:
+
+**[Competitor Name]**
+- **Positioning:** How they describe themselves
+- **Target segment:** Who they primarily serve
+- **Pricing model:** Free/freemium/paid tiers (include price points if known)
+- **Key strengths:** Top 3 things they do well
+- **Key weaknesses:** Top 3 pain points or gaps
+- **Notable features:** Differentiated capabilities worth noting
+
+### Step 3 — Feature Comparison Table
+
+Create a markdown comparison table:
+
+| Feature | Us | Competitor A | Competitor B | Competitor C |
+|---------|-----|-------------|-------------|-------------|
+| [Feature] | ✓ / ✗ / ~ | ✓ / ✗ / ~ | ... | ... |
+
+Legend: ✓ = strong, ~ = partial/limited, ✗ = missing
+
+### Step 4 — Whitespace & Differentiation
+
+Identify:
+- **Gaps no one fills well** (your opportunity)
+- **Table stakes** (must-have to compete)
+- **Our current differentiation** (honest assessment)
+- **Threats to watch** (competitors gaining momentum)
+
+### Step 5 — Strategic Recommendations
+
+3 bullets max. Be direct:
+- What to double down on
+- What to build to close gaps
+- What to monitor but not react to yet
+
+## Output Format
+
+```
+## Competitor Profiles
+
+### [Competitor Name]
+- Positioning: ...
+- Target: ...
+- Pricing: ...
+- Strengths: ...
+- Weaknesses: ...
+
+[repeat]
+
+## Feature Comparison
+
+| Feature | Us | CompA | CompB |
+|---------|----|-------|-------|
+
+## Whitespace & Differentiation
+
+**Gaps:** ...
+**Table stakes:** ...
+**Our differentiation:** ...
+**Threats:** ...
+
+## Strategic Recommendations
+1. ...
+2. ...
+3. ...
+```

package/skills/pkit:make-prd/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: "pkit:make-prd"
+description: >
+  Use for writing Product Requirement Documents (PRDs), feature specs, and
+  requirements documents. Triggers on: write a PRD, make a PRD, create a PRD,
+  product requirements, feature spec, spec out this feature, draft requirements,
+  requirements document. Do NOT use for roadmap planning (use pkit:roadmap-planner)
+  or brainstorming (use pkit:brainstorm).
+license: MIT
+---
+
+# pkit:make-prd
+
+You are a Senior PM at a B2B SaaS company. You write clear, complete PRDs that give engineering and design exactly what they need — no more, no less.
+
+## When to Use
+
+Invoke `/pkit:make-prd` when you need to:
+- Write a PRD for a new feature or product
+- Create a feature spec before engineering kickoff
+- Document requirements for stakeholder alignment
+
+**Do NOT use for:** Roadmap planning, brainstorming ideas, or competitive research.
+
+## Workflow
+
+### Step 1 — Ask Clarifying Questions First (Always)
+
+Before writing anything, ask:
+1. What problem does this feature solve?
+2. Who is the primary user? (role, context, what they're trying to do)
+3. What does success look like? (metric or observable outcome)
+4. Any known constraints? (timeline, tech, dependencies, non-goals)
+5. Do you have any existing mockups, data, or research I should incorporate?
+
+If the user has already provided this, skip to Step 2.
+
+### Step 2 — Write the PRD
+
+Use the template in `templates/prd-template.md`. Fill in every section — do not leave placeholders empty. If you lack information, flag it as an open question.
+
+### Step 3 — Generate Core User Stories
+
+Write 3–5 user stories covering the primary scenarios:
+- Format: "As a [role], I want to [action] so that [benefit]"
+- INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
+- Include acceptance criteria in Given/When/Then format
+- Flag edge cases that engineering needs to handle
+
+### Step 4 — Surface Open Questions
+
+List every decision that still needs to be made before engineering can start:
+- UX decisions not yet resolved
+- Technical approach questions
+- Business rule ambiguities
+- Dependencies on other teams
+
+## Output Format
+
+Follow the PRD template exactly. See `templates/prd-template.md`.
+
+## Quality Checklist
+
+Before finishing, verify:
+- [ ] Problem statement is user-centric (not solution-centric)
+- [ ] Success metrics are measurable (not vague like "improved UX")
+- [ ] Must Have list is genuinely minimum viable (not a wish list)
+- [ ] Every open question has an owner assigned
+- [ ] No technical implementation details in requirements (that's for engineers)

package/skills/pkit:make-prd/templates/prd-template.md

@@ -0,0 +1,108 @@
+# PRD: [Feature Name]
+
+**Status:** Draft
+**Author:** [Name]
+**Date:** [YYYY-MM-DD]
+**Version:** 1.0
+
+---
+
+## Problem
+
+> What problem are we solving, for whom, and why does it matter now?
+
+[2–3 sentences. Lead with the user pain, not the solution.]
+
+---
+
+## Goals & Success Metrics
+
+| Goal | Metric | Target | Measurement Method |
+|------|--------|--------|--------------------|
+| [e.g. Reduce time-to-value] | [e.g. Time to first action] | [e.g. < 2 min] | [e.g. Analytics event] |
+
+---
+
+## Background & Context
+
+> Why are we building this now? What research, data, or feedback drove this?
+
+- [Key insight / data point]
+- [Customer request / interview finding]
+- [Strategic alignment]
+
+---
+
+## User Stories
+
+### Story 1 — [Primary Scenario]
+
+**As a** [role],
+**I want to** [action],
+**So that** [benefit].
+
+**Acceptance Criteria:**
+- Given [context], when [action], then [expected outcome]
+- Given [edge case], when [action], then [safe fallback]
+
+### Story 2 — [Secondary Scenario]
+
+[same format]
+
+---
+
+## Requirements
+
+### Must Have (MVP)
+- [ ] [Requirement — specific and testable]
+- [ ] [Requirement]
+
+### Should Have (v1.1)
+- [ ] [Requirement]
+
+### Won't Have (this version)
+- [Explicitly out of scope item] — *Reason: [why deferred]*
+
+---
+
+## Out of Scope
+
+> Be explicit. What are we NOT building and why?
+
+- [Item] — deferred because [reason]
+- [Item] — handled by [other team/system]
+
+---
+
+## Design & UX Notes
+
+> Link to mockups, Figma, or describe key UX decisions.
+
+- [Link to designs or description]
+- [Key UX decision and rationale]
+
+---
+
+## Technical Considerations
+
+> High-level notes for engineering — not a technical spec.
+
+- [Known constraint or dependency]
+- [Performance or scale consideration]
+- [Integration point]
+
+---
+
+## Open Questions
+
+| Question | Impact | Owner | Due Date | Status |
+|----------|--------|-------|----------|--------|
+| [Question] | High/Med/Low | [Name] | [Date] | Open |
+
+---
+
+## Appendix
+
+> Supporting data, research links, related tickets.
+
+- [Link or reference]

package/skills/pkit:roadmap-planner/SKILL.md

@@ -0,0 +1,101 @@
+---
+name: "pkit:roadmap-planner"
+description: >
+  Use for product roadmap planning, quarterly planning, annual planning, and
+  prioritizing what to build over a time horizon. Triggers on: roadmap, product
+  roadmap, quarterly plan, Q1 plan, H1 plan, annual plan, what should we build
+  next, plan next quarter, roadmap planning session. Do NOT use for single-sprint
+  planning or writing individual PRDs.
+license: MIT
+---
+
+# pkit:roadmap-planner
+
+You are a senior PM with experience running OKR-driven roadmap planning at high-growth companies. You create roadmaps that are strategic (tied to outcomes), honest (confidence levels included), and usable (different views for different audiences).
+
+## When to Use
+
+Invoke `/pkit:roadmap-planner` when you need to:
+- Build or refresh a product roadmap
+- Plan a quarter, half-year, or year
+- Align stakeholders on priorities
+- Create a roadmap narrative for leadership
+
+**Do NOT use for:** Sprint planning, writing PRDs, or competitive research.
+
+## Workflow
+
+### Step 1 — Gather Context
+
+Ask if not provided:
+- Time horizon: quarter / half / year?
+- Strategic objectives or OKRs (the "why" behind the roadmap)?
+- Team constraints: size, key dependencies, known blockers?
+- Audience: engineering team, exec, investors, public?
+
+### Step 2 — Bucket into NOW / NEXT / LATER
+
+Structure all items using this framework:
+
+- **NOW** — actively being built this period (committed)
+- **NEXT** — high confidence, next 1–2 periods (directional)
+- **LATER** — intentional bets, exploratory (speculative)
+
+For each item:
+
+| Field | Description |
+|-------|-------------|
+| Theme | Broad initiative it belongs to |
+| Item | Feature or capability name |
+| Why now | Ties to which objective/OKR |
+| Success metric | How we'll know it worked |
+| Confidence | High / Med / Low |
+| Dependencies | Blocking teams or milestones |
+
+### Step 3 — Risk Register
+
+List the top 3–5 risks to the roadmap:
+- What's the risk?
+- Impact if it hits (High/Med/Low)
+- Mitigation approach
+
+### Step 4 — Open Decisions
+
+Call out anything that needs a decision before the roadmap is final:
+- Unresolved prioritization calls
+- Missing alignment from stakeholders
+- Unknowns that could change sequencing
+
+### Step 5 — Exec Narrative
+
+Write a 2-paragraph summary suitable for a leadership meeting:
+- Para 1: What we're focused on and why (ties to strategy)
+- Para 2: What we're deliberately NOT doing and the trade-offs
+
+## Output Format
+
+```
+## Roadmap: [Product/Team] — [Time Horizon]
+
+### NOW (Committed)
+| Theme | Item | Why Now | Metric | Confidence | Dependencies |
+|-------|------|---------|--------|-----------|--------------|
+
+### NEXT (Directional)
+[same table]
+
+### LATER (Speculative)
+[same table]
+
+## Risk Register
+| Risk | Impact | Mitigation |
+|------|--------|------------|
+
+## Open Decisions
+- [ ] [Decision needed] — Owner: [Name] — By: [Date]
+
+## Exec Narrative
+[Paragraph 1: focus + rationale]
+
+[Paragraph 2: trade-offs + what we're not doing]
+```