vc-generate-spec
vc-generate-spec turns research findings and user intent into a reviewable requirements document written for stakeholders, not engineers. It captures what users want and why before any implementation approach is chosen, serving as the authoritative bridge between discovery and planning. The skill enforces structured sections—from user stories through acceptance criteria—ensuring specs remain focused on observable outcomes and user-facing behavior.
vc-generate-spec creates a plain-language product requirements document from research findings and user intent for stakeholder sign-off.
AI-generated summary based on this skill's SKILL.md
Install
withkynam/vibecode-pro-max-kit/vc-generate-spec · repository language: JavaScript
git clone https://github.com/withkynam/vibecode-pro-max-kit
cp -r vibecode-pro-max-kit/.claude/skills/vc-generate-spec ~/.claude/skills/vc-generate-specnpx skillfed install withkynam/vibecode-pro-max-kit/vc-generate-specFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does vc-generate-spec turn research into a spec?
vc-generate-spec converts research findings and user intent into a plain-language requirements document written for stakeholder review. It structures your discovery work into user stories, behavioral outcomes, and acceptance criteria—capturing what users want and why before any implementation approach is chosen. The result is a reviewable SPEC artifact that serves as the authoritative bridge between discovery and planning phases.
What sections does vc-generate-spec include in its output?
vc-generate-spec enforces structured sections that move from user intent through testable requirements. Each spec includes user stories, behavioral outcomes, and acceptance criteria organized to remain focused on observable, user-facing behavior. This ensures your requirements document is complete, reviewable, and ready to gate the move into innovation and planning phases.
Can vc-generate-spec create requirements document for product discovery?
Yes. vc-generate-spec is designed to create requirements documents that bridge research discovery and implementation planning. It takes feature ideas and research findings, then produces a gated requirements document with clear scope boundaries. The output is written for stakeholders, not engineers, making it ideal for product discovery workflows.
Who should use vc-generate-spec and when?
vc-generate-spec is for product teams, researchers, and stakeholders who need to formalize discovery work before moving to planning. Use it after research is complete but before implementation begins. It generates acceptance criteria and scope boundaries that ensure everyone agrees on what success looks like—turning brainstorms and findings into a testable, reviewable spec.
What makes vc-generate-spec different from writing specs manually?
vc-generate-spec enforces a consistent structure that captures user intent and behavioral outcomes without jumping to implementation details. It ensures specs remain focused on what users want and why, not how engineers will build it. The skill bridges the gap between discovery and planning by producing a structured, stakeholder-friendly artifact that gates progress into the next phase.
SKILL.md
rendered from the published skill — quoted content, verbatim
Generate SPEC
> Output style: Follow process/development-protocols/communication-standards.md — answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Use this skill to produce the authoritative product-discovery SPEC artifact for a task — a plain-language requirements document written for user review, not for an engineer.
A SPEC captures what the user wants and why so the user can read it, recognize their own intent, and confirm "yes, build that" before any approach or code is chosen. It is the bridge between RESEARCH (the facts) and INNOVATE (the how). PLAN cannot start until a SPEC exists for non-trivial work.
SPEC consumes: RESEARCH findings + the user's stated intent/brainstorm.
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 3 files
.claude/skills/vc-generate-spec/SKILL.md
.claude/skills/vc-generate-spec/references/spec-contract.md
.claude/skills/vc-generate-spec/templates/program-spec-template.md