Menü
Guides the selection and documentation of architectural decisions using ADR patterns.
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.
Basierend auf der SOC-Berufsklassifikation
Guides the creation and review of Architectural Decision Records (ADRs). Use this skill when a significant architectural change is proposed, a new technology is introduced, or a trade-off needs to be documented.
Intelligently routes requests to the correct context instructions and documentation files. Use this skill to determine which AGENT.md, guide, or technical instruction file is most relevant for a user's request.
Scaffold API mocking infrastructure using Mountebank and Testcontainers for reliable integration testing.
Manage full-stack observability using Logfire (logging/tracing) and OpenObserve (storage/visualization).
Interface for managing the Temporal Database and AI system (ReDB + GGUF embeddings).
Spec-Driven Development workflow using VibesPro conventions
| name | architecture-decisioning |
| description | Guides the selection and documentation of architectural decisions using ADR patterns. |
| metadata | {"id":"ce.skill.architecture-decisioning","tags":["architecture","planning","context-min"],"inputs":{"files":["ARCHITECTURE.md"],"concepts":["tradeoffs"],"tools":["toolset:read"]},"outputs":{"artifacts":[],"files":[],"actions":["propose-decision"]},"dependsOn":{"artifacts":["ce.doc.architecture"],"files":["ARCHITECTURE.md"]},"related":{"artifacts":["ce.prompt.propose-adr"],"files":[]}} |
When a significant design choice must be made, use this skill to weigh options and document the decision clearly.
State the context. Summarise the problem or requirement driving the decision. Reference
relevant sections of ARCHITECTURE.md and other docs that impose constraints.
Identify options. List the viable alternatives. For each, describe the approach, including technologies, patterns and how it satisfies the requirements.
Evaluate trade‑offs. Compare the options against criteria such as complexity, performance, scalability, security, maintainability and alignment with existing architecture. Note pros and cons.
Recommend a decision. Select the option that best meets the criteria. Explain why it is preferred and address why other options were rejected.
Document the decision. Create or update an Architecture Decision Record (ADR) in a
dedicated directory (e.g. docs/adr/). Include context, decision, consequences and links
to relevant discussions. Ensure the ADR is referenced in ARCHITECTURE.md.
Communicate and review. Share the ADR with stakeholders for feedback. Incorporate suggestions and finalise. Make sure the decision is reflected in subsequent plans and implementations.
Thoroughly documented decisions foster transparency and ease future maintenance or revisiting when requirements change.
