sivaprasadreddy

SDD step 1. Analyse a feature request and produce a detailed feature.md spec. Use when the user describes a new feature they want to build. Asks for missing details before writing the spec.

SDD step 0. Analyse the project codebase and create docs/project.md with tech stack, architecture, and conventions. Run once before starting SDD in a new project. If docs/project.md already exists, asks whether to regenerate it.

SDD step 3. Read feature.md and produce a detailed implementation plan.md tailored to the project's tech stack and architecture. Use after /sdd-feature has produced feature.md.

SDD step 2 (optional, repeatable). Read an existing feature.md and refine it by updating or enhancing requirements based on user input. Use when requirements have changed, new edge cases are discovered, or the spec needs clarification before planning or…

SDD fast path. Runs the full pipeline — analyse → plan → implement → review → archive — with a single confirmation gate before implementation begins. Stops automatically if Critical or Major issues are found in review. Use when you want to ship a…

SDD step 7. Archive feature.md and plan.md into docs/specs-archive/<yyyymmddHHMM>-<feature-name>/ directory, then update docs/project.md with the new feature, and any architecture decisions made. Use after /sdd-review is complete and the feature is ready to…

SDD step 5. Reviews the implemented feature code against language and framework best practices, checks for code duplication, security vulnerabilities, performance issues, test coverage, and alignment with feature.md acceptance criteria. Use after…

SDD step 4. Read plan.md and implement the feature step by step, then verify all acceptance criteria are met. Use after /sdd-plan has produced plan.md.

Collaboratively design, implement, review, and refine software features with a human developer using an iterative pair programming workflow. Prioritize understanding, explicit approval, small reviewable changes, and synchronized specifications.

Build Spring Boot 4.x applications following the best practices. Use this skill: * When developing Spring Boot applications using Spring MVC, Spring Data JPA, Spring Modulith, Spring Security * To create recommended Spring Boot package structure * To…

Apply the changes from all open Renovate bot pull requests of a GitHub repository into the local working tree. Use this skill when asked to apply, merge locally, consolidate, batch, or try out Renovate/dependabot-style dependency update PRs so the combined…

Use when the user wants to create/generate/scaffold a new Spring Boot project (Maven or Gradle, REST API / Web App / Spring Boot + Angular full stack). Derives progen CLI inputs from the user's plain-English project description, asks for any missing mandatory…

Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. By default review files modified in git; when the user explicitly names files, classes, packages, or a diff, review that scope instead. Generate a…

Verifies whether code follows Spring Modulith code structure or not. Show list of violations along with recommendations on how to fix them. Use this skill: * When reviewing Spring Boot applications which uses Spring Modulith * When verifying whether Spring…

Use this skill when asked to perform any of the following actions in a Java project: - To add jspecify support - To prevent NullPointerExceptions - To better handle Nullability This skill will add jspecify dependency, configure Maven or Gradle build to…

Creates JPA entities following best practices.

Creates Spring Data JPA repositories following best practices.

Creates Spring REST APIs following best practices.

Creates Spring Service classes following best practices.

Creates recommended package structure for Spring Boot projects.

Clarify feature intent, resolve business-rule ambiguities, and produce reviewable behavioral requirements and acceptance criteria before implementation.

Implement approved behavior with automated tests as a feedback loop, choosing test-first or exploratory implementation according to task risk and uncertainty.

Derive reviewable, implementation-independent test scenarios from approved requirements and acceptance criteria.

Challenge an implementation against approved requirements and test evidence, looking for gaps that a self-validating implementation workflow can miss.

Generate or regenerate a requirements.md use-case specification from a product requirements document (PRD.md). Use when translating a PRD into implementable use cases, dependencies, statuses, and testable acceptance criteria; do not use for implementation or…

Update one documented UC-### use case so its description, acceptance criteria, dependencies, and status accurately reflect the current implementation. Use after human or ad hoc code changes fill gaps, alter behavior, or correct an implementation; do not use…

Implement one documented use case identified by a UC-### ID, including its tests and requirements status transitions. Use when the user asks to implement a specific use case from requirements.md; do not use to draft requirements or implement an unspecified…

Implement one documented use case identified by a UC-### ID, including its tests and requirements status transitions. Use when the user asks to implement a specific use case from requirements.md; do not use to draft requirements or implement an unspecified…

Generate or regenerate a requirements.md use-case specification from a product requirements document (PRD.md). Use when translating a PRD into implementable use cases, dependencies, statuses, and testable acceptance criteria; do not use for implementation or…

Update one documented UC-### use case so its description, acceptance criteria, dependencies, and status accurately reflect the current implementation. Use after human or ad hoc code changes fill gaps, alter behavior, or correct an implementation; do not use…

Checks Maven Central, the Gradle Plugin Portal, nodejs.org and the npm registry for newer versions of the dependencies and plugins used in generated Spring Boot projects, and updates generators/springboot/versions.go. Use when asked to upgrade, bump, refresh…

Generate a comprehensive, structured learning guide for any technical topic or technology. Use this skill whenever a user wants to learn a new technology, programming language, framework, tool, or concept — even if they phrase it casually (e.g., "teach me…

Interview the human one question at a time to clarify feature intent and business rules, then write reviewable behavioral requirements and acceptance criteria before implementation.