Mvp Research
Create an Evidence Pack for a Web MVP. Use after an Idea Brief exists when the user needs competitor research, user/problem evidence, feature prioritization, monetization clues, technical feasibility, and a Go/Narrow/Pause recommendation.
Mvp Tech Design
Create a practical Technical Blueprint for a Web MVP. Use after a buildable PRD exists when the user needs a stack decision, No-code vs AI-code vs Developer route comparison, architecture, setup commands, security baseline, testing plan, and cost/maintenance notes.
Mvp Workflow
Orchestrate a Codex-first Web MVP planning workflow from rough idea to build-ready artifacts. Use when the user wants to turn an app idea into a structured MVP plan, PRD, technical blueprint, AGENTS.md context, and implementation tickets.
Mvp Idea Brief
Create an Idea Brief for a Web MVP. Use when the user has a rough app idea and needs to clarify the target user, problem, current workaround, smallest useful outcome, platform choice, budget, and MVP exclusions before research or PRD work.
Mvp Build Tickets
Generate implementation task tickets for a Web MVP. Use after AGENTS.md and agent_docs exist when the user needs small Codex-executable task files with required reading, scope, acceptance criteria, implementation plan, verification checks, risks, and done conditions.
Mvp Agent Context
Generate Codex-first agent context files for a Web MVP. Use after the PRD and Technical Blueprint exist when the user needs AGENTS.md, REVIEW-CHECKLIST.md, and agent_docs for project brief, requirements, tech stack, page map, data model, build tasks, testing, and reusable prompts.
Mvp Prd
Create a buildable MVP PRD. Use after the Idea Brief and Evidence Pack exist when the user needs pages, user journey, P0/P1 features, acceptance criteria, data objects, success metrics, design direction, risks, and Definition of Done.