xchewtoyx/rgh-sme

Retrieve agentic engineering wiki concepts. Use when the question is about agentic engineering: Prompt and context engineering; Harness and agent-computer interface (ACI) design; Agent loop and orchestration design; External memory and knowledge architecture for agents; Agent failure modes and design-time evaluation; Maintenance and evolution. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve api design wiki concepts. Use when the question is about api design: Resource and endpoint modelling; Wire-contract naming, typing, and identification; Message and parameter structure; Operation semantics for async and bulk work; Reliability-facing contract mechanics; Response shaping and transfer efficiency; API evolution and lifecycle governance; API-as-product decisions. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve automation engineering wiki concepts. Use when the question is about automation engineering: Toil; The automation maturity path; Designing safe automation; Operational software engineering; Ironies of automation; Self-healing and auto-remediation patterns and their risks. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve capacity performance wiki concepts. Use when the question is about capacity performance: Capacity planning; Performance analysis methodology; Load characterisation and testing; Latency engineering; Efficiency and cost; Scalability patterns as they affect capacity. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve change engineering wiki concepts. Use when the question is about change engineering: Progressive delivery; Rollback engineering; Release verification; CI/CD as a safety system; Change risk management; Delivery metrics (DORA-style) as they inform delivery safety. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve ci cd wiki concepts. Use when the question is about ci cd: Continuous integration, build automation, artifact management, and commit-stage feedback; Deployment pipelines, release orchestration, environment promotion, and automated rollback execution; Automated acceptance, integration, and non-functional testing as delivery gates; Software supply chain security; Evolutionary database schema migrations, database sandboxing, and zero-downtime schema deployment patterns; Pipeline design for repeatability, fast feedback, traceability, and safe change flow; Versioning, branching, dependency management, and release coordination; On-demand, self-service provisioning of ephemeral test environments within delivery pipelines; Delivery metrics and pipeline bottleneck diagnosis when they guide pipeline improvement; Delivery of LLM/agent artifacts. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve data engineering wiki concepts. Use when the question is about data engineering: Pipeline design; Loading dimensional and analytical structures; Data quality engineering; Orchestration; Analytical platform architecture; Data lifecycle engineering. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve data visualization wiki concepts. Use when the question is about data visualization: Matching visual form to analytical question; Perceptual foundations; Dashboard design; Graphical integrity; Analytical interaction. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve decision alignment wiki concepts. Use when the question is about decision alignment: Decision-document genres; Options analysis; Stakeholder alignment; Making decisions defensible; Turning a decision into coordinated action. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve dimensional modelling wiki concepts. Use when the question is about dimensional modelling: Dimensional modelling technique; Fact table types (transaction, periodic snapshot, accumulating snapshot, factless), additivity, degenerate dimensions; Dimension design; The bus architecture, bus matrix, and enterprise conformance, including the business-led governance process that…; The dimensional design process; Physical implementation of a dimensional model; Schema patterns that absorb operational/timing realities; Trade-offs versus other modelling styles (Inmon's Corporate Information Factory, stand-alone data marts, Data Vault…. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve distributed systems wiki concepts. Use when the question is about distributed systems: Replication; Partitioning; Transactions and consistency; Coordination and consensus; The failure semantics of distribution; Distribution architecture. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve evidence verification wiki concepts. Use when the question is about evidence verification: Substantiating claims; Verification method; Review process; Review workflows; Common failure modes. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve incident management wiki concepts. Use when the question is about incident management: Incident response structure; On-call design; Postmortems and learning from incidents; Preparedness. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve infrastructure as code wiki concepts. Use when the question is about infrastructure as code: Infrastructure expressed as version-controlled, reviewable declarations; Resource, module, component, and stack design; State management, drift detection, import, migration, and reconciliation; Safe live-infrastructure change; Infrastructure testing, validation, policy-as-code, and compliance controls; Cost governance embedded in infrastructure code and its pipeline; Reusable infrastructure interfaces, environment promotion, and team workflows; Tooling choices and trade-offs for provisioning and configuration systems. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve judgment calibration wiki concepts. Use when the question is about judgment calibration: The dual-process frame and bias mechanism; Statistical-reasoning failure modes; The overconfidence family; Calibration and scoring; Structured estimation method; Belief updating as its own skill; Debiasing technique and deliberate practice; Team and aggregation epistemics for judgment; Choice under uncertainty and its distortion. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve observability wiki concepts. Use when the question is about observability: Telemetry types and their trade-offs; Instrumentation practice; Debugging methodology; AI agent & LLM observability; Observability data systems; Sociotechnical & developer feedback loops. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve operational handover wiki concepts. Use when the question is about operational handover: Runbook and playbook writing; Handover documents; Capturing tacit/tribal knowledge; Maintenance documentation; Troubleshooting guides and onboarding documentation aimed at building independent operating competence, not just…. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve organizational learning wiki concepts. Use when the question is about organizational learning: Psychological safety as a group-level construct; Silence and voice dynamics; Leadership practice for learning cultures; Team learning as a discipline distinct from individual learning; Mental models and shared vision as organisational routines; Failure taxonomy and blameless learning at organisational scale; Systems thinking as a shared diagnostic language for learning failures; Knowledge flow as a social phenomenon. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve reliability engineering wiki concepts. Use when the question is about reliability engineering: SLI identification; SLO development; Error budgets; Alerting on SLOs; Service-level management practice; Reliability principles; Service-level management for nondeterministic, model-backed services. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve requirements architecture wiki concepts. Use when the question is about requirements architecture: Requirements practice; Architecture documentation; Constraints and trade-offs; Rationale capture; Traceability; Requirements for machine consumers. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve resilience engineering wiki concepts. Use when the question is about resilience engineering: Accident causation models; Safety-I versus Safety-II; Human factors of failure; Safety culture and organisation; The human-factors critique of procedures. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve security engineering wiki concepts. Use when the question is about security engineering: Threat modelling; Secure-design principles; Identity, authentication and authorisation as design concepts; Vulnerability classes as concepts; Security and reliability as related system properties; Security assurance practice; Machine-agent identity and delegated authority; The LLM/agent threat surface as a vulnerability-class family. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve software design wiki concepts. Use when the question is about software design: Module design; Complexity management; Interface and API design; Public API surface as a product; Refactoring; Test design at the code level; Code-level readability. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Retrieve technical communication wiki concepts. Use when the question is about technical communication: Audience analysis; Clarity technique; Document structure; Adapting the same material for different formats and reader types (executive summary vs deep reference vs quickstart)…; Editing practice. Scan concepts.json in this skill folder. Read only matching notes. Follow basename links hop by hop. Do not load every note. Do not answer from fleeting/ notes.

Route SME wiki questions to the matching domain wiki skills. Use when you do not know which bundle applies or the question spans multiple bundles: dimensional-modelling, observability, reliability-engineering, incident-management, automation-engineering, change-engineering, capacity-performance, technical-communication, evidence-verification, requirements-architecture, decision-alignment, operational-handover, infrastructure-as-code, ci-cd, resilience-engineering, data-engineering, data-visualization, distributed-systems, software-design, security-engineering, agentic-engineering, api-design, judgment-calibration, organizational-learning. Compact charter extracts are routing hints only — hand off to <slug>-wiki skills. Do not answer from the summaries.