Vc Generate Spec
Create or update a product-discovery SPEC (requirements doc) for user review.
Install
npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-spec -g -a claude-code -y- Repository
- withkynam/vibecode-pro-max-kit1.2k
- Category
- Writing
- Updated
- 5mo ago
- License
- MIT
- Context cost
- Lightabout 1,264 tokens
- Runs scripts
- No, instructions only
What it does
Create or update a product-discovery SPEC (requirements doc) for user review. Use when turning RESEARCH findings plus user intent into a reviewable requirements artifact before INNOVATE/PLAN.
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. It does NOT consume a chosen approach or a Decision Summary, no approach exists yet at SPEC time.
Normal output is one SPEC file: {slug}_SPEC_{dd-mm-yy}.md.
For a phase program, the program-level (umbrella) SPEC is written once during the outer loop and governs every inner phase. Use templates/program-spec-template.md for that case. The inner loop never writes a SPEC.
