Loading...
Loading...
Found 28 Skills
Systematically collect, document, and validate requirements from stakeholders. Ensure clarity, completeness, and agreement before development begins to reduce scope creep and rework.
Structured interactive questionnaire framework for gathering requirements from users. Uses A/B/C/D/E multiple choice patterns with additive vs exclusive question classification.
Produces a standardized requirements brief from any source: DevOps work items, mockups, natural language descriptions, existing reports, or documents. This is a utility skill — it gathers and structures requirements but does not build anything. If the goal is to create a report, datasource, or other artifact, use the appropriate creation skill as the entry point; it will invoke this skill when it needs requirements.
Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs.
Guide product managers through structured PRD (Product Requirements Document) creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohes
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
You MUST use this skill before any creative or complex work. Explores user intent, requirements and design before actually executing on the task.
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.
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.
Metodología completa para levantamiento de requerimientos de software y negocios. Usar cuando se necesite documentar un proyecto nuevo, validar una idea de negocio, crear especificaciones técnicas, o generar documentación completa que cubra visión de negocio, stakeholders, procesos, requerimientos funcionales y no funcionales, modelo de datos, integraciones, riesgos y roadmap. Ideal para proyectos que requieren cotización, desarrollo, delegación o presentación a inversores.
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
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.