kvokov/discovery-interview
skills/discovery-interview/SKILL.md
Conduct an interactive discovery interview to produce a structured product specification. Triggers: write a spec, PRD, feature spec, requirements, product requirements, scope a project, brainstorm a feature, flesh out an idea, plan a new project. Uses AskUserQuestion for all user choices; WebSearch/WebFetch when the user wants research. Outputs: user stories, acceptance criteria, technical constraints, prioritized requirements in docs/specs/ per SPEC_TEMPLATE.md. Do NOT use for: implementation, code review, debugging, refactors, or when the user already has a complete spec they only want edited.
$ install --global
skillsauthnpx skillsauth add kvokov/oh-my-ai discovery-interviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 2:52 AM27.9s7 files scanned
SKILL.md
- name:
- discovery-interview
- description:
- Conduct an interactive discovery interview to produce a structured product specification. Triggers: write a spec, PRD, feature spec, requirements, product requirements, scope a project, brainstorm a feature, flesh out an idea, plan a new project. Uses AskUserQuestion for all user choices; WebSearch/WebFetch when the user wants research. Outputs: user stories, acceptance criteria, technical constraints, prioritized requirements in docs/specs/ per SPEC_TEMPLATE.md. Do NOT use for: implementation, code review, debugging, refactors, or when the user already has a complete spec they only want edited.
- version:
- 1.0.5
- tags:
- discovery, product-spec, PRD, requirements, AskUserQuestion, interviews, specs
Discovery Interview
Turn vague ideas into an implementable spec through ordered phases and targeted questions.
Non-negotiables (do not skip)
-
Run all 7 phases in order below. Do not jump to the spec early.
-
Minimum 10–15 questions across categories for any real project. Never treat 3–5 questions as enough.
-
Every AskUserQuestion must include an option for uncertainty (e.g. "I'm not sure" / "Research this").
Example AskUserQuestion call:
AskUserQuestion( question: "Which database are you planning to use?", options: ["PostgreSQL", "MySQL", "MongoDB", "I'm not sure", "Research this for me"] ) -
At least one research loop for any non-trivial project (user accepts research → WebSearch/WebFetch or agent, then follow-up questions).
Example research loop: User selects "Research this for me" on a scaling question →
WebSearch("serverless vs container hosting cost comparison 2024")+WebFetch(top result)→ follow-up: "Based on the research, AWS Lambda looks cost-effective at your expected traffic. Does that align with your budget?" -
Completeness check (Phase 5) must pass before writing the spec. If anything is missing, ask more; do not write the spec yet.
-
Summarize your understanding and get user confirmation before generating the spec file.
-
Write the spec to
docs/specs/YYYY-MM-DD-<name>.mdusing SPEC_TEMPLATE.md. Createdocs/specs/if it does not exist.
Process
Execute phases in order. Detailed steps live in companion rules:
| Phase | Focus | Rules | |-------|--------|--------| | 1 | Initial orientation | orientation-and-deep-dive | | 2 | Category deep dive | orientation-and-deep-dive | | 3 | Research loops | research-and-conflict-resolution | | 4 | Conflict resolution | research-and-conflict-resolution | | 5 | Completeness check | completeness-spec-and-handoff | | 6 | Spec generation | completeness-spec-and-handoff | | 7 | Implementation handoff | completeness-spec-and-handoff |
Integrated flow (one pass)
Orientation → deep dive categories for the project type → if unsure on stack/approach, research loop → if two goals conflict, conflict resolution → completeness table green → confirm summary → write spec file → handoff question.
Anti-patterns
- Writing the spec after a handful of questions.
- Skipping research when the user is guessing about tools or scale.
- Leaving contradictions unresolved.
- Writing the spec before the completeness check passes.
Related Skills
kvokov/nestjs
tools
VerifiedTrustedCommunity
NestJS (Nest.js) production patterns for modules, controllers, providers, guards, interceptors, pipes, middleware, JWT, ValidationPipe, microservices, GraphQL, Bull queues, Prisma, and TypeORM. Triggers: NestJS, Nest.js, Nest module, dependency injection, class-validator DTO, exception filter, testing module, GraphQL resolver, Bull queue, microservice client. Uses: Read, Grep, Glob, Bash, WebSearch. Outputs: tier-ordered review checklists and/or concrete code edits with cited rule filenames. Do NOT use for: non-Nest backends (Express/Fastify only with no Nest integration), frontend-only frameworks, generating AGENTS.md, or toolchain setup unrelated to Nest.
4SKILL.mdUpdated May 1, 2026
kvokov/uiux
development
VerifiedTrustedCommunity
Professional UI/UX design skill for React, Next.js, Tailwind CSS, React Native, and Flutter. Use when the user asks to create or polish UI components (modals, forms, tables, charts, navbars, sidebars, cards), design landing pages, build dashboards or admin panels, set up SaaS or mobile app screens, review or fix layout and accessibility issues, configure dark mode or responsive breakpoints, or establish a design system with tokens and component specs. Capabilities include: creating design-system token files and MASTER.md artifacts, generating responsive Tailwind layouts, scaffolding page-level component hierarchies, reviewing and fixing UI accessibility (a11y, WCAG), implementing React Native safe-area screens, and configuring Flutter ThemeData. Outputs design-system files (MASTER, page overrides, tokens, component specs) plus stack-faithful code. Do NOT use for: pure backend-only work with no UI impact, or inventing branding assets you do not have rights to use.
3SKILL.mdUpdated Apr 23, 2026
kvokov/skill-maker
tools
VerifiedTrustedCommunity
Use this skill any time someone wants to create, scaffold, build, fix, improve, benchmark, or optimize a Tessl/Claude skill — even if they don't say 'tessl' explicitly. If the request involves making a new skill ('create a skill for X', 'build me a skill that does Y', 'scaffold a skill called Z'), fixing or completing an existing one (missing tile.json, broken repo integration, low eval scores, description not triggering), or running and iterating on evals, invoke this skill. The full workflow covers: structured interview → SKILL.md + tile.json + rules/ scaffolding → README/CI repo integration → tessl tile lint → optional Tessl CLI pipeline (skill review, scenario generate/download, eval run) → hand-authored evals or LLM-as-judge fallback → benchmark logging. Do NOT use for: editing application code, debugging, refactoring, writing general documentation, or creating presentations.
3SKILL.mdUpdated Apr 23, 2026
kvokov/reading-synthesis
tools
VerifiedTrustedCommunity
Rigorous thirteen-part synthesis of a text or talk: deep summary, insights, structure, critique, framework rebuild, and CEO-level takeaways. Triggers: reading synthesis, synthesize this, deep dive, rigorous analysis, deconstruct, book analysis, article analysis, essay breakdown, intellectual synthesis, multi-dimensional analysis, executive summary of ideas, framework extraction. Uses: Read (and related file tools) for attached sources; WebSearch or WebFetch when comparands are missing or context is thin. Outputs: single structured markdown message with fixed section headers per rules/output-sections.md.
3SKILL.mdUpdated Apr 23, 2026