Maintain AISTANCE.md as a living document. Use quarterly or when a new AI tool is adopted. Handles review triggers, the three-bucket update process, socialization checklist, and cross-repo consistency. Companion to ai-stance skill.
Monthly DORA ROI snapshot using the 2026 DORA ROI report five-dimension framework. Use when producing board-readable ROI evidence, quarterly LinkedIn posts, or Dojo 'proof it works' content. Requires dora-measurement snapshot. Tier 3: Phase 2.
Emit and consume telemetry spans for agent invocations, skill loads, findings, and decisions. Use when instrumenting the agent system itself or when analyzing agent behavior patterns.
Emit OTEL spans when an agent starts and completes its task. Use when instrumenting an agent to measure duration, success rate, and invocation patterns.
Track which skills are loaded during agent invocations. Use when analyzing skill usage patterns, identifying dead skills, or optimizing context loading.
Generate and maintain AISTANCE.md for any uFawkes repo. Use when onboarding a repo to the uFawkesAI suite, when reviewing AI policy currency, or when a new AI tool is being adopted. Implements DORA AI Capability 1.
Ensure graphify corpus is current and complete before each agent session. Define minimum AI-accessible documentation per repo. Use at session startup to verify internal context is available to AI tools. Implements DORA AI Capability 3.
The cross-validation skill enables the cross-validation agent to validate consistency between agent outputs and their sources. It provides the rules registry and validation runner that check pairwise consistency across the agent pipeline.
Break the specification into logical architectural components. Use when identifying system components, data flows, external dependencies, and boundaries.
Identify the components required to implement the design. Use when mapping architecture to concrete services, modules, pipelines, and GitOps components.
Validate Kubernetes-related design decisions. Use when checking resource requirements, deployment patterns, network design, and secret usage in the design.
Provide CLI commands that scaffold new components, pipelines, tests, and GitOps structures. Use when scaffolding new services, pipeline-spec.yaml, GitOps overlays, or test suites.
Ensure the Fawkes CLI provides a clean, intuitive developer experience. Use when validating command naming, help text, error messages, or interactive prompts.
Provide a reproducible, standardized development environment for all Fawkes projects using devcontainers. Use when validating devcontainer.json, Dockerfile.dev, required tools, or Coder compatibility.
Ensure all required tools for Fawkes development are installed and correct versions. Use when validating Node, Python, kubectl, kustomize, or Fawkes CLI versions.
Simulate PIPE, OBS, GitOps, and cluster behavior locally for fast feedback loops. Use when running local pipeline simulations, GitOps updates, or cluster deployments.
★not rated 2 12d agoA39 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: