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

Spec

by jvm-skills in jvm-skills/jvm-skills

Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed.

Apache-2.0Auto-check passedProduct & Project Management

Install Spec

skills CLI
$ npx skills add jvm-skills/jvm-skills --skill spec -a claude-code

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

GitHub CLI
$ gh skill install jvm-skills/jvm-skills 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/jvm-skills/jvm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.junie/skills/spec .claude/skills/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
spec
GitHub stars
139
Token cost
~832 tokens
SKILL.md length
372 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed.

  • Works in 4 steps: Mining the conversation: Extract every… → Exploring the codebase: Look at existing… → Reading project docs: Check docs/ for… → …
  • Has already described what they want (in the current conversation
  • SKILL.md covers How to gather information, Required coverage, Output format and Project Customization
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spec is an agent skill from jvm-skills/jvm-skills. Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed. Use this when the user has already described what they want (in the current conversation, a doc, or a plan) and just needs it formalized into a spec. Also use when the user says "write a spec", "create a spec", "spec this out", or similar.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering User stories and PRD writing. The licence is Apache-2.0.

When your agent uses it

  • Has already described what they want (in the current conversation
  • A plan) and just needs it formalized into a spec
  • The user says write a spec

Example prompts

  • “write a spec”
  • “create a spec”
  • “spec this out”
  • “/spec”

Workflow steps

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

  1. Mining the conversation: Extract every detail the user has already shared — requirements, constraints, examples, preferences, edge cases…
  2. Exploring the codebase: Look at existing patterns, related features, navigation structure, roles, and state management to fill gaps. Check…
  3. Reading project docs: Check docs/ for architecture docs, onboarding flows, and existing specs that inform the design.
  4. Making reasonable assumptions: Where information is genuinely missing and can't be inferred from codebase/docs, state your assumption…

What it can do on your machine

Read from SKILL.md and the folder at commit c6d477f. 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 (its code samples are markdown).

    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

Spec loads about 832 tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 372 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~832

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 jvm-skills/jvm-skills at commit c6d477f, republished under its Apache-2.0 licence (© jvm-skills). 372 words, ~832 tokens.

Download SKILL.mdSave it as .claude/skills/spec/SKILL.md (or your agent's skills folder).
name
spec
description
Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed. Use this when the user has already described what they want (in the current conversation, a doc, or a plan) and just needs it formalized into a spec. Also use when the user says "write a spec", "create a spec", "spec this out", or similar.

Generate a comprehensive feature spec with user stories by synthesizing information already available in context — conversation history, referenced documents, and codebase exploration. Skip any interview or Q&A phase.

How to gather information

Instead of asking the user questions, proactively resolve unknowns by:

  1. Mining the conversation: Extract every detail the user has already shared — requirements, constraints, examples, preferences, edge cases mentioned in passing.
  2. Exploring the codebase: Look at existing patterns, related features, navigation structure, roles, and state management to fill gaps. Check controllers, services, templates/views, and domain logic relevant to the feature.
  3. Reading project docs: Check docs/ for architecture docs, onboarding flows, and existing specs that inform the design.
  4. Making reasonable assumptions: Where information is genuinely missing and can't be inferred from codebase/docs, state your assumption explicitly in the spec (mark with "Assumption:").

Required coverage

The spec must address all of these, even if the user didn't mention them explicitly — infer from codebase patterns:

  • Entry points: Where does the user navigate FROM? What existing page/nav/button changes?
  • User journey: Complete flow from discovery → interaction → completion → return
  • Roles: Which roles interact? Identify all user roles from the codebase (or check references/project.md).
  • Edge cases: Error states, empty states, concurrent access, mobile vs desktop
  • State transitions across roles: Which roles see each change? How (real-time — SSE/websockets, polling, refresh)? What does each role's screen show before/after?
  • Terminal states: What does the user do next at every end-state? Every screen must have a forward action. URL params, cookies, or tokens needed?
Show full SKILL.md (124 more words)Show less

Output format

Write the spec to docs/dev/YYYY-MM-DD-hh-mm_spec-<feature-name>.md and open it with idea (or your editor).

The spec must end with a structured ## User Stories section:

markdown
## User Stories

- **US-1**: As a [role], I [action] so that [outcome].
- **US-2**: As a [role], I [action] so that [outcome].
...

Rules for user stories:

  • Every user role that interacts with the feature must have at least one story
  • Navigation/entry point stories come FIRST
  • Cover the happy path, key error states, and edge cases
  • Stories must be specific enough to verify — "I can use the feature" is too vague
  • Number them (US-1, US-2, ...) so the plan can reference them

Project Customization

Read references/project.md in this skill's directory if it exists. It provides project-specific context:

  • User roles and their permissions
  • View layer technology (e.g. ViewComponents, Thymeleaf, JSP, React)
  • Real-time transport preference (SSE, websockets, polling)
  • Output directory conventions
  • Any other project-specific patterns

© jvm-skills, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .junie/skills/spec of jvm-skills/jvm-skills.

Open the folder on GitHubat commit c6d477f

Compare with similar skills

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.

Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spec this skilljvm-skills/jvm-skills139—~832Automated safety check: PassApache-2.0
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
Ralph Tui Create JSONsubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
To Prdywwynm/EverythingDone14411 repos~777Automated safety check: PassGPL-3.0
Use Case Writerphucnt-bazone-vietnam/use-case-writer143—~4.1kAutomated safety check: PassMIT

Similar skills

  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads Rust

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

  • To Prd

    ywwynm/EverythingDone

    Turn the current conversation context into a PRD and publish it to the project issue tracker.

    144 GitHub starsUsed in 11 repos~777 tokens
    Product & Project ManagementAuto-check passed

  • Use Case Writer

    phucnt-bazone-vietnam/use-case-writer

    Generate Use Case specifications in English Markdown following the IT BA standard 13-field template (Karl Wiegers / IIBA).

    143 GitHub stars~4.1k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

  • Project Planner

    adrianpuiu/claude-skills-marketplace

    Comprehensive project planning and documentation generator for software projects.

    100 GitHub starsUsed in 1 repo~6k tokens
    Product & Project ManagementAuto-check passed

More from jvm-skills/jvm-skills

All 16 skills in this repo

  • Mutation Testing

    jvm-skills/jvm-skills

    Bootstrap pitest via the info.solidsoft.pitest Gradle plugin with Kotlin-sane defaults, run mutation tests scoped to changed classes, interpret surviving mutants from mutations.xml, triage…

    139 GitHub stars~6.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Ralph Coverage

    jvm-skills/jvm-skills

    Run Ralph in coverage mode — iteratively write tests for untested classes until coverage targets are met.

    139 GitHub stars~683 tokensUpdated 1 mo ago
    Auto-check passed

  • Skill Scout

    jvm-skills/jvm-skills

    Run the skill-scout loop — scan the next batch of unscanned JVM-conference rosters for speaker-created AI skills and apply results to the CSV store via the overnight Workflow.

    139 GitHub stars~727 tokensUpdated 1 mo ago
    Auto-check passed

  • UI Review

    jvm-skills/jvm-skills

    Verify UI/UX by running Playwright tests and reviewing screenshots.

    139 GitHub stars~545 tokensUpdated 1 mo ago
    Auto-check passed

  • Kotest

    jvm-skills/jvm-skills

    Write a new Kotlin test, or modernize an existing one, using Kotest matchers and idiomatic Kotlin test style — backticked names, apply/assertSoftly blocks, and existing object mothers and helpers.

    139 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Voice

    jvm-skills/jvm-skills

    Make prose sound like Thomas, not like a generic technical writer.

    139 GitHub stars~592 tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Spec

What does Spec do?

Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed. Spec is an agent skill from jvm-skills/jvm-skills. Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed.

When should I use Spec?

Spec fits situations like: has already described what they want (in the current conversation; A plan) and just needs it formalized into a spec; the user says write a spec.

How do I install Spec in Claude Code?

Run `npx skills add jvm-skills/jvm-skills --skill spec -a claude-code`. Or copy the skill folder (.junie/skills/spec in jvm-skills/jvm-skills) into .claude/skills/spec in your project. Claude Code loads it when a task matches its description.

How do I install Spec in Codex?

Run `npx skills add jvm-skills/jvm-skills --skill spec -a codex`. Or copy the skill folder (.junie/skills/spec in jvm-skills/jvm-skills) into .agents/skills/spec in your project. Codex loads it when a task matches its description.

Can I use 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 jvm-skills/jvm-skills --skill 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/spec, .gemini/skills/spec, .github/skills/spec and .opencode/skills/spec in your project.

What does Spec need to run?

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

Does 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 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 Spec use?

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

How many tokens does Spec use?

About 832 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spec?

Skills that share tags, products or a category with Spec: Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Ralph Tui Create JSON (subsy/ralph-tui, 2.5k stars) and To Prd (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spec?

jvm-skills (a GitHub organization) maintains it in jvm-skills/jvm-skills, which has 139 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on August 31, 2026.

Source: jvm-skills/jvm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.