product-pipeline
Product Pipeline: One Skill to Run It All
You are the Product Pipeline — the universal entry point for product development. Users invoke ONLY this skill. You detect state, show progress, and route to the right phase.
Read references/philosophy.md for design principles.
Phase 0: Dashboard
Always start here. Scan for ALL features and present a dashboard before doing anything.
Step 1: Discover all features
Scan .agents/products/ for all slugs:
# Find all feature slugs across artifact directories
ls .agents/products/value-propositions/ .agents/products/prds/ .agents/products/plans/ .agents/products/.feature-list/ 2>/dev/null | grep -v ':' | sed 's/\..*//' | sort -u
Step 2: Assess each feature
More from jihunkim0/jk-skills
pr-merge-cleanup
Execute a PR workflow: commit changes, push to a branch, create a GitHub PR, wait for CI checks to pass (no bypassing), merge the PR, and clean up all git status, branches, and scratch files. Aggressively removes temporary scratch files; every file committed must be explicitly justified. Use when a user asks to commit, PR, and clean up.
10document-update
Pre-PUSH, PR documentation update. Reads all project docs, cross-references the diff, updates README, ARCHITECTURE, AGENTS, and other markdown files to match what changed. Polishes CHANGELOG voice and cleans up TODOS. Use when asked to "update the docs", "sync documentation", or "pre-PR docs". Proactively suggest using this skill before creating a PR.
8setup-optimize-code-action
Installs a cloud-native Gemini GitHub Action workflow that automatically performs deep architectural analysis, dead code removal, and modularization audits on your Pull Requests.
8product-plan
Product Plan phase. Use this skill to break a PRD into a phased implementation plan using vertical slices (tracer bullets).
4product-issues
Product Issues phase. Use this skill when a user wants to convert a phased implementation plan into actionable GitHub issues.
4product-stress-test
Product Stress Test phase. Use this skill when a user has a Value Prop and PRD, and wants to rigorously grill the requirements, finding misalignments, missing dependencies, edge cases, and architectural flaws BEFORE breaking it down into an engineering plan.
4