菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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". |
Creates a well-structured ADR following the format used in .claude/ADRS-*.md.
arch makes a structural decision (IPC contract, DB schema, Electron config)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## 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)* | |
After writing the ADR, add a line to .claude/ADRS.md:
| ADR-NNN | Short title | Accepted | T<id> |
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.
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.
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".
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.
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.
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.