engineering-skills

Plugin engineering-skills from marketplace awesome-prompts in sharmapuneet1510/awesome-prompts. Commands read from the repo's manifest — 1 month ago.

Skills (43)

• adr

  A change alters a contract, data shape, dependency, or failure mode (RULE 11a), or `architect:adr` runs

• agent-skill-design

  Authoring a new skill, or restructuring an existing one

• ansible

  Configuring servers or VMs, deploying an app onto hosts, or reviewing playbooks — `implementer:iac`, `implementer:pipeline`

• apache-camel

  Building or debugging Camel routes, EIP integrations, or Camel on Spring Boot

• apache-pulsar

  Producing or consuming Pulsar messages, choosing a subscription type, or debugging backlog/redelivery

• ba-create

  Plain-text, Markdown, or Gherkin requirements must become Jira issues with BDD acceptance criteria (`ba:create`)

• backend

  Generating REST endpoints in FastAPI or Spring Boot (`implementer:build`, `architect:api`)

• code-documentation

  Adding or fixing Javadoc, docstrings, or JSDoc — `implementer:doc`, or the doc phase of `implementer:full`

• code-formatting

  Setting up or enforcing formatting and naming for Java, Python, or JS/TS

• code-health

  Deep inspection of existing code for risk — `quality:audit`, or a health pass before refactoring

• code-review

  Reviewing a PR against its Jira ticket — `quality:review`, `quality:report`

• context-builder

  A project has no `docs/context/`, or its structure changed — `orchestrator:context`, `architect:analyse`

• current-tech-spec

  An ADR reached Accepted or later, or a PR merged — `architect:spec`

• database

  Designing tables, indexes, or migrations for PostgreSQL, MySQL, or SQL Server — `architect:schema`

• debugging

  A bug, failing test, or incident needs a root cause — `quality:debug`, `quality:diagnose`

• error-handling

  Designing exceptions, retries, fallbacks, or error responses in Java, Python, or JS

• frontend

  Generating React + TypeScript components and pages — `implementer:build`, `architect:frontend`

• html-report

  A skill run created, modified, or deleted files, or the caller passed `report=html`

• java-advanced

  Writing or reviewing Java 17/21 code, with or without Spring Boot

• jira-html-report

  A Jira export (JSON or CSV) must become a readable backlog — `ba:parse`, `ba:report`

• jira-implementation

  "Implement PROJ-123" — one Jira ticket, end to end, to a PR ready to merge. `implementer:full`, `orchestrator:build`

• jira-incremental-spec-generator

  Building one specification from a whole Jira project by reading tickets in sequence

• logger

  Adding or configuring logging in Java: SLF4J, Logback, Log4j2

• lombok

  Reducing Java boilerplate with Lombok

• maven

  Creating or fixing a Maven build, adding a module, resolving a dependency conflict, or wiring Maven into CI — `implementer:build`, `implementer:pipeline`

• mcp-server-builder

  Creating, testing, or registering an MCP server

• mcp-server

  Designing which tools an MCP server or agent exposes, and their schemas

• mssql-advanced

  Writing or reviewing T-SQL: procedures, indexes, dynamic SQL on SQL Server / Azure SQL

• mssql-dba

  SQL Server is slow, blocked, or deadlocking; or indexes and partitioning need a review — `quality:perf`, `quality:diagnose`, `quality:debug`

• multi-review-html

  Several PR reviews must become one HTML report — `quality:batch-review`

• nemesis

  A finished conclusion — PR approval, ADR, test result, release decision, RCA — must be attacked before it is trusted (`orchestrator:nemesis`)

• oop

  Designing classes and their relationships in any OO language

• opentelemetry

  Adding traces, metrics, or log correlation to a Java / Spring Boot service

• project-context

  Any companion is about to act (read) or has had a decision approved (write) — every BA, architect, quality function

• project-setup

  A new project, or an existing one with no written stack and library decisions — before `implementer:build` writes feature code. `orchestrator:ideate`, `orchestrator:plan`, `architect:design`

• python-advanced

  Writing or reviewing Python 3.11+ code: FastAPI, SQLAlchemy, Pydantic, asyncio

• python-project

  Starting a Python project, adding tooling to one, fixing dependency or packaging problems, or containerising it — `implementer:build`, `implementer:pipeline`, `implementer:docker`

• react-advanced

  Writing or reviewing React 18+/19 + TypeScript

• refactoring

  Restructuring code without changing behaviour — `architect:refactor`, or before a feature that the current shape blocks

• security-audit

  A focused hunt for exploitable weaknesses — `quality:security`, `quality:qa suite=security`

• spec-driven-development

  Any feature work — RULE 11: requirements → design → tasks, each approved before the next

• spring-advanced

  Spring internals: IoC, AOP, WebFlux, Batch, Cloud, events, or a Spring behaviour that makes no sense

• traceability

  Before `implementer:build` (gate checks), after `architect:spec`, inside `quality:observe`, before a release — `ba:trace`