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
Decision gist · record as of 2026-06-21
vc-generate-spec creates a plain-language product requirements document from research findings and user intent for stakeholder sign-off. 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.
Use it when
- vc-generate-spec enforces structured sections that move from user intent through testable requirements.
- Yes.
Verify before relying
Read SKILL.md below before installing (3 files). Open directory: indexed for reading, not audited.
Install
withkynam/vibecode-pro-max-kit/vc-generate-spec · repository language: JavaScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
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
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Generate a plain-language product spec from research findings and user intent for stakeholder review”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill scaffolds multi-phase programs by generating an umbrella orchestration plan, Program Goal Charter, per-phase plan stubs, and a session-goal block. It enforces a 7-step inner loop (Research → Innovate → Plan-Supplement → PVL → Execute → EVL → Update-Process) with validation gates between phases, ensuring each phase is ready before the next begins. Use it when work naturally breaks into 3+ dependent phases across multiple packages or services.
vc-generate-plan transforms feature ideas and product requirements into structured implementation plan artifacts saved to your repo. It handles both straightforward single-phase work and large multi-phase programs, organizing plans with required sections for touchpoints, contracts, blast radius, and verification gates. The skill enforces answer-first communication and ensures execution handoff clarity through explicit resume notes.
vc-audit-plans scans your active plan inventory to flag stale, completed, or obsolete artifacts and recommend archival or cleanup actions. It validates plan status against your codebase, detects misplaced task artifacts, and surfaces a summary table with classifications and next steps. Use it for periodic maintenance, post-burst reconciliation, or when plan cleanup has drifted.
vc-setup guides you through configuring an agent development harness tailored to your project. It detects your tech stack, asks clarifying questions to understand your codebase, then scaffolds the necessary directory structure and context files—always requesting approval before making changes. Works equally well on new projects and those with existing configurations.
vc-context-discovery is the canonical context-loading entry point for every agent session. It discovers and surfaces all nested files under process folders, extracts frontmatter metadata, and routes context by domain using keyword matching. Use the auto-discovery script or keyword-first routing to load exactly the docs your task needs.
vc-generate-context creates and updates process/context/all-context.md, your project's durable knowledge layer for sharing context across agents. It supports full scans for new projects, delta updates for existing repos, and grouped context generation for organized documentation. Validation scripts ensure routing integrity before context is marked refreshed.
More skills vc-debug (MIT) · verify (MIT)