113-java-maven-documentation
This Claude Code skill generates a DEVELOPER.md file for Maven projects by combining a fixed base template with dynamic content extracted from pom.xml files, including tables for plugin goals, Maven profiles, and submodules in multi-module projects. Use it when creating or updating developer documentation for Maven-based Java projects that need standardized, pom-derived reference material.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/113-java-maven-documentation && cp -r /tmp/113-java-maven-documentation/skills/113-java-maven-documentation ~/.claude/skills/113-java-maven-documentationSKILL.md
# Create DEVELOPER.md for the Maven projects Generate a `DEVELOPER.md` file that combines a fixed base template with dynamic sections derived from analysing the project `pom.xml`. **What is covered in this Skill?** - Base template reproduction (verbatim) - Plugin goals reference: table of `./mvnw` goals per explicitly declared plugin, max 8 goals each - Maven Profiles table: profile ID, activation trigger, representative command, description - Submodules table (multi-module projects only) ## Constraints Before generating any content, read every pom.xml in the workspace. Only include plugins explicitly declared in the project POMs — never plugins inherited from parent POMs or the Maven super-POM unless redeclared. - **MANDATORY**: Read every `pom.xml` in the workspace (root and submodules) before generating any content - **PLUGIN SCOPE**: Only include plugins **explicitly declared** in `<build><plugins>` or `<build><pluginManagement><plugins>` — never plugins inherited from parent POMs or the Maven super-POM unless redeclared - **SCOPE**: Execute steps 1–5 in order. Omit Profiles section if no profiles; omit Submodules section if not multi-module - **BEFORE APPLYING**: Read the reference for the base template content, plugin catalog, and detailed constraints for each step ## When to use this skill - Create DEVELOPER.md - Generate DEVELOPER.md - Maven project documentation - Add Maven documentation - Plugin goals reference - Maven Profiles table - Submodules table ## Workflow 1. **Read all POM files in workspace** Read root and every submodule `pom.xml` before generating content. 2. **Read documentation reference assets** Read `references/113-java-maven-documentation.md` to use the base template and plugin catalog constraints exactly. 3. **Assemble DEVELOPER.md base and dynamic sections** Generate `DEVELOPER.md` with verbatim base template plus dynamic sections: plugin goals, profiles (if any), and submodules (if multi-module). 4. **Enforce plugin scope and section omission rules** Include only explicitly declared plugins and omit Profiles/Submodules sections when not applicable. ## Reference For detailed guidance, examples, and constraints, see [references/113-java-maven-documentation.md](references/113-java-maven-documentation.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project