specgen-sdk-java

Generate Java SDK specifications from PRD and CLAUDE inputs.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/rashidee/co2-skills --skill specgen-sdk-java
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specgen-sdk-java
Source: https://github.com/rashidee/co2-skills/tree/main/skills/specgen-sdk-java
Command: npx skills add https://github.com/rashidee/co2-skills --skill specgen-sdk-java

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a detailed specification for building a distributable Java SDK (Multi-Release fat JAR) from PRD and CLAUDE inputs, enabling consistent, build-ready design docs.

Core Features & Use Cases

  • Automates the creation of a two-tier specification: a root SPECIFICATION.md and per-module SPEC.md files.
  • Maps user stories, NFRs, constraints, and test plans to concrete module surfaces and API mappings.
  • Produces a ready-to-implement Maven/MR-JAR blueprint with OpenAPI surface extraction guidance and module templates.

Quick Start

Provide the application name and version, then generate a complete Java SDK specification from PRD and CLAUDE inputs.

Frequently Asked Questions about specgen-sdk-java

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

FAQPage Schema
How do I generate a Java SDK specification from a PRD?

To generate a Java SDK specification from a PRD, provide your application name and version to automatically map user stories and constraints into module surfaces and OpenAPI mappings. This produces a deterministic, implementation-ready design document.

What is a Multi-Release MR-JAR and how does it apply to Java SDK packaging?

A Multi-Release MR-JAR allows a Java SDK package to contain classes for multiple Java versions. This Skill generates a Maven blueprint that configures MR-JAR packaging to produce a production-ready distributable artifact.

How do I map OpenAPI surfaces to Maven module definitions for a Java SDK?

You can map OpenAPI surfaces to Maven modules by providing your PRD inputs to generate per-module SPEC files. The output includes a root SPECIFICATION.md and module templates that define concrete API mappings and required Maven configuration.

What inputs are required to create a build-ready Java SDK spec?

Creating a build-ready Java SDK spec requires the application name and version as mandatory inputs, with an optional module parameter. It validates these inputs against your PRD and CLAUDE data to output deterministic specifications with versioned references.

Can I use this to automate Maven configuration for a distributable Java fat JAR?

Yes, you can automate Maven configuration for a distributable Java fat JAR. The Skill produces a ready-to-implement Maven and MR-JAR blueprint that extracts OpenAPI surfaces and maps NFRs to module templates for a production-ready artifact.

Why does my Java SDK specification need traceability and versioned references?

Java SDK specifications need traceability and versioned references to ensure consistent, build-ready design docs. This Skill outputs deterministic specifications that map user stories and test plans to concrete module surfaces with traceable, versioned references.