Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

create-adr

Sterne3

Forks0

Aktualisiert13. Dezember 2025 um 12:41

Create Architecture Decision Records (ADRs) following LCA conventions. INVOKE THIS SKILL when user: - Asks to "document a decision" or "record a decision" - Mentions "ADR", "decision record", or "architectural decision" - Wants to capture trade-offs or options considered - Needs to supersede or update an existing decision - Asks about decision history or rationale Trigger keywords: ADR, decision record, architectural decision, trade-offs, options, rationale

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

rayk

rayk/lucid-toolkit

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	create-adr
description	Create Architecture Decision Records (ADRs) following LCA conventions. INVOKE THIS SKILL when user: - Asks to "document a decision" or "record a decision" - Mentions "ADR", "decision record", or "architectural decision" - Wants to capture trade-offs or options considered - Needs to supersede or update an existing decision - Asks about decision history or rationale Trigger keywords: ADR, decision record, architectural decision, trade-offs, options, rationale
allowed-tools	["Read","Write","Glob","AskUserQuestion"]

Guide creation of Architecture Decision Records that capture the "why" behind architectural choices. ADRs are append-only documents that preserve decision history, enabling future maintainers to understand context and trade-offs.

<quick_start>

Identify decision scope: What architectural choice needs documentation?
Gather context: Why is this decision being made now? What drivers exist?
Document options: What alternatives were considered?
Analyze trade-offs: Explicit positive, negative, neutral consequences
Record decision: Write ADR with proper numbering and status
Link to architecture docs: Reference from relevant ARCHITECTURE.md

<naming_convention>

adr-NNN-{slug}.md

Examples:
adr-001-use-protocol-buffers.md
adr-002-adopt-event-sourcing.md
adr-003-schema-org-boundaries.md

Numbers are sequential and never reused. Superseded ADRs keep their number. </naming_convention>

Mehr aus diesem Repository

gleiches Repository

create-subagents

rayk/lucid-toolkit

Expert guidance for creating, building, and using Claude Code subagents and the Task tool. Use when working with subagents, setting up agent configurations, understanding how agents work, or using the Task tool to launch specialized agents.

2025-12-203

delegate-first

rayk/lucid-toolkit

Behavioral principle for context preservation through strategic delegation. Use when starting multi-step operations, uncertain about scope, or when direct execution might exhaust context. Complements never-guess and resolve-ambiguity skills.

2025-12-153

operation-tracker

rayk/lucid-toolkit

Maintain awareness of operation counts across the conversation to prevent cumulative context exhaustion. Use when you notice multiple operations accumulating or when working on iterative tasks across turns.

2025-12-153

consider

rayk/lucid-toolkit

Selects and applies mental models for structured problem analysis. Triggers when user asks "why", "what if", "how should we", needs systematic problem-solving, or mentions analyzing a situation. MUST BE USED when comparing options, making decisions, or evaluating trade-offs.

2025-12-143

dart-flutter-mcp

rayk/lucid-toolkit

Provides Flutter and Dart development workflows using dart-mcp tools. Triggers when working with .dart files, pubspec.yaml, or when user mentions Flutter, widget, Riverpod, Freezed, or Dart development. MUST BE USED for Flutter project work involving dart_analyzer, dart_run_tests, hot_reload, or IDE MCP tools.

2025-12-143

manage-architecture

rayk/lucid-toolkit

Create and maintain architecture documentation following Lucid Composite Architecture (LCA) principles. INVOKE THIS SKILL when user: - Asks an "architect" to review or analyze anything - Mentions "architecture review", "structural review", or "design review" - Requests documentation of system structure or component hierarchies - Wants to create, update, or review ARCHITECTURE.md files - Discusses Atoms, Composites, Conduits, or Deployable Units - Asks about LCA principles or architectural patterns - Needs data strategy with Schema.org at boundaries Trigger keywords: architect, architecture, structural, LCA, component hierarchy, ARCHITECTURE.md

2025-12-133

name	create-adr
description	Create Architecture Decision Records (ADRs) following LCA conventions. INVOKE THIS SKILL when user: - Asks to "document a decision" or "record a decision" - Mentions "ADR", "decision record", or "architectural decision" - Wants to capture trade-offs or options considered - Needs to supersede or update an existing decision - Asks about decision history or rationale Trigger keywords: ADR, decision record, architectural decision, trade-offs, options, rationale
allowed-tools	["Read","Write","Glob","AskUserQuestion"]

<quick_start>

Identify decision scope: What architectural choice needs documentation?
Gather context: Why is this decision being made now? What drivers exist?
Document options: What alternatives were considered?
Analyze trade-offs: Explicit positive, negative, neutral consequences
Record decision: Write ADR with proper numbering and status
Link to architecture docs: Reference from relevant ARCHITECTURE.md

<naming_convention>

adr-NNN-{slug}.md

Examples:
adr-001-use-protocol-buffers.md
adr-002-adopt-event-sourcing.md
adr-003-schema-org-boundaries.md

Numbers are sequential and never reused. Superseded ADRs keep their number. </naming_convention>