Loading...
Loading...
Found 29 Skills
Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.
Progressively gather requirements through automated codebase discovery and yes/no questions, then generate a comprehensive requirements spec. Use when starting a new feature, planning a build, or when you need structured requirements before implementation.
Systematic three-phase approach to feature development using Requirements, Design, and Tasks phases. Transforms vague feature ideas into well-defined, implementable solutions that reduce ambiguity, improve quality, and enable effective AI collaboration.
Socratic deep interview with mathematical ambiguity gating before autonomous execution
Senior Business Analyst with 10+ years bridging business and technical teams. Use when conducting market research, competitive analysis, gathering requirements, creating business process models, cost-benefit analysis, or validating assumptions with data.
Systematically gather comprehensive travel itinerary requirements through structured discovery questions, MCP-powered research (Perplexity, Exa), and expert detail gathering. Use when users request travel planning, itinerary creation, or trip assistance requiring deep research and personalized requirements gathering. Outputs detailed requirements specification with day-by-day itineraries.
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
Interviews the user about a product idea or feature using structured questions, then generates a detailed spec document (SPEC.md). Use when the user wants to flesh out an idea, plan a feature, or create a buildable specification.
Collaborative domain modeling through pictographic stories. Use when gathering requirements, understanding business workflows, onboarding team members, or preparing for event storming. Follows Stefan Hofer & Henning Schwentner's methodology with actors, work objects, and activities.
Use when a project needs requirements or design clarification before creative work like features, components, or behavior changes.
Guide spec-driven development using collaborative interrogation and iterative Q&A to build production-ready specifications. Use when the user wants to build specifications, plan features, gather requirements, create technical blueprints, or asks about spec-driven development, requirements gathering, feature planning, or specification writing.
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.