Menú
Display current product development project state and suggest next steps. Deterministic — reads .product-dev/context.json.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Reverse-pass UX audit of an existing product: extract problem, personas, journeys, and value props from its repository, validate with the owner, and produce a prioritized optimization spec. Entry point for products built without formal UX artifacts.
Map user flows, define screens and states, plan prototype scope, design test questions, and synthesize test results. Covers Phases 04-06 of the UX research workflow. Use when the user has a solution concept and hypothesis and wants to plan flows, scope a prototype, or analyze user-testing results.
Guide early-stage product exploration from vague idea through problem definition, objectives, solution concept, and testable hypothesis. Covers Phases 00-03 of the UX research workflow. Use when the user wants to explore a product idea, define a problem worth solving, or turn a rough concept into a falsifiable hypothesis.
Map user flows, define screens and states, plan prototype scope, design test questions, and synthesize test results. Covers Phases 04-06 of the UX research workflow.
Guide early-stage product exploration from vague idea through problem definition, objectives, solution concept, and testable hypothesis. Covers Phases 00-03 of the UX research workflow.
Generate technical specifications from established design artifacts. Produces data models, API contracts, business rules, and non-functional requirements. Spawns the Tech Spec Writer subagent.
| name | status |
| description | Display current product development project state and suggest next steps. Deterministic — reads .product-dev/context.json. |
| user-invocable | true |
| allowed-tools | Read Glob |
Display the current product development project status. This is primarily deterministic — no LLM generation needed for core display.
Read .product-dev/context.json from the working directory.
If no project exists:
"No product development project found in this directory. Run
/product-dev:ideato start one."
If project exists, display:
Project: {project_name}
Tier: {tier} ({tier_label})
Started: {created}
Last updated: {updated}
Phase Progress:
00 Fuzzy Front End [{completed}/{total}] {progress_bar}
01 Define Problem [{completed}/{total}] {progress_bar}
02 Objectives [{completed}/{total}] {progress_bar}
03 Solution Hypothesis [{completed}/{total}] {progress_bar}
04 User Flow [{completed}/{total}] {progress_bar}
05 Prototype [{completed}/{total}] {progress_bar}
06 Post-Test Synthesis [{completed}/{total}] {progress_bar}
Tech Requirements [{completed}/{total}] {progress_bar}
Artifacts:
{name} (from {source_prompt}, {date})
...
Suggested Next:
{list prompts whose `requires` are all satisfied by existing artifacts}
Tier labels: 1 = "Quick Exploration", 2 = "Structured Discovery", 3 = "Full Framework".
Count only prompts matching the current tier level for progress calculations.
For suggested next steps, check each unexecuted Tier 1 prompt's requires array against existing artifacts. List those that are unblocked.