Loading...
Loading...
Found 66 Skills
Validate Business Requirements Documents (BRD) against Layer 1 MVP schema standards
End-to-end workflow for taking a new tool idea from research to working MVP. Use when the user has an idea for a CLI tool, library, or small project and wants to go from concept to initial implementation. Triggers on "I have an idea for a tool", "build a new CLI", "create a new project", "kickoff new tool", "I want to build", "let's build a new", "新しいツールを作りたい", "CLIを作る".
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.
Trigger: Invoke when you start from scratch with extremely limited resources and need to find the minimum viable entry point first to build a stable base. Common signals include bootstrap, MVP, pilot, first foothold, and small team startup. Trigger when starting from almost nothing and needing a viable foothold before scaling up. Use this skill to build a durable base, start small, and grow from a validated nucleus instead of scattering effort.
Use this skill when the user needs to turn an idea into a buildable spec, write a project scope, create feature requirements, or define an MVP. Covers quick feature specs (10-15 min) for immediate AI builds and full project scopes (1-2 hours) for planning and contractor estimates.
Provides startup advice using Eric Ries' Lean Startup methodology focusing on Build-Measure-Learn cycles, validated learning, and rapid experimentation. Use when advising on MVPs, product iterations, pivot decisions, growth metrics, or when user mentions Lean Startup, Eric Ries, validated learning, or rapid experimentation.
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.
Scaffold a production-ready full-stack monorepo with working MVP features, tests, and CI/CD. Generates complete CRUD functionality, Clerk authentication, and quality gates that run immediately with `bun dev`.
Fullstack development skill using bkend.ai BaaS platform. Covers authentication, data storage, API integration for dynamic web apps. Project initialization with "init dynamic" or "dynamic init". Use proactively when user needs login, database, or backend features without managing servers. Triggers: fullstack, BaaS, bkend, authentication, login feature, signup, database, web app, SaaS, MVP, init dynamic, dynamic init, 풀스택, 인증, 로그인 기능, 회원가입, 데이터베이스, 웹앱, フルスタック, 認証, ログイン機能, データベース, 全栈, 身份验证, 登录功能, autenticación, inicio de sesión, registro, base de datos, fullstack, aplicación web, authentification, connexion, inscription, base de données, fullstack, application web, Authentifizierung, Anmeldung, Registrierung, Datenbank, Fullstack, Web-App, autenticazione, accesso, registrazione, database, fullstack, applicazione web Do NOT use for: static websites, Enterprise-grade systems requiring custom infrastructure.
Ship Faster end-to-end workflow for small web apps (default: Next.js 16.1.1): idea/prototype → foundation gate → design-system.md → lightweight guardrails + docs → feature iteration → optional Supabase + Stripe → optional GitHub + Vercel deploy → optional AI-era SEO (sitemap/robots/llms.txt). Resumable, artifact-first under runs/ship-faster/ (or OpenSpec changes/). Trigger: ship/launch/deploy/production-ready MVP.
Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
Help non-technical stakeholders write clear, scoped requirements documents. Translates business needs into structured specs including user goals, workflows, and success criteria — but first guides the requester through prioritization, scope limits, and MVP phasing to prevent wishlist bloat. Output in Taiwan Traditional Chinese. Use this skill when your boss, PM, or stakeholder wants to define what a feature should do, write a PRD, plan a product, or describe requirements. It is also suitable when someone presents a large feature wishlist and needs help structuring and narrowing down its scope.