Loading...
Loading...
Found 119 Skills
Prevent feature creep when building software, apps, and AI-powered products. Use this skill when planning features, reviewing scope, building MVPs, managing backlogs, or when a user says "just one more feature." Helps developers and AI agents stay focused, ship faster, and avoid bloated products.
Traffic-First opportunity discovery. KILL funnel filters ideas by traffic channel, demand, competition, revenue, interest, MVP-ability. Outputs one idea + one channel recommendation.
Use when a founder has a rough product idea and wants autonomous deep validation, market and competitor research, and an evidence-based MVP decision with minimal back-and-forth.
Compara o template atual com um MVP.md existente, acrescenta seções novas e preserva todo conteúdo já preenchido.
Recomenda arquitetura Laravel, infraestrutura VPS, banco, arquivos, IA, segurança e operação simples para o MVP SaaS.
Product design, feature planning, and technical architecture for new projects. Explores the problem space through deep requirements gathering, suggests creative features, makes architecture decisions, and produces a structured MVP plan with scope boundaries, a future roadmap, and a deliverable tracker. Uses plan mode for deliberate thinking before writing any artifacts. Use when the user says "mvp", "plan a product", "design features", "what should I build", "feature planning", "scope an MVP", or describes a product they want to plan.
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
Interactive, problem-first PRD generator — interviews the user to surface the thesis (the problem, and WHY build it) and a falsifiable hypothesis, then writes a focused PRODUCT-level PRD (problem · evidence · hypothesis · users · MVP · success metrics · non-goals · open questions). Use at the start of a greenfield effort to discuss the product. A PRD is INTENT (what/why), never engineering decisions (how) — those are the `plan-architecture` skill's spec.
Orquestra a entrevista adaptativa para definir o primeiro MVP SaaS, guardar cada resposta e consolidar o plano em MVP.md.
Run structured multi-role design reviews and architecture debates for technical decisions. Use when Codex needs to compare options, pressure-test tradeoffs, recommend an MVP path, or simulate a meeting with distinct evaluation roles such as moderator, skeptic, pragmatist, minimalist, maximalist, retrieval architect, Granary workflow lead, semantic purist, lightweight contrarian, context economist, or workflow conservative.
Gera, atualiza e valida o MVP.md do MVPFy com seções estáveis, estado claro e preservação do conteúdo existente.
Use biological evolution logic (genetic variation + natural selection) to address uncertainty, and iterate products or teams through the cycle of MVP launch → market feedback screening → variation and innovation → accumulating advantages. It applies to scenarios with unclear goals, rapidly changing environments, and inability to plan in advance. It is not suitable for deterministic projects with clear goals and clear paths (planning is more efficient). Planning and evolution are complementary like Yin and Yang: Planning = Yang (efficiency), Evolution = Yin (addressing uncertainty). Key trigger signals: "Unsure what users want", "The market changes too fast", "Plans can't keep up with changes", "Let's get started first"