Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

architecture-decision-records

Sterne2

Forks0

Aktualisiert31. Mai 2026 um 09:06

Use when adding, updating, or consulting repository-local `ADR.md` architecture decisions. Keep ADR authority user-owned and ensure planning flows load `./ADR.md` via `AGENTS.md`.

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

integrii

integrii/logic-patterns

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	architecture-decision-records
description	Use when adding, updating, or consulting repository-local `ADR.md` architecture decisions. Keep ADR authority user-owned and ensure planning flows load `./ADR.md` via `AGENTS.md`.

ADR Recordkeeping

Use repository-local ./ADR.md as the source of truth for user-decided architecture and system design decisions.

Rules:

when starting work in a new repository, create or locate ./ADR.md
before architecture or design decisions, load and consult ./ADR.md
record only decisions the user explicitly makes
do not record your own preferences or inferred architecture choices as ADR decisions
if a repository has AGENTS.md, ensure it tells agents to load ./ADR.md before creating a development plan
treat ADR.md as repository-local accepted decision authority; keep cross-repository rules in root ARCHITECTURE.md and service-local desired behavior in SPEC.md

Good ADR content:

rendering model
deployment stack
language constraints
explicit user rules such as always SSR or deploy via Kargo

Do not use ADR.md as a dump for incidental implementation notes.

Mehr aus diesem Repository

gleiches Repository

five-whys

integrii/logic-patterns

Use when investigating root cause with the Five Whys method: gather evidence across the full problem space, ask five explicit why questions in sequence, and answer each why with a Because line that connects each cause to the prior answer.

2026-07-042

github-release-builds

integrii/logic-patterns

Use when adding or repairing GitHub Actions release automation that builds multi-arch container images on semver tags, pushes them to GitHub Container Registry, updates example healthcheck manifests, creates GitHub releases, and documents the tag-only release process in RELEASE.md.

2026-06-092

bifurcate

integrii/logic-patterns

Use for complex, multi-factor incidents. Recursively split causes into binary branches, pursue one path to a single concrete fix, then backtrack through sibling branches and implement fixes one at a time until the issue-level check passes.

2026-06-022

session-review

integrii/logic-patterns

Use when you need to convert session history into reusable, repo-specific workflow skills from repeated service-specific discovery.

2026-05-312

architecture-spec

integrii/logic-patterns

Use only at workspace root in a multi-service repo with authoritative `ARCHITECTURE.md` when deciding cross-repo ownership, compatibility, or service-to-service contracts. Do not use for service-local `SPEC.md` work.

2026-05-312

centralized-fix-selection

integrii/logic-patterns

Use when deciding whether a behavior change belongs in centralized policy, a shared abstraction, or a local call site. Prefer narrow high-leverage shared fixes for cross-cutting behavior.

2026-05-312

name	architecture-decision-records
description	Use when adding, updating, or consulting repository-local `ADR.md` architecture decisions. Keep ADR authority user-owned and ensure planning flows load `./ADR.md` via `AGENTS.md`.

ADR Recordkeeping

Use repository-local ./ADR.md as the source of truth for user-decided architecture and system design decisions.

Rules:

when starting work in a new repository, create or locate ./ADR.md
before architecture or design decisions, load and consult ./ADR.md
record only decisions the user explicitly makes
do not record your own preferences or inferred architecture choices as ADR decisions
if a repository has AGENTS.md, ensure it tells agents to load ./ADR.md before creating a development plan
treat ADR.md as repository-local accepted decision authority; keep cross-repository rules in root ARCHITECTURE.md and service-local desired behavior in SPEC.md

Good ADR content:

rendering model
deployment stack
language constraints
explicit user rules such as always SSR or deploy via Kargo

Do not use ADR.md as a dump for incidental implementation notes.