Run any Skill in Manus with one click

adr-writing

Stars2

Forks1

UpdatedMarch 10, 2026 at 15:32

Write an Architecture Decision Record (ADR) for KanbAgent following the project's existing format. Activates when a structural decision needs to be documented, when agent arch completes a design decision, or when user says "ADR", "architecture decision", "document this choice".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

IvyNotFound

IvyNotFound/KanbAgent

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	adr-writing
description	Write an Architecture Decision Record (ADR) for KanbAgent following the project's existing format. Activates when a structural decision needs to be documented, when agent arch completes a design decision, or when user says "ADR", "architecture decision", "document this choice".

ADR Writing Skill

Creates a well-structured ADR following the format used in .claude/ADRS-*.md.

When to Use

Agent arch makes a structural decision (IPC contract, DB schema, Electron config)
A decision will affect multiple agents or future contributors
User says "write an ADR", "document this architecture decision"
Before implementing any change touching multiple layers or scopes

File Naming

Check existing ADR files first:

ls .claude/ADRS*.md

ADRs are grouped by number range. Add to the latest group file or create a new one:

.claude/ADRS.md — index
.claude/ADRS-001-003.md — decisions 001 to 003
etc.

ADR Format

## ADR-<NNN> — <Short title>

**Date:** YYYY-MM-DD
**Status:** Accepted | Superseded by ADR-NNN | Deprecated
**Decider:** arch
**Ticket:** T<id>

### Context

[What situation prompted this decision? What problem are we solving?
Be factual — describe the current state and constraints.]

### Decision

[What was decided, precisely. One clear sentence ideally.
Then explain the implementation if needed.]

### Rejected alternatives

| Alternative | Reason for rejection |
|---|---|
| Option A | [Why not] |
| Option B | [Why not] |

### Consequences

**Positives:**
- [Benefit 1]
- [Benefit 2]

**Negatives / trade-offs:**
- [Tradeoff 1]
- [Constraint introduced]

### Agent impact

| Agent | Impact |
|---|---|
| `dev-back-electron` | [What changes for this agent] |
| `dev-front-vuejs` | [What changes for this agent] |
| *(others if relevant)* | |

Update the Index

After writing the ADR, add a line to .claude/ADRS.md:

| ADR-NNN | Short title | Accepted | T<id> |

Rules

Language: English (conv & code)
Be specific — vague ADRs are useless 6 months later
Always list at least 2 rejected alternatives
"Negative consequences" is mandatory — no decision is perfect
One ADR per structural decision — don't bundle unrelated choices

More from this repository

same repository

agent-session-starting

IvyNotFound/KanbAgent

Start an agent session correctly in KanbAgent. Activates when an agent needs to begin work, when user says "start a session", "launch agent X", "begin session", or when an agent role is invoked and no active session exists. Ensures correct startup sequence: dbstart → read tasks → begin work.

2026-04-052

agent-log-writing

IvyNotFound/KanbAgent

Write agent_logs entries correctly in KanbAgent. Activates when an agent needs to log an action, when completing a task, starting a session, or when agent_logs entries are missing. Triggers on "log this", "insert agent_log", "add a log", or any task_started/task_done/session_end event.

2026-04-012

ipc-handler-creating

IvyNotFound/KanbAgent

Create a new typed IPC handler in KanbAgent following the full stack pattern. Activates when user or agent needs to add a new IPC channel, expose a new API to the renderer, or wire a new feature across main/preload/renderer. Triggers on "add IPC", "new handler", "expose to renderer", "new IPC channel", "create a handler".

2026-03-102

migration-creating

IvyNotFound/KanbAgent

Create a versioned SQLite migration for KanbAgent. Activates when the DB schema needs to change, when user says "add a column", "create a table", "migration", "alter schema", "add a column", "modify the schema". Follows the existing migration pattern with idempotency and better-sqlite3 compatibility.

2026-03-102

release-checklist

IvyNotFound/KanbAgent

Execute a release in KanbAgent following the full devops + review protocol. Activates when agent devops receives a release ticket, when user says "release", "publish version", "bump version", "npm run release". Covers prerequisites, version bump, CI wait, GitHub Release publication.

2026-03-102

ticket-completing

IvyNotFound/KanbAgent

Complete a task ticket in KanbAgent following the mandatory order. Activates when an agent finishes work on a task, when user says "mark as done", "ticket done", "close ticket", "close task". Enforces comment-first then done order, session closure, and backlog check.

2026-03-102

name	adr-writing
description	Write an Architecture Decision Record (ADR) for KanbAgent following the project's existing format. Activates when a structural decision needs to be documented, when agent arch completes a design decision, or when user says "ADR", "architecture decision", "document this choice".

ADR Writing Skill

Creates a well-structured ADR following the format used in .claude/ADRS-*.md.

When to Use

Agent arch makes a structural decision (IPC contract, DB schema, Electron config)
A decision will affect multiple agents or future contributors
User says "write an ADR", "document this architecture decision"
Before implementing any change touching multiple layers or scopes

File Naming

Check existing ADR files first:

ls .claude/ADRS*.md

ADRs are grouped by number range. Add to the latest group file or create a new one:

.claude/ADRS.md — index
.claude/ADRS-001-003.md — decisions 001 to 003
etc.

ADR Format

## ADR-<NNN> — <Short title>

**Date:** YYYY-MM-DD
**Status:** Accepted | Superseded by ADR-NNN | Deprecated
**Decider:** arch
**Ticket:** T<id>

### Context

[What situation prompted this decision? What problem are we solving?
Be factual — describe the current state and constraints.]

### Decision

[What was decided, precisely. One clear sentence ideally.
Then explain the implementation if needed.]

### Rejected alternatives

| Alternative | Reason for rejection |
|---|---|
| Option A | [Why not] |
| Option B | [Why not] |

### Consequences

**Positives:**
- [Benefit 1]
- [Benefit 2]

**Negatives / trade-offs:**
- [Tradeoff 1]
- [Constraint introduced]

### Agent impact

| Agent | Impact |
|---|---|
| `dev-back-electron` | [What changes for this agent] |
| `dev-front-vuejs` | [What changes for this agent] |
| *(others if relevant)* | |

Update the Index

After writing the ADR, add a line to .claude/ADRS.md:

| ADR-NNN | Short title | Accepted | T<id> |

Rules

Language: English (conv & code)
Be specific — vague ADRs are useless 6 months later
Always list at least 2 rejected alternatives
"Negative consequences" is mandatory — no decision is perfect
One ADR per structural decision — don't bundle unrelated choices