Skill UI

Alex converts high-level requirements into a precise, dependency-aware, and actionable implementation checklist. It maps critical paths, breaks down features into atomic micro-tasks, and establishes clear Definitions of Done (DoD) across various layers. Ideal for bridging the gap between conceptual goals and step-by-step engineering execution.

This skill designs and audits the core engineering harness required for reliable AI agent collaboration within a codebase. It establishes critical infrastructure elements such as change tracking, linting rules, CI/CD gates, and standardized documentation, ensuring the repository remains the single source of truth for all intelligent agents. Ideal for setting up complex development workflows.

This skill enables the creation of a robust 'harness' system for coding agents within a repository. It addresses the need to prevent repeated AI-generated coding mistakes by implementing durable instructions, guardrails, regression tests, and failure memory. It treats the target repository as the source of truth, ensuring consistency and maintaining high reliability across all automated contributions.

This skill scaffolds the necessary configurations for advanced engineering workflows. It guides the user through setting up the issue tracking system (GitHub, GitLab, or local markdown), defining the canonical triage label vocabulary, and establishing the domain documentation context (single or multi-context). It must be run once to initialize the repository for subsequent agent-driven development skills.

This skill is designed for complex, multi-step tasks requiring coordination among multiple AI agents. It implements a robust workflow engine that first generates a detailed plan (task graph, topology) and then orchestrates parallel execution with adversarial verification. Use this when the task spans many files, requires multiple specialized roles, or involves an overall 'workflow' concept, ensuring structured, reliable, and auditable results.

The /goal command converts standard agent prompts into persistent, self-correcting loops (plan → act → test → review → iterate). It is designed for long-running, complex engineering tasks like migrations, coverage lifts, or refactoring, ensuring progress is tracked against a verifiable stop condition and mandated documentation.

This comprehensive guide outlines a rigorous, human-in-the-loop engineering workflow for leveraging advanced AI agents to complete complex implementation tasks. It mandates defining clear completion criteria, decomposing work into manageable units, and strategically routing models (Haiku, Sonnet, Opus) based on task complexity. The workflow emphasizes continuous evaluation, regression testing, security review of invariants and edge cases, and strict cost discipline to ensure robust and reliable software development using AI assistance.

This model provides an engineering operational framework for teams that leverage AI agents to generate large volumes of code. It shifts the focus from simple syntax to process quality, robust architecture design, rigorous testing, and systematic risk control, ensuring the development of highly stable and reliable systems in AI-assisted environments.

Turns a one-line goal into a step-by-step build plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief, plus review gates, dependency graphs, parallel step detection, and a plan-change protocol.

This skill helps optimize and verify latency-sensitive systems such as real-time dashboards, market data feeds, and streaming agents. It involves tracking p50/p95/p99 latency, freshness age, and queue depth. You will map hot paths and run live readbacks to ensure performance. Use this when throughput or data freshness matters in engineering contexts.

A comprehensive, end-to-end playbook designed for software engineers and AI agents. It provides a structured methodology to safely introduce machine learning capabilities into existing, non-ML codebases. The process covers critical stages: problem framing, data readiness, architectural decoupling (using dedicated APIs/services), baseline model implementation, and final handoff to MLOps practices (CI/CD, monitoring).

Shared orchestration engine behind the orch-* skill family, implementing a gated Research-Plan-TDD-Review-Commit pipeline with size classification, agent/command mapping, and human approval gates. Used indirectly via operation skills like orch-add-feature or orch-fix-defect; read directly when tuning shared phases or adding new operations.