{"enrichment":{"faq":[{"a":"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\u2014capturing 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.","q":"How does vc-generate-spec turn research into a spec?"},{"a":"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.","q":"What sections does vc-generate-spec include in its output?"},{"a":"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.","q":"Can vc-generate-spec create requirements document for product discovery?"},{"a":"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\u2014turning brainstorms and findings into a testable, reviewable spec.","q":"Who should use vc-generate-spec and when?"},{"a":"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.","q":"What makes vc-generate-spec different from writing specs manually?"}],"shadow_tags":["requirements-artifact","product-discovery","spec-authoring","pre-planning","user-intent-capture","behavioral-outcomes","acceptance-criteria","phase-gating","artifact-generation"],"summary_rewrite":"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\u2014from user stories through acceptance criteria\u2014ensuring specs remain focused on observable outcomes and user-facing behavior."},"files":[{"bytes":5537,"path":".claude/skills/vc-generate-spec/SKILL.md","sha256":"be89c067223abc735be1112717efb808e0a15c89c7874ffe1c5f6ea6769e7838","url":"https://skillfed.io/files/withkynam/vibecode-pro-max-kit/vc-generate-spec/40640db8/SKILL.md"}],"id":"withkynam/vibecode-pro-max-kit/vc-generate-spec","links":{"html":"https://skillfed.io/withkynam/vibecode-pro-max-kit/vc-generate-spec","md":"https://skillfed.io/withkynam/vibecode-pro-max-kit/vc-generate-spec.md","repo":"https://github.com/withkynam/vibecode-pro-max-kit"},"meta":{"agents_supported":["claude-code"],"first_seen":"2026-07-28","forks":219,"language":"JavaScript","last_updated":"2026-06-21","license":"MIT","name":"vc-generate-spec","publisher":"withkynam","stars":1058},"relations":{"categories":["product-management","requirements-engineering","discovery"],"similar":[{"id":"withkynam/vibecode-pro-max-kit/vc-generate-phase-program"},{"id":"withkynam/vibecode-pro-max-kit/vc-generate-plan"},{"id":"withkynam/vibecode-pro-max-kit/vc-generate-closeout"},{"id":"withkynam/vibecode-pro-max-kit/vc-feasibility-test"},{"id":"withkynam/vibecode-pro-max-kit/vc-agent-strategy-compare"},{"id":"withkynam/vibecode-pro-max-kit/vc-audit-plans"},{"id":"withkynam/vibecode-pro-max-kit/vc-review-situation"},{"id":"withkynam/vibecode-pro-max-kit/vc-context-discovery"},{"id":"kdlbs/kandev/spec"},{"id":"withkynam/vibecode-pro-max-kit/vc-validate-findings"}]},"slug":{"owner":"withkynam","repo":"vibecode-pro-max-kit","skill":"vc-generate-spec"},"version":"40640db8"}