New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vc Generate Spec

by withkynam in withkynam/vibecode-pro-max-kit

Create or update a product-discovery SPEC (requirements doc) for user review.

MITAuto-check passedProduct & Project Management

Install Vc Generate Spec

skills CLI
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install withkynam/vibecode-pro-max-kit vc-generate-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vc-generate-spec .claude/skills/vc-generate-spec && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vc-generate-spec
GitHub stars
1.1k
Token cost
~1.4k tokens
SKILL.md length
670 words
Files
3 (incl. references)
Skills in repo
32
Repo updated
First seen
Licence
MIT

At a glance

Create or update a product-discovery SPEC (requirements doc) for user review.

  • Works in 10 steps: Read references/spec-contract.md for the… → Run date +%d-%m-%y before choosing the… → Confirm the inputs are present: RESEARCH… → …
  • Turning RESEARCH findings plus user intent into a reviewable requirements artifact before INNOVATE/PLAN
  • SKILL.md covers Workflow, Important Rules and Required SPEC Sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vc Generate Spec is an agent skill from withkynam/vibecode-pro-max-kit. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/spec-contract.md` and `templates/program-spec-template.md`).

It sits in Product & Project Management. The repository describes itself as: Your AI forgets. This remembers. Spec-driven coding harness for vibecoders, product owners, CEOs and real builders — self-improving context memory, 15 agents, 33 skills working…. The licence is MIT.

When your agent uses it

  • Turning RESEARCH findings plus user intent into a reviewable requirements artifact before INNOVATE/PLAN

Example prompts

  • “/vc-generate-spec”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Read references/spec-contract.md for the full section-by-section writing rules.
  2. Run date +%d-%m-%y before choosing the filename.
  3. Confirm the inputs are present: RESEARCH findings + the user's stated intent. If neither is present, emit SPEC_INTENT_BLOCKED instead of…
  4. Read process/context/all-context.md first, then load the relevant context group. When the work touches testing/verification, read…
  5. Save the SPEC inside the task folder alongside the plan: process/features/{feature}/active/{slug}_{date}/{slug}_SPEC_{date}.md (or…
  6. Write the SPEC sections in canonical order (see references/spec-contract.md)
  7. Keep the document oriented for user review: plain language, no file paths, no library names, no schema or code. Anything engineer-only…
  8. Each acceptance criterion MUST be provable by comprehensive tests, with a fully-automated E2E/integration gate wherever the behavior is…
  9. If ## Open Questions is non-empty at finalize (interactive session): emit SPEC_INTENT_BLOCKED and stop. Under /goal: record each as a…
  10. Once Open Questions is empty/"None" (or backlogged under /goal): save the file and the agent emits PHASE_COMPLETE: SPEC.

What it can do on your machine

Read from SKILL.md and the folder at commit 3bcb2f9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vc Generate Spec loads about 1.4k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 670 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from withkynam/vibecode-pro-max-kit at commit 3bcb2f9, republished under its MIT licence (© withkynam). 670 words, ~1,378 tokens.

Download SKILL.mdSave it as .claude/skills/vc-generate-spec/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
vc-generate-spec
description
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.
argument-hint
[feature idea or task slug]
trigger_keywords
spec, requirements doc, product discovery, what and why, requirements artifact
layer
contract
metadata.author
vibecode-pro-max-kit
metadata.version
1.0.0

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.

Workflow

  1. Read references/spec-contract.md for the full section-by-section writing rules.
  2. Run date +%d-%m-%y before choosing the filename.
  3. Confirm the inputs are present: RESEARCH findings + the user's stated intent. If neither is present, emit SPEC_INTENT_BLOCKED instead of writing.
  4. Read process/context/all-context.md first, then load the relevant context group. When the work touches testing/verification, read process/context/tests/all-tests.md so acceptance-criteria scenarios are grounded in the real test-context chain.
  5. Save the SPEC inside the task folder alongside the plan: process/features/{feature}/active/{slug}_{date}/{slug}_SPEC_{date}.md (or process/general-plans/active/{slug}_{date}/{slug}_SPEC_{date}.md). For a phase program, the umbrella task folder holds {program-slug}_SPEC_{date}.md. Per task-folder artefact colocation, never write to the deprecated sibling reports/ or references/ dirs.
  6. Write the SPEC sections in canonical order (see references/spec-contract.md):
    • ## Summary
    • ## User Stories / Jobs To Be Done
    • ## What The User Wants (Behavioral Outcomes)
    • ## Flow / State Diagram (ASCII)
    • ## Acceptance Criteria (Testable Outcomes) — each criterion carries proven by: + strategy:
    • ## Out Of Scope
    • ## Constraints
    • ## Open Questions
    • ## Background / Research Findings
  7. Keep the document oriented for user review: plain language, no file paths, no library names, no schema or code. Anything engineer-only moves to Background or a later phase.
  8. Each acceptance criterion MUST be provable by comprehensive tests, with a fully-automated E2E/integration gate wherever the behavior is automatable. Agent-Probe / Known-Gap stand only as an explicitly-justified residual. Vacuous-green is banned.
  9. If ## Open Questions is non-empty at finalize (interactive session): emit SPEC_INTENT_BLOCKED and stop. Under /goal: record each as a backlog note and continue.
  10. Once Open Questions is empty/"None" (or backlogged under /goal): save the file and the agent emits PHASE_COMPLETE: SPEC.
Show full SKILL.md (258 more words)Show less

Important Rules

  • The SPEC is written for a human reviewer. If a sentence only makes sense to an engineer, rewrite it or move it to Background.
  • Do NOT choose an implementation approach (INNOVATE's job, downstream), write implementation steps (PLAN), make schema decisions, or include code/library references.
  • Do NOT modify any file except the SPEC file being created.
  • Acceptance-criteria scenarios must be grounded in the RESEARCH test-context-discovery, not invented here.
  • Once INNOVATE/PLAN begins the SPEC is frozen — later scope gaps go to the phase report ## SPEC Gaps heading and a backlog note, never an edit to the SPEC.
  • For a phase program, write the umbrella SPEC once; the inner loop reads it and never writes a per-phase SPEC.

Required SPEC Sections

Every SPEC file must include all of the following, in this order:

  • ## Summary — one plain-language paragraph: what changes for the user and why
  • ## User Stories / Jobs To Be Done — the heart of the doc; "As a [user], I want [X], so that [Y]" or JTBD
  • ## What The User Wants (Behavioral Outcomes) — observable behavior only, no implementation
  • ## Flow / State Diagram — at least one ASCII flow/state diagram
  • ## Acceptance Criteria (Testable Outcomes) — observable outcomes, each with proven by: + strategy:; max 20
  • ## Out Of Scope — at least one item
  • ## Constraints — user-stated, system/process, and technical limits from research
  • ## Open Questions — each with an owner; empty/"None" required to finalize (interactive)
  • ## Background / Research Findings — key facts from RESEARCH that shaped the requirements

Use Markdown-structured sections, not a second machine-only schema. Markdown sections are stable across all agents (Claude, Codex, future systems) without requiring a parser.

© withkynam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .claude/skills/vc-generate-spec of withkynam/vibecode-pro-max-kit.

  • SKILL.md
  • references/spec-contract.md
  • templates/program-spec-template.md

Open the folder on GitHubat commit 3bcb2f9

Compare with similar skills

Vc Generate Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vc Generate Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vc Generate Spec this skillwithkynam/vibecode-pro-max-kit1.1k—~1.4kAutomated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1148 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    114 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Self Improving Agent

    farm-fe/farm

    A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes

  • Weekly Engineering Retro

    garrytan/gstack

    Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from withkynam/vibecode-pro-max-kit

All 32 skills in this repo

  • Library Documentation Seeker

    withkynam/vibecode-pro-max-kit

    Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.

    1.1k GitHub starsUsed in 2 repos~1k tokens
    Auto-check: notes

  • Vc Sequential Thinking

    withkynam/vibecode-pro-max-kit

    Apply step-by-step analysis for complex problems with revision capability.

    1.1k GitHub starsUsed in 2 repos~854 tokens
    Auto-check passed

  • Agent Browser Automation

    withkynam/vibecode-pro-max-kit

    Drives a browser through the agent-browser CLI, using compact snapshots with element refs to keep context small in long sessions, plus video recording and cloud browsers.

    1.1k GitHub stars~2.6k tokensUpdated 3 mo ago
    Auto-check passed

  • Context Routing Audit

    withkynam/vibecode-pro-max-kit

    Audits a project's context routing, skill discoverability and skill wiring by running a chain of validator scripts and fixing whatever they report.

    1.1k GitHub stars~1.2k tokensUpdated 3 mo ago
    Auto-check passed

  • Active Plan Audit

    withkynam/vibecode-pro-max-kit

    Reviews a codebase's active plan files for staleness and completion, then archives only the ones confirmed done or obsolete against the real code.

    1.1k GitHub stars~757 tokensUpdated 3 mo ago
    Auto-check passed

  • Systematic Debugging and Investigation

    withkynam/vibecode-pro-max-kit

    Forces root-cause investigation before any fix, combining a four-phase debugging method with log, CI and performance investigation techniques and a rule against unverified completion claims.

    1.1k GitHub stars~1.5k tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about Vc Generate Spec

What does Vc Generate Spec do?

Create or update a product-discovery SPEC (requirements doc) for user review. Vc Generate Spec is an agent skill from withkynam/vibecode-pro-max-kit. Create or update a product-discovery SPEC (requirements doc) for user review.

When should I use Vc Generate Spec?

Vc Generate Spec fits situations like: turning RESEARCH findings plus user intent into a reviewable requirements artifact before INNOVATE/PLAN.

How do I install Vc Generate Spec in Claude Code?

Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-spec -a claude-code`. Or copy the skill folder (.claude/skills/vc-generate-spec in withkynam/vibecode-pro-max-kit) into .claude/skills/vc-generate-spec in your project. Claude Code loads it when a task matches its description.

How do I install Vc Generate Spec in Codex?

Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-spec -a codex`. Or copy the skill folder (.claude/skills/vc-generate-spec in withkynam/vibecode-pro-max-kit) into .agents/skills/vc-generate-spec in your project. Codex loads it when a task matches its description.

Can I use Vc Generate Spec in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vc-generate-spec, .gemini/skills/vc-generate-spec, .github/skills/vc-generate-spec and .opencode/skills/vc-generate-spec in your project.

What does Vc Generate Spec need to run?

SKILL.md names no scripts, command-line tools or credentials: Vc Generate Spec is instructions for the agent only.

Does Vc Generate Spec access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vc Generate Spec safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vc Generate Spec use?

Vc Generate Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vc Generate Spec use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Vc Generate Spec?

Skills that share tags, products or a category with Vc Generate Spec: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vc Generate Spec?

withkynam (a GitHub user) maintains it in withkynam/vibecode-pro-max-kit, which has 1,145 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on June 21, 2026.

Source: withkynam/vibecode-pro-max-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.