product-plan
Product Plan: Engineering Manager Mode
You are a Senior Engineering Manager breaking a PRD into thin, independent vertical slices. Each unit is a demoable, testable path through every layer of the stack.
A plan is ready when an implementer can start confidently without the plan writing code for them. The plan provides architecture, file paths, test scenarios, and sequencing. The implementer provides the actual code.
Phase 0: Warm Start
Ask the user for the feature slug.
Run go run ../../scripts/cmd/assess state --slug=$SLUG. Based on output:
- If
journal.resume_hintexists → present: "Resume from: {hint}?" and skip completed steps. - If
artifacts.plan.exists=true→ inform user plan exists, offer revision or re-plan. Rungo run ../../scripts/cmd/compound retrieve --slug=$SLUG --domain=plan→ load relevant learnings.
Emit: go run ../../scripts/cmd/events emit --slug=$SLUG --skill=plan --type=phase_start --payload='{"phase":"plan"}'
Classify plan depth from PRD scope and announce to user:
| Depth | When | Ceremony |
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.
8optimize-code
Deep architectural analysis, aggressive cleanup, modularization, and test enforcement — ruminate on the codebase to identify dead code, redundancies, duplicated logic, over-abstractions, test gaps, and files exceeding 300 lines that need splitting. Systematically eliminate waste, enforce modular architecture, and ensure all functionality has corresponding integration tests. Use whenever the user asks to optimize, slim down, clean up, audit, deduplicate, tighten, or modularize a codebase. Also use when asked to find dead code, reduce line count, eliminate redundancies, split large files, enforce architecture, make code leaner, or audit test coverage. Triggers on phrases like 'audit the codebase', 'clean up', 'find dead code', 'deduplicate', 'make it leaner', 'trim the fat', 'optimize code', 'tidy up', 'remove redundancies', 'refactor for maintainability', 'modularize', 'split large files', 'architecture review', 'files are too big', or 'break this up'. Proactively suggest using this skill before creating a PR.
8product-implement
Product Implement phase. Use this skill when a user wants to execute a planned feature by fetching unblocked tickets from Linear/GitHub, dispatching isolated subagents via git worktrees, and executing a strict TDD loop.
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-pipeline
Product Factory — the single entry point for all product development. Detects where you are, shows a dashboard, and routes to the right phase. Handles ideation, discovery, PRD, vision, stress test, plan, deepening, issues, implementation, and feature-complete ceremony. Invoke at any stage — it picks up where you left off.
7