spec

Generate complete feature specifications from conversation details, documents, and code patterns.

135|25|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jvm-skills/jvm-skills --skill spec-jvm-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/spec
Command: npx skills add https://github.com/jvm-skills/jvm-skills --skill spec-jvm-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates scattered conversation details, referenced documents, and partial code patterns into a complete feature specification, removing the need for time-consuming interviews while preserving intent and scope.

Core Features & Use Cases

  • Generate a structured feature spec from existing context (conversation history, docs, and code exploration) that includes goals, success criteria, and acceptance criteria.
  • Produce clear User Stories with roles, actions, and outcomes, aligned to the feature narrative and design patterns.
  • Provide a ready-to-use document for product planning, design handoffs, and backlog grooming, with sections for entry points, user journeys, edge cases, and state transitions.

Quick Start

Provide the conversation context and relevant codebase references to generate a complete feature spec.

Frequently Asked Questions about spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a feature specification from existing conversation details and code patterns?

Generate a feature specification by providing conversation context and relevant codebase references, which translates scattered details into a structured spec with goals, user journeys, and acceptance criteria.

Can I create user stories for backlog grooming without conducting stakeholder interviews?

Yes, you can create user stories without interviews by mining existing context from conversation histories and documents to produce a final User Stories block aligned with roles and outcomes.

What is the best way to turn scattered product design context into a production-ready spec?

Turn scattered product design context into a production-ready spec by processing conversation details and partial code patterns into organized sections for entry points, edge cases, and state transitions.

What sections are included in a feature specification generated from mined context?

A generated feature specification includes organized sections for entry points, user journeys, roles, edge cases, state transitions, and a final User Stories block following project conventions.

Does generating feature specifications this way work for design handoffs and product planning?

Yes, this specification generation works for design handoffs and product planning by producing a ready-to-use document with success criteria and clear user stories directly from existing project context.

When do I need to use context mining for feature specification instead of manual drafting?

Use context mining for feature specification when you have scattered conversation details and partial code patterns but need to quickly remove time-consuming interviews while preserving intent and scope.