Define requirements for an OpenClaw integration
Document a proposed integration's data needs, actions, credentials, and review boundaries.
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
--- name: architecture-a720187db88d description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design. allowed-tools: Read, Glob, Grep --- # Architecture Decision Framework > "Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale." ## π― Selective Reading Rule **Read ONLY files relevant to the request!** Check the content map, find what you need. | File | Description | When to Read | |------|-------------|--------------| | `context-discovery.md` | Questions to ask, project classification | Starting architecture design | | `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions | | `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns | | `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations | | `patterns-reference.md` | Quick lookup for patterns | Pattern comparison | --- ## π Related Skills | Skill | Use For | |-------|---------| | `@[skills/database-design]` | Database schema design | | `@[skills/api-patterns]` | API design patterns | | `@[skills/deployment-procedures]` | Deployment architecture | --- ## Core Principle **"Simplicity is the ultimate sophistication."** - Start simple - Add complexity ONLY when proven necessary - You can always add patterns later - Removing complexity is MUCH harder than adding it --- ## Validation Checklist Before finalizing architecture: - [ ] Requirements clearly understood - [ ] Constraints identified - [ ] Each decision has trade-off analysis - [ ] Simpler alternatives considered - [ ] ADRs written for significant decisions - [ ] Team expertise matches chosen patterns ## AGI Framework Integration ### Qdrant Memory Integration Before executing complex tasks with this skill: ```bash python3 execution/memory_manager.py auto --query "<task summary>" ``` **Decision Tree:** - **Cache hit?** Use cached response directly β no need to re-process. - **Memory match?** Inject `context_chunks` into your reasoning. - **No match?** Proceed normally, then store results: ```bash python3 execution/memory_manager.py store \ --content "Description of what was decided/solved" \ --type decision \ --tags architecture <relevant-tags> ``` > **Note:** Storing automatically updates both Vector (Qdrant) and Keyword (BM25) indices. ### Agent Team Collaboration - **Strategy**: This skill communicates via the shared memory system. - **Orchestration**: Invoked by `orchestrator` via intelligent routing. - **Context Sharing**: Always read previous agent outputs from memory before starting. ### Local LLM Support When available, use local Ollama models for embedding and lightweight inference: - Embeddings: `nomic-embed-text` via Qdrant memory system - Lightweight analysis: Local models reduce API costs for repetitive patterns--- name: architecture-a720187db88d description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design. allowed-tools: Read, Glob, Grep --- # Architecture Decision Framework > "Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale." ## π― Selective Reading Rule **Read ONLY files relevant to the request!** Check the content map, find what you need. | File | Description | When to Read | |------|-------------|--------------| | `context-discovery.md` | Questions to ask, project classification | Starting architecture design | | `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions | | `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns | | `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations | | `patterns-reference.md` | Quick lookup for patterns | Pattern comparison | --- ## π Related Skills | Skill | Use For | |-------|---------| | `@[skills/database-design]` | Database schema design | | `@[skills/api-patterns]` | API design patterns | | `@[skills/deployment-procedures]` | Deployment architecture | --- ## Core Principle **"Simplicity is the ultimate sophistication."** - Start simple - Add complexity ONLY when proven necessary - You can always add patterns later - Removing complexity is MUCH harder than adding it --- ## Validation Checklist Before finalizing architecture: - [ ] Requirements clearly understood - [ ] Constraints identified - [ ] Each decision has trade-off analysis - [ ] Simpler alternatives considered - [ ] ADRs written for significant decisions - [ ] Team expertise matches chosen patterns ## AGI Framework Integration ### Qdrant Memory Integration Before executing complex tasks with this skill: ```bash python3 execution/memory_manager.py auto --query "<task summary>" ``` **Decision Tree:** - **Cache hit?** Use cached response directly β no need to re-process. - **Memory match?** Inject `context_chunks` into your reasoning. - **No match?** Proceed normally, then store results: ```bash python3 execution/memory_manager.py store \ --content "Description of what was decided/solved" \ --type decision \ --tags architecture <relevant-tags> ``` > **Note:** Storing automatically updates both Vector (Qdrant) and Keyword (BM25) indices. ### Agent Team Collaboration - **Strategy**: This skill communicates via the shared memory system. - **Orchestration**: Invoked by `orchestrator` via intelligent routing. - **Context Sharing**: Always read previous agent outputs from memory before starting. ### Local LLM Support When available, use local Ollama models for embedding and lightweight inference: - Embeddings: `nomic-embed-text` via Qdrant memory system - Lightweight analysis: Local models reduce API costs for repetitive patterns
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.