@tydung26/product-kit 0.1.4 → 1.0.0

package/README.md

@@ -15,7 +15,7 @@ pkit init              # Interactive: pick tool + commands
 pkit init --yes        # Install all commands to all tools
 pkit list                 # Show available/installed commands
 pkit update               # Update all installed commands
-pkit remove pkit:brainstorm
+pkit remove pkit:discover
 pkit config               # View configuration
 pkit config set toolPaths.antigravity /custom/path
 pkit doctor               # Diagnose installation issues
@@ -25,17 +25,17 @@ pkit doctor               # Diagnose installation issues
 
 | Slash Command | Purpose |
 |---|---|
-| `/pkit:brainstorm` | Ideation → clustered ideas → top picks |
-| `/pkit:competitive-analysis` | Competitor profiles → feature matrix → whitespace |
-| `/pkit:roadmap-planner` | NOW/NEXT/LATER table → risk register → exec narrative |
-| `/pkit:make-prd` | Clarifying questions → full PRD → user stories |
+| `/pkit:discover` | Discovery → customer slicing → clustered ideas → top picks |
+| `/pkit:market-intel` | Competitor profiles → feature matrix → whitespace → strategic recs |
+| `/pkit:roadmap` | NOW/NEXT/LATER table → risk register → exec narrative |
+| `/pkit:product-design` | PRD → brand guideline → wireframes → polished design |
 
 ## Install Paths
 
 | Tool | Global path |
 |---|---|
-| Claude Code + OpenCode | `~/.claude/commands/pkit/` |
-| Antigravity | `~/.gemini/antigravity/commands/pkit/` |
+| Claude Code + OpenCode | `~/.claude/skills/` |
+| Antigravity | `~/.gemini/antigravity/skills/` |
 
 ## License
 

package/dist/commands/install/index.js

@@ -45,7 +45,7 @@ function registerInstall(cli) {
             force: opts.force,
             yes: opts.yes,
         });
-        (0, prompts_1.outro)('Done! Use /pkit:brainstorm (or other skill names) in your AI tool.');
+        (0, prompts_1.outro)('Done! Use /pkit:discover (or other skill names) in your AI tool.');
     });
 }
 //# sourceMappingURL=index.js.map

package/dist/commands/install/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/commands/install/index.ts"],"names":[],"mappings":";;AAcA,0CA2CC;AAxDD,iDAA2D;AAC3D,6DAA2D;AAC3D,sDAAmG;AAWnG,SAAgB,eAAe,CAAC,GAAQ;IACtC,GAAG;SACA,OAAO,CAAC,kBAAkB,EAAE,wCAAwC,CAAC;SACrE,MAAM,CAAC,eAAe,EAAE,iDAAiD,CAAC;SAC1E,MAAM,CAAC,iBAAiB,EAAE,0BAA0B,EAAE,EAAE,OAAO,EAAE,QAAQ,EAAE,CAAC;SAC5E,MAAM,CAAC,SAAS,EAAE,kCAAkC,CAAC;SACrD,MAAM,CAAC,WAAW,EAAE,6DAA6D,CAAC;SAClF,MAAM,CAAC,KAAK,EAAE,MAAgB,EAAE,IAAiB,EAAE,EAAE;QACpD,IAAA,eAAK,EAAC,4BAA4B,CAAC,CAAC;QAEpC,6DAA6D;QAC7D,IAAI,IAAI,GAAG,IAAI,CAAC,IAAI,CAAC;QACrB,IAAI,CAAC,IAAI,EAAE,CAAC;YACV,IAAI,IAAI,CAAC,GAAG,EAAE,CAAC;gBACb,IAAI,GAAG,KAAK,CAAC;YACf,CAAC;iBAAM,CAAC;gBACN,IAAI,GAAG,MAAM,IAAA,6BAAmB,GAAE,IAAI,SAAS,CAAC;gBAChD,IAAI,CAAC,IAAI;oBAAE,OAAO;YACpB,CAAC;QACH,CAAC;QAED,6DAA6D;QAC7D,IAAI,UAAU,GAAG,MAAM,CAAC;QACxB,IAAI,UAAU,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YAC5B,MAAM,SAAS,GAAG,IAAA,4BAAmB,GAAE,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;YACzD,IAAI,IAAI,CAAC,GAAG,EAAE,CAAC;gBACb,UAAU,GAAG,SAAS,CAAC;YACzB,CAAC;iBAAM,CAAC;gBACN,MAAM,QAAQ,GAAG,MAAM,IAAA,8BAAoB,EAAC,SAAS,CAAC,CAAC;gBACvD,IAAI,CAAC,QAAQ;oBAAE,OAAO;gBACtB,UAAU,GAAG,QAAQ,CAAC;YACxB,CAAC;QACH,CAAC;QAED,MAAM,IAAA,4BAAa,EAAC,UAAU,EAAE;YAC9B,KAAK,EAAE,IAAgB;YACvB,KAAK,EAAE,IAAI,CAAC,KAAqB;YACjC,KAAK,EAAE,IAAI,CAAC,KAAK;YACjB,GAAG,EAAE,IAAI,CAAC,GAAG;SACd,CAAC,CAAC;QAEH,IAAA,eAAK,EAAC,oEAAoE,CAAC,CAAC;IAC9E,CAAC,CAAC,CAAC;AACP,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/commands/install/index.ts"],"names":[],"mappings":";;AAcA,0CA2CC;AAxDD,iDAA2D;AAC3D,6DAA2D;AAC3D,sDAAmG;AAWnG,SAAgB,eAAe,CAAC,GAAQ;IACtC,GAAG;SACA,OAAO,CAAC,kBAAkB,EAAE,wCAAwC,CAAC;SACrE,MAAM,CAAC,eAAe,EAAE,iDAAiD,CAAC;SAC1E,MAAM,CAAC,iBAAiB,EAAE,0BAA0B,EAAE,EAAE,OAAO,EAAE,QAAQ,EAAE,CAAC;SAC5E,MAAM,CAAC,SAAS,EAAE,kCAAkC,CAAC;SACrD,MAAM,CAAC,WAAW,EAAE,6DAA6D,CAAC;SAClF,MAAM,CAAC,KAAK,EAAE,MAAgB,EAAE,IAAiB,EAAE,EAAE;QACpD,IAAA,eAAK,EAAC,4BAA4B,CAAC,CAAC;QAEpC,6DAA6D;QAC7D,IAAI,IAAI,GAAG,IAAI,CAAC,IAAI,CAAC;QACrB,IAAI,CAAC,IAAI,EAAE,CAAC;YACV,IAAI,IAAI,CAAC,GAAG,EAAE,CAAC;gBACb,IAAI,GAAG,KAAK,CAAC;YACf,CAAC;iBAAM,CAAC;gBACN,IAAI,GAAG,MAAM,IAAA,6BAAmB,GAAE,IAAI,SAAS,CAAC;gBAChD,IAAI,CAAC,IAAI;oBAAE,OAAO;YACpB,CAAC;QACH,CAAC;QAED,6DAA6D;QAC7D,IAAI,UAAU,GAAG,MAAM,CAAC;QACxB,IAAI,UAAU,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YAC5B,MAAM,SAAS,GAAG,IAAA,4BAAmB,GAAE,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;YACzD,IAAI,IAAI,CAAC,GAAG,EAAE,CAAC;gBACb,UAAU,GAAG,SAAS,CAAC;YACzB,CAAC;iBAAM,CAAC;gBACN,MAAM,QAAQ,GAAG,MAAM,IAAA,8BAAoB,EAAC,SAAS,CAAC,CAAC;gBACvD,IAAI,CAAC,QAAQ;oBAAE,OAAO;gBACtB,UAAU,GAAG,QAAQ,CAAC;YACxB,CAAC;QACH,CAAC;QAED,MAAM,IAAA,4BAAa,EAAC,UAAU,EAAE;YAC9B,KAAK,EAAE,IAAgB;YACvB,KAAK,EAAE,IAAI,CAAC,KAAqB;YACjC,KAAK,EAAE,IAAI,CAAC,KAAK;YACjB,GAAG,EAAE,IAAI,CAAC,GAAG;SACd,CAAC,CAAC;QAEH,IAAA,eAAK,EAAC,kEAAkE,CAAC,CAAC;IAC5E,CAAC,CAAC,CAAC;AACP,CAAC"}

package/dist/domains/skills/skill-loader.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"skill-loader.d.ts","sourceRoot":"","sources":["../../../src/domains/skills/skill-loader.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,aAAa,CAAC;AAQzC,wBAAgB,mBAAmB,IAAI,KAAK,EAAE,CAoB7C;AAGD,wBAAgB,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,KAAK,GAAG,SAAS,CAE/D"}
+{"version":3,"file":"skill-loader.d.ts","sourceRoot":"","sources":["../../../src/domains/skills/skill-loader.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,aAAa,CAAC;AAQzC,wBAAgB,mBAAmB,IAAI,KAAK,EAAE,CAsB7C;AAGD,wBAAgB,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,KAAK,GAAG,SAAS,CAE/D"}

package/dist/domains/skills/skill-loader.js

@@ -6,32 +6,35 @@ const fs_1 = require("fs");
 const path_1 = require("path");
 const paths_1 = require("../../shared/paths");
 const skill_validator_1 = require("./skill-validator");
-// Derives the slash-command name from a filename: "brainstorm.md" → "pkit:brainstorm"
-function fileNameToCommandName(filename) {
-    return `pkit:${(0, path_1.basename)(filename, '.md')}`;
+// Derives the slash-command name from a directory: "discover" → "pkit:discover"
+function dirNameToCommandName(dirName) {
+    return `pkit:${dirName}`;
 }
-// Loads all commands from the bundled commands/pkit/ directory
+// Loads all skills from skills/ directories (each dir contains a SKILL.md file)
 function loadAvailableSkills() {
     if (!(0, fs_1.existsSync)(paths_1.PACKAGE_COMMANDS_DIR))
         return [];
     const skills = [];
     const entries = (0, fs_1.readdirSync)(paths_1.PACKAGE_COMMANDS_DIR, { withFileTypes: true });
     for (const entry of entries) {
-        if (!entry.isFile() || !entry.name.endsWith('.md'))
+        if (!entry.isDirectory())
+            continue;
+        // Look for SKILL.md inside each skill directory
+        const filePath = (0, path_1.join)(paths_1.PACKAGE_COMMANDS_DIR, entry.name, 'SKILL.md');
+        if (!(0, fs_1.existsSync)(filePath))
             continue;
-        const filePath = (0, path_1.join)(paths_1.PACKAGE_COMMANDS_DIR, entry.name);
         try {
             const content = (0, fs_1.readFileSync)(filePath, 'utf8');
             const meta = (0, skill_validator_1.validateSkillContent)(content, filePath);
-            skills.push({ name: fileNameToCommandName(entry.name), filePath, meta });
+            skills.push({ name: dirNameToCommandName(entry.name), filePath, meta });
         }
         catch {
-            // Skip invalid command files silently in production
+            // Skip invalid skill files silently in production
         }
     }
     return skills;
 }
-// Find a single command by name (e.g. "pkit:brainstorm")
+// Find a single skill by name (e.g. "pkit:discover")
 function findSkillByName(name) {
     return loadAvailableSkills().find(s => s.name === name);
 }

package/dist/domains/skills/skill-loader.js.map

@@ -1 +1 @@
-{"version":3,"file":"skill-loader.js","sourceRoot":"","sources":["../../../src/domains/skills/skill-loader.ts"],"names":[],"mappings":";;AAYA,kDAoBC;AAGD,0CAEC;AArCD,2BAA2D;AAC3D,+BAAsC;AACtC,8CAA0D;AAC1D,uDAAyD;AAGzD,sFAAsF;AACtF,SAAS,qBAAqB,CAAC,QAAgB;IAC7C,OAAO,QAAQ,IAAA,eAAQ,EAAC,QAAQ,EAAE,KAAK,CAAC,EAAE,CAAC;AAC7C,CAAC;AAED,+DAA+D;AAC/D,SAAgB,mBAAmB;IACjC,IAAI,CAAC,IAAA,eAAU,EAAC,4BAAoB,CAAC;QAAE,OAAO,EAAE,CAAC;IAEjD,MAAM,MAAM,GAAY,EAAE,CAAC;IAC3B,MAAM,OAAO,GAAG,IAAA,gBAAW,EAAC,4BAAoB,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;IAE3E,KAAK,MAAM,KAAK,IAAI,OAAO,EAAE,CAAC;QAC5B,IAAI,CAAC,KAAK,CAAC,MAAM,EAAE,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,QAAQ,CAAC,KAAK,CAAC;YAAE,SAAS;QAC7D,MAAM,QAAQ,GAAG,IAAA,WAAI,EAAC,4BAAoB,EAAE,KAAK,CAAC,IAAI,CAAC,CAAC;QAExD,IAAI,CAAC;YACH,MAAM,OAAO,GAAG,IAAA,iBAAY,EAAC,QAAQ,EAAE,MAAM,CAAC,CAAC;YAC/C,MAAM,IAAI,GAAG,IAAA,sCAAoB,EAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;YACrD,MAAM,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,qBAAqB,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC;QAC3E,CAAC;QAAC,MAAM,CAAC;YACP,oDAAoD;QACtD,CAAC;IACH,CAAC;IAED,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,yDAAyD;AACzD,SAAgB,eAAe,CAAC,IAAY;IAC1C,OAAO,mBAAmB,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC;AAC1D,CAAC"}
+{"version":3,"file":"skill-loader.js","sourceRoot":"","sources":["../../../src/domains/skills/skill-loader.ts"],"names":[],"mappings":";;AAYA,kDAsBC;AAGD,0CAEC;AAvCD,2BAA2D;AAC3D,+BAA4B;AAC5B,8CAA0D;AAC1D,uDAAyD;AAGzD,gFAAgF;AAChF,SAAS,oBAAoB,CAAC,OAAe;IAC3C,OAAO,QAAQ,OAAO,EAAE,CAAC;AAC3B,CAAC;AAED,gFAAgF;AAChF,SAAgB,mBAAmB;IACjC,IAAI,CAAC,IAAA,eAAU,EAAC,4BAAoB,CAAC;QAAE,OAAO,EAAE,CAAC;IAEjD,MAAM,MAAM,GAAY,EAAE,CAAC;IAC3B,MAAM,OAAO,GAAG,IAAA,gBAAW,EAAC,4BAAoB,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;IAE3E,KAAK,MAAM,KAAK,IAAI,OAAO,EAAE,CAAC;QAC5B,IAAI,CAAC,KAAK,CAAC,WAAW,EAAE;YAAE,SAAS;QACnC,gDAAgD;QAChD,MAAM,QAAQ,GAAG,IAAA,WAAI,EAAC,4BAAoB,EAAE,KAAK,CAAC,IAAI,EAAE,UAAU,CAAC,CAAC;QACpE,IAAI,CAAC,IAAA,eAAU,EAAC,QAAQ,CAAC;YAAE,SAAS;QAEpC,IAAI,CAAC;YACH,MAAM,OAAO,GAAG,IAAA,iBAAY,EAAC,QAAQ,EAAE,MAAM,CAAC,CAAC;YAC/C,MAAM,IAAI,GAAG,IAAA,sCAAoB,EAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;YACrD,MAAM,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,oBAAoB,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC;QAC1E,CAAC;QAAC,MAAM,CAAC;YACP,kDAAkD;QACpD,CAAC;IACH,CAAC;IAED,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,qDAAqD;AACrD,SAAgB,eAAe,CAAC,IAAY;IAC1C,OAAO,mBAAmB,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC;AAC1D,CAAC"}

package/dist/shared/paths.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"paths.d.ts","sourceRoot":"","sources":["../../src/shared/paths.ts"],"names":[],"mappings":"AAMA,eAAO,MAAM,oBAAoB,QAAkD,CAAC;AAGpF,eAAO,MAAM,UAAU,QAAuC,CAAC;AAC/D,eAAO,MAAM,aAAa,QAAoC,CAAC;AAC/D,eAAO,MAAM,WAAW,QAAkC,CAAC;AAG3D,eAAO,MAAM,kBAAkB;;;;CAOrB,CAAC;AAGX,eAAO,MAAM,qBAAqB;;;;CAIxB,CAAC"}
+{"version":3,"file":"paths.d.ts","sourceRoot":"","sources":["../../src/shared/paths.ts"],"names":[],"mappings":"AAMA,eAAO,MAAM,oBAAoB,QAAwC,CAAC;AAG1E,eAAO,MAAM,UAAU,QAAuC,CAAC;AAC/D,eAAO,MAAM,aAAa,QAAoC,CAAC;AAC/D,eAAO,MAAM,WAAW,QAAkC,CAAC;AAG3D,eAAO,MAAM,kBAAkB;;;;CAIrB,CAAC;AAGX,eAAO,MAAM,qBAAqB;;;;CAIxB,CAAC"}

package/dist/shared/paths.js

@@ -4,25 +4,22 @@ exports.PROJECT_TOOL_SEGMENTS = exports.DEFAULT_TOOL_PATHS = exports.CONFIG_PATH
 const os_1 = require("os");
 const path_1 = require("path");
 const home = (0, os_1.homedir)();
-// Absolute path to the commands/pkit/ directory bundled in this npm package
-exports.PACKAGE_COMMANDS_DIR = (0, path_1.join)(__dirname, '..', '..', 'commands', 'pkit');
+// Absolute path to the skills/ directory bundled in this npm package
+exports.PACKAGE_COMMANDS_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) — commands go into commands/pkit/
+// Default install paths per tool (global scope) — skills install to ~/.claude/skills/
 exports.DEFAULT_TOOL_PATHS = {
-    // Claude Code + OpenCode both read ~/.claude/commands/
-    claude: (0, path_1.join)(home, '.claude', 'commands', 'pkit'),
-    // OpenCode shares the same path as Claude Code
-    opencode: (0, path_1.join)(home, '.claude', 'commands', 'pkit'),
-    // Antigravity uses a separate path (configurable)
-    antigravity: (0, path_1.join)(home, '.gemini', 'antigravity', 'commands', 'pkit'),
+    claude: (0, path_1.join)(home, '.claude', 'skills'),
+    opencode: (0, path_1.join)(home, '.claude', 'skills'),
+    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', 'commands', 'pkit'),
-    opencode: (0, path_1.join)('.claude', 'commands', 'pkit'),
-    antigravity: (0, path_1.join)('.agent', 'commands', 'pkit'),
+    claude: (0, path_1.join)('.claude', 'skills'),
+    opencode: (0, path_1.join)('.claude', 'skills'),
+    antigravity: (0, path_1.join)('.agent', 'skills'),
 };
 //# sourceMappingURL=paths.js.map

package/dist/shared/paths.js.map

@@ -1 +1 @@
-{"version":3,"file":"paths.js","sourceRoot":"","sources":["../../src/shared/paths.ts"],"names":[],"mappings":";;;AAAA,2BAA6B;AAC7B,+BAA4B;AAE5B,MAAM,IAAI,GAAG,IAAA,YAAO,GAAE,CAAC;AAEvB,4EAA4E;AAC/D,QAAA,oBAAoB,GAAG,IAAA,WAAI,EAAC,SAAS,EAAE,IAAI,EAAE,IAAI,EAAE,UAAU,EAAE,MAAM,CAAC,CAAC;AAEpF,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,kFAAkF;AACrE,QAAA,kBAAkB,GAAG;IAChC,uDAAuD;IACvD,MAAM,EAAE,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,UAAU,EAAE,MAAM,CAAC;IACjD,+CAA+C;IAC/C,QAAQ,EAAE,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,UAAU,EAAE,MAAM,CAAC;IACnD,kDAAkD;IAClD,WAAW,EAAE,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,aAAa,EAAE,UAAU,EAAE,MAAM,CAAC;CAC7D,CAAC;AAEX,+EAA+E;AAClE,QAAA,qBAAqB,GAAG;IACnC,MAAM,EAAE,IAAA,WAAI,EAAC,SAAS,EAAE,UAAU,EAAE,MAAM,CAAC;IAC3C,QAAQ,EAAE,IAAA,WAAI,EAAC,SAAS,EAAE,UAAU,EAAE,MAAM,CAAC;IAC7C,WAAW,EAAE,IAAA,WAAI,EAAC,QAAQ,EAAE,UAAU,EAAE,MAAM,CAAC;CACvC,CAAC"}
+{"version":3,"file":"paths.js","sourceRoot":"","sources":["../../src/shared/paths.ts"],"names":[],"mappings":";;;AAAA,2BAA6B;AAC7B,+BAA4B;AAE5B,MAAM,IAAI,GAAG,IAAA,YAAO,GAAE,CAAC;AAEvB,qEAAqE;AACxD,QAAA,oBAAoB,GAAG,IAAA,WAAI,EAAC,SAAS,EAAE,IAAI,EAAE,IAAI,EAAE,QAAQ,CAAC,CAAC;AAE1E,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,sFAAsF;AACzE,QAAA,kBAAkB,GAAG;IAChC,MAAM,EAAE,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,QAAQ,CAAC;IACvC,QAAQ,EAAE,IAAA,WAAI,EAAC,IAAI,EAAE,SAAS,EAAE,QAAQ,CAAC;IACzC,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,SAAS,EAAE,QAAQ,CAAC;IACnC,WAAW,EAAE,IAAA,WAAI,EAAC,QAAQ,EAAE,QAAQ,CAAC;CAC7B,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tydung26/product-kit",
-  "version": "0.1.4",
+  "version": "1.0.0",
   "description": "🧠 Product management skills kit",
   "bin": {
     "pkit": "bin/pkit.js"
@@ -18,7 +18,7 @@
   },
   "files": [
     "dist/",
-    "commands/",
+    "skills/",
     "bin/",
     "README.md"
   ],

package/skills/discover/SKILL.md

@@ -0,0 +1,131 @@
+---
+name: "pkit:discover"
+description: >
+  Use for product discovery, ideation, exploring solutions, and customer segment
+  slicing. Triggers on: discover, brainstorm, ideate, explore ideas, what if we,
+  what could we build, idea generation, think through options, who is the customer.
+  Do NOT use for writing PRDs (use pkit:product-design), roadmaps
+  (use pkit:roadmap), or market intel (use pkit:market-intel).
+license: MIT
+---
+
+# Discover - Structured Product Ideation
+
+Divergent thinking → customer slicing → clustered themes → top picks with next steps.
+
+**Principles:** Quantity over quality (diverge first) | Ground in real user needs | Be specific, not generic
+
+## Usage
+
+```
+/pkit:discover <product/feature/problem-space>
+```
+
+**Do NOT use for:** Writing PRDs (`/pkit:product-design`), roadmaps (`/pkit:roadmap`), or market intel (`/pkit:market-intel`).
+
+## Workflow Overview
+
+```
+[Clarify Problem] → [Slice Customer Segment] → [Generate 5-10 Ideas] → [Cluster by Theme] → [Top 2-3 Picks] → [Next Steps]
+```
+
+| Step         | Action                                     | Skip if                   |
+| ------------ | ------------------------------------------ | ------------------------- |
+| 1. Clarify   | Ask problem/user/constraints/prior art     | Context already provided  |
+| 2. Slice     | Narrow customer segment via who-where test | Specific segment provided |
+| 3. Diverge   | Generate 5–10 ideas, no filtering          | —                         |
+| 4. Cluster   | Group into 2–4 themes                      | —                         |
+| 5. Recommend | Pick top 2–3, present as table             | —                         |
+| 6. Open door | Offer deeper dives                         | —                         |
+
+## Step Details
+
+### Step 1 — Clarify the Problem Space
+
+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?
+
+### Step 2 — Slice the Customer Segment
+
+Narrow down **who** you're building for. Vague audience → vague ideas.
+
+**Slicing questions (repeat until specific):**
+
+1. Within this customer group, who has the **strongest need**?
+2. Will **everyone** buy/use it, or only a subset?
+3. **Why** do they want this? Underlying motivation?
+4. Is there a **trigger or forcing function** driving them?
+5. What **other groups** share that same motivation?
+
+**Two answer types:**
+
+- **Demographic cluster** — role, company size, geography, etc.
+- **Goal/motivation cluster** — shared objectives and pain drivers
+
+**Keep slicing until you can answer both:**
+
+- **Who** are they? (specific enough to describe a real person)
+- **Where** do you find them? (channels, communities, platforms)
+
+Can't answer "where"? Segment too broad — slice again.
+
+**Pick focus using:** 1) Ability to pay & market size 2) Ease of reach 3) Personal energy
+
+### Step 3 — Diverge: Generate Ideas
+
+Generate **5–10 distinct ideas**. No filtering yet.
+
+Per idea: **Name** | **One-liner** | **Target user** | **Core value prop** | **Biggest risk**
+
+### Step 4 — Cluster by Theme
+
+Group into 2–4 themes. Label each (e.g. "Self-serve automation", "Human-in-the-loop", "Data visibility").
+
+### Step 5 — Recommend Top 2–3
+
+Pick strongest by: user value, feasibility, differentiation, strategic fit.
+
+| Idea | Why Strong | Key Risk | Suggested Next Step |
+| ---- | ---------- | -------- | ------------------- |
+
+### Step 6 — 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
+
+```
+## Target Segment
+
+**Who:** [specific persona]
+**Where:** [channels/communities to reach them]
+**Why them:** [motivation + ability to pay + reachability]
+
+## 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/market-intel/SKILL.md

@@ -0,0 +1,121 @@
+---
+name: "pkit:market-intel"
+description: >
+  Use for competitive analysis, market research, and understanding the competitive
+  landscape. Triggers on: competitive analysis, market intel, 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
+---
+
+# Market Intel - Competitive Landscape Analysis
+
+Scope → competitor profiles → feature matrix → whitespace mapping → strategic recommendations.
+
+**Principles:** Be honest about strengths and gaps | Actionable recs over generic summaries | Evidence over opinion
+
+## Usage
+
+```
+/pkit:market-intel <product/feature/market>
+```
+
+**Do NOT use for:** Internal A/B decisions, roadmap planning (`/pkit:roadmap`), or feature prioritization.
+
+## Workflow Overview
+
+```
+[Scope Analysis] → [Competitor Profiles] → [Feature Comparison] → [Whitespace & Differentiation] → [Strategic Recs]
+```
+
+| Step          | Action                                       | Skip if          |
+| ------------- | -------------------------------------------- | ---------------- |
+| 1. Scope      | Define product, competitors, focus area      | Context provided |
+| 2. Profiles   | Build competitor profiles                    | —                |
+| 3. Compare    | Feature comparison matrix                    | —                |
+| 4. Whitespace | Gaps, table stakes, differentiation, threats | —                |
+| 5. Recommend  | 3 strategic bullets                          | —                |
+
+## Step Details
+
+### 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/product-design/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: "pkit:product-design"
+description: >
+  Use for product design workflow: PRD, brand guidelines, wireframes, moodboards,
+  and design refinement. Triggers on: write a PRD, make a PRD, product design,
+  brand guideline, design spec, feature spec, product requirements, design flow.
+  Do NOT use for roadmap planning (use pkit:roadmap)
+  or discovery/brainstorming (use pkit:discover).
+license: MIT
+---
+
+# Product Design - PRD to Polished Design
+
+End-to-end product design pipeline: research → PRD → brand → wireframes → moodboard → final design.
+
+**Principles:** User pain first, solution second | Be specific, flag unknowns | No implementation details in requirements
+
+## Usage
+
+```
+/pkit:product-design <feature-name>
+```
+
+**Do NOT use for:** Roadmap planning (`/pkit:roadmap`), discovery (`/pkit:discover`), or market intel (`/pkit:market-intel`).
+
+## Workflow Overview
+
+```
+[Clarify] → [Write PRD] → [User Stories] → [Open Questions] → [Next Steps: Brand Guideline]
+```
+
+| Step          | Action                                    | Skip if          |
+| ------------- | ----------------------------------------- | ---------------- |
+| 1. Clarify    | Ask problem/user/success/constraints      | Context provided |
+| 2. PRD        | Write full PRD using template             | —                |
+| 3. Stories    | 3–5 user stories with acceptance criteria | —                |
+| 4. Questions  | Surface all open decisions                | —                |
+| 5. Next steps | Point to Brand Guideline as next step     | —                |
+
+## Step Details
+
+### Step 1 — Clarify (Always First)
+
+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. Existing mockups, data, or research to incorporate?
+
+### Step 2 — Write the PRD
+
+Use template below. Fill every section — no empty placeholders. Flag unknowns as open questions.
+
+### Step 3 — Generate Core User Stories
+
+Write 3–5 user stories:
+
+- Format: "As a [role], I want to [action] so that [benefit]"
+- INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
+- Acceptance criteria in Given/When/Then format
+- Flag edge cases for engineering
+
+### Step 4 — Surface Open Questions
+
+List every decision needed before engineering starts:
+
+- UX decisions not yet resolved
+- Technical approach questions
+- Business rule ambiguities
+- Dependencies on other teams
+
+### Step 5 — Point to Next Steps
+
+Always end with:
+
+> "PRD is done — Step 1 of 6 complete. Next: define your **Brand Guideline** (tone, colors, typography, spacing, icon/image style). Want me to draft one based on this PRD?"
+
+## Product Design Flow
+
+The PRD is Step 1 of a 6-step pipeline from research to polished design:
+
+```
+[1. PRD] → [2. Brand Guideline] → [3. Wireframes] → [4. Moodboard] → [5. Design] → [6. Refine]
+```
+
+| Step               | What                                             | Output                        | Tool             |
+| ------------------ | ------------------------------------------------ | ----------------------------- | ---------------- |
+| 1. Research & PRD  | User needs, pain points, barriers                | PRD document                  | This command     |
+| 2. Brand Guideline | Tone, colors, typography, spacing, icons, images | Brand Guideline doc           | AI-assisted      |
+| 3. Wireframes      | Feed PRD + Brand Guideline → generate screens    | Layout wireframes (not final) | Google Stitch    |
+| 4. Inspiration     | Browse references for specific components        | Moodboard in Figma            | Mobbin, Awwwards |
+| 5. Design          | Wireframe structure + Moodboard style            | Final design                  | Figma            |
+| 6. Refine          | Audit against Brand Guideline                    | Polished, consistent design   | Manual review    |
+
+**Key rules:**
+
+- Step 3 output = **wireframes only** — don't ship as final design
+- Step 4 = search with intent (find references for specific components, not aimless browsing)
+- Step 6 = check spacing, text sizes, components, colors match the guideline
+
+## Quality Checklist
+
+- [ ] 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
+
+## PRD Template
+
+See `templates/prd-template.md` for the full template.

package/skills/roadmap/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: "pkit:roadmap"
+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
+---
+
+# Roadmap - OKR-Driven Product Planning
+
+Context → NOW/NEXT/LATER bucketing → risk register → open decisions → exec narrative.
+
+**Principles:** Tie everything to outcomes | Include confidence levels | Different views for different audiences
+
+## Usage
+
+```
+/pkit:roadmap <product/team/time-horizon>
+```
+
+**Do NOT use for:** Sprint planning, writing PRDs (`/pkit:product-design`), or market intel (`/pkit:market-intel`).
+
+## Workflow Overview
+
+```
+[Gather Context] → [NOW/NEXT/LATER] → [Risk Register] → [Open Decisions] → [Exec Narrative]
+```
+
+| Step         | Action                                   | Skip if          |
+| ------------ | ---------------------------------------- | ---------------- |
+| 1. Context   | Ask horizon, OKRs, constraints, audience | Context provided |
+| 2. Bucket    | NOW/NEXT/LATER with metrics + confidence | —                |
+| 3. Risks     | Top 3–5 risks + mitigation               | —                |
+| 4. Decisions | Unresolved calls blocking the roadmap    | —                |
+| 5. Narrative | 2-paragraph exec summary                 | —                |
+
+## Step Details
+
+### 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]
+```

package/commands/pkit/brainstorm.md

@@ -1,90 +0,0 @@
----
-description: Ideation → clustered themes → top picks with risks and next steps
-argument-hint: <product/feature/problem-space>
----
-
-Brainstorm product ideas or solutions for the given topic.
-<task>$ARGUMENTS</task>
-
----
-
-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 commands.
-
-## 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/commands/pkit/competitive-analysis.md

@@ -1,100 +0,0 @@
----
-description: Competitor profiles → feature matrix → whitespace opportunities
-argument-hint: <product/market> [focus-area]
----
-
-Run a structured competitive analysis for the given product or market.
-<task>$ARGUMENTS</task>
-
----
-
-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/commands/pkit/make-prd.md

@@ -1,177 +0,0 @@
----
-description: Clarifying questions → full PRD → user stories with acceptance criteria
-argument-hint: <feature-name>
----
-
-Write a Product Requirements Document for the given feature.
-<task>$ARGUMENTS</task>
-
----
-
-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 PRD template below. 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
-
-## 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)
-
----
-
-## PRD Template
-
----
-
-# 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/commands/pkit/roadmap-planner.md

@@ -1,98 +0,0 @@
----
-description: NOW/NEXT/LATER roadmap → risk register → exec narrative
-argument-hint: <team/product> [time-horizon]
----
-
-Plan a product roadmap for the given team or product.
-<task>$ARGUMENTS</task>
-
----
-
-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]
-```