Why these five roles
The shortlist follows a common solo-founder sequence: decide, plan, build the interface, verify the critical path, and make the result understandable to search engines and people. Each role owns a different artifact so overlap stays visible.
This is a source-reviewed workflow, not a promise that five packages will create a business. Customer evidence, distribution, pricing, security, legal obligations, and production operations remain founder responsibilities.
1. grill-me — pressure-test the product decision
Use grill-me to surface assumptions, missing choices, and weak tradeoffs before code becomes sunk cost. End with a short decision record: target user, painful job, smallest promise, exclusions, and the next falsifiable check.
Do not mistake an Agent interview for customer discovery. Replace its assumptions with interviews, observed behavior, or real usage data as soon as possible.
2. create-implementation-plan — turn scope into phases
create-implementation-plan produces atomic phases, dependencies, checks, and risks. It is useful after the product decision is narrow enough to plan without inventing half the roadmap.
Reject plans that hide unresolved product questions inside technical tasks or expand beyond the smallest testable release.
3. frontend-design — make the first impression credible
frontend-design gives the interface an intentional visual concept and implementation direction. For an MVP, constrain it to the primary action, real copy, required states, and the smallest component surface.
Visual confidence cannot compensate for a broken promise. Keep accessibility, load time, and task clarity ahead of decorative complexity.
4. webapp-testing — prove one critical path
webapp-testing provides browser-level evidence for a short acceptance flow. A founder should begin with the action that creates value—signup alone rarely qualifies—and preserve console or screenshot evidence for failures.
One passing flow does not cover production data, payments, security, mobile devices, or every browser. State exactly what was and was not tested.
5. ai-seo — make the launch understandable
ai-seo covers technical and editorial search work for product-led teams. Use it after the product, audience, and page promise are real enough to describe without keyword fabrication.
SEO is a distribution layer, not demand proof. Avoid scaled pages that repeat the same claim, and measure qualified visits and product actions instead of impressions alone.
A seven-day MVP sequence
Day one challenges the decision; day two freezes the smallest plan; days three to five build the primary interface; day six verifies the critical path; day seven publishes one honest, search-readable landing page. The schedule is a forcing function, not a universal estimate.
Stop and narrow the scope whenever a role cannot name its output, reviewer, acceptance check, and rollback. The smallest explainable stack usually moves faster than a collection of overlapping helpers.
- One target user and job are explicit.
- The plan has a smallest release and exclusions.
- The primary interface includes empty, loading, error, and success states where relevant.
- One value-producing flow has browser evidence.
- The launch page makes no claim the product cannot support.