From vamfi-software-consultancy
This skill should be used when the user asks to "run discovery", "facilitate a discovery session", "create a discovery document", "map stakeholders", "build an assumption register", "define success metrics", "plan discovery interviews", or needs to structure the initial research phase of an engagement.
npx claudepluginhub vamfi/vamfi-plugins --plugin vamfi-software-consultancyThis skill uses the workspace's default tool permissions.
Facilitate a structured discovery process that surfaces the real problem, maps stakeholders, and builds the foundation for requirements and architecture work.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Facilitate a structured discovery process that surfaces the real problem, maps stakeholders, and builds the foundation for requirements and architecture work.
Discovery is the most leveraged activity in any engagement. Poor discovery produces beautiful solutions to the wrong problem. This skill produces a Discovery Document that becomes the single source of truth for all downstream work.
Define the problem with precision:
Produce a stakeholder map table:
| Name/Role | Interest | Influence | Communication | Interview Priority |
|---|---|---|---|---|
| [Executive sponsor] | [what they care about] | High | Monthly steering | Essential |
| [End user] | [daily pain points] | Low | User testing | Essential |
| [IT/Engineering] | [technical constraints] | Medium | Working sessions | Important |
Interview priority: Essential / Important / Inform-only
For each Essential/Important stakeholder, produce a tailored interview guide:
| # | Assumption | Category | Confidence | Impact if Wrong | Owner | Validation Method |
|---|---|---|---|---|---|---|
| 1 | [assumption] | Technical/Business/User | High/Med/Low | High/Med/Low | [name] | [how to validate] |
Categories: Technical, Business, User, Commercial, Regulatory
Define how success will be measured:
# Discovery Document: [Initiative Name]
Date: [YYYY-MM-DD] | Status: Draft
## Problem Statement
[Precise problem framing]
## Stakeholder Map
[Table]
## Key Discovery Findings
[Themes emerging from interviews/research]
## Assumption Register
[Table]
## Success Metrics
[Table]
## Open Questions
[Questions that remain unanswered after discovery]
## Recommended Next Steps
[What to do with these findings]
If stakeholder interviews are not possible (solo session, internal initiative):
references/interview-question-library.md — Domain-specific question banksassets/discovery-document-template.md — Full blank template