adr

Name: Adr
Author: camunda

// Use when the user asks to write an ADR, says "create an ADR for X", "document this decision", "we need an ADR", or whenever you're about to make a significant design choice — introducing a port/adapter/SPI, picking between viable approaches, altering data flow, adding a dependency, or establishing a project-wide convention. Default to invoking this skill for any architectural change.

Run Skill in Manus

$ git log --oneline --stat

stars:4

forks:0

updated:May 8, 2026 at 14:35

SKILL.md

readonly

name	adr
description	Use when the user asks to write an ADR, says "create an ADR for X", "document this decision", "we need an ADR", or whenever you're about to make a significant design choice — introducing a port/adapter/SPI, picking between viable approaches, altering data flow, adding a dependency, or establishing a project-wide convention. Default to invoking this skill for any architectural change.

Write an Architecture Decision Record

Follow the workflow in docs/workflows/adr.md to create a new ADR in docs/adr/.

Read that file and follow it exactly. It covers when an ADR is required, how to number it, the body structure (including the Deciders field), and how to link the ADR from the work it accompanies.

related-skills.json

same repository

epic.md

from "camunda/camunda-security-library"

Use when the user wants to track a phase of work within a feature, says "create an epic for phase X", "track this phase", or needs to group related tasks under a milestone. Epics sit between features and tasks in the hierarchy.

2026-05-284

tour.md

from "camunda/camunda-security-library"

Use when the user wants an orientation to this repo, says "tour", "show me around", "what can I do here", "how does this repo work", "I'm new here", or wants to know the available slash commands and project structure

2026-04-244

task.md

from "camunda/camunda-security-library"

Use when the user asks to track a task, says "create a task for X", "break this feature into tasks", "we need to implement X", or wants a small, self-contained unit of work captured as an issue (standalone or as part of a feature)

2026-04-174

bug.md

from "camunda/camunda-security-library"

Use when the user reports a bug, says "track this bug", "this is broken", "the behavior should be X", or describes unexpected behavior they want fixed

2026-04-174

docs.md

from "camunda/camunda-security-library"

Use when the user asks to document something in the codebase, says "document this", "add docs for", "write documentation for", or wants code-level documentation created or updated

2026-04-174

feature.md

from "camunda/camunda-security-library"

Use when the user requests a new capability, says "we should be able to", "add support for", "I want to be able to", or describes functionality that doesn't exist yet

2026-04-174

package.json