ai-agent-lead

ai-agent-lead/skills

Skill Claude CodeCodex

Performance benchmarking discipline. Measures latency, throughput, and records baseline environments. Triggered by phrases like "benchmark", "performance test", "measure latency".

ai-agent-lead/skills

Skill Claude CodeCodex

Initializes a greenfield repository. Creates the docs/ directory, the initial CONTEXT.md, and the first ADR. Triggered by phrases like "new project", "initialize", "bootstrap".

ai-agent-lead/skills

Skill Claude CodeCodex

Ultra-concise communication utility for token optimization. Use when the user mentions "caveman mode", "be concise", "save tokens", or "ooga booga". Strips articles, pleasantries, and filler words to maximize efficiency. Skip when the user explicitly requests professional or detailed explanations.

ai-agent-lead/skills

Skill Claude CodeCodex

Disciplined reproduction, isolation, and hypothesis-testing for non-trivial bugs — runs BEFORE tdd when the failing assertion isn't yet known. Use when the user reports a bug whose root cause is not obvious from the symptom — triggered by phrases like "it's broken", "this is failing", "intermittent", "flaky"…

ai-agent-lead/skills

Skill Claude CodeCodex

Module and interface design principles — deep modules and testable interfaces. Use when designing a NEW module, class, or public API; deciding what to expose vs hide; reviewing an interface before implementation; or when the user asks "how should I structure this", mentions "deep modules", "testability", or "API…

ai-agent-lead/skills

Skill Claude CodeCodex

One-page contract for a non-trivial feature or bug fix — Problem, User Story, Acceptance Criteria, Non-Goals. The ACs become the test list for tdd. Use before any non-trivial feature or bug fix; when the user mentions "spec this out", "write a feature doc", "before any non-trivial feature", or describes a feature…

ai-agent-lead/skills

Skill Claude CodeCodex

Grilling session that stress-tests a chosen plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use AFTER a direction has been picked (post-investigate or post-feature-doc), when the user wants to pressure-test the plan — triggered…

ai-agent-lead/skills

Skill Claude CodeCodex

Find deepening opportunities in EXISTING code, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable. Use for EXISTING code…

ai-agent-lead/skills

Skill Claude CodeCodex

Use when the user asks for investigation, research, a proposal, or "options" before any code lands; or proactively for non-trivial structural decisions (new dependency, framework choice, API contract change, cross-cutting refactor). Triggered by phrases like "investigate X", "research Y", "give me a proposal", "what…

ai-agent-lead/skills

Skill Claude CodeCodex

Discipline for reviewing someone else's pull request — the inverse of prod-ready (which is the author's pre-merge gate). Use when the user asks to "review this PR", "look over the diff", "check this change", "give feedback on", or invokes a code-review slash command. Reviews against the linked feature doc / ADRs /…

ai-agent-lead/skills

Skill Claude CodeCodex

Pre-merge production-readiness checklist — operational, infrastructure, and consistency checks that tests alone don't surface. Use after tdd reaches green; before opening a PR or merging to main; after significant infra changes (new DB, new deployment target, new auth flow); or when the user mentions "shipping"…

ai-agent-lead/skills

Skill Claude CodeCodex

Threat-model + control-review pass for surface-changing work — runs alongside tdd and as a heavier gate than prod-ready Section 3 when the change introduces or alters trust boundaries, authentication, authorization, sensitive data flows, or external surfaces. Use when the user mentions "security review", "threat…

ai-agent-lead/skills

Skill Claude CodeCodex

Single end-of-round sweep that tightens what tdd just left green — review every changed file for reuse, quality, efficiency, and test relevance. Use after tdd reaches green and before opening a PR (or before a Builder closes a round in tdd-rounds). Triggered by phrases like "simplify pass", "tighten this", "clean up…

ai-agent-lead/skills

Skill Claude CodeCodex

System-level architecture for greenfield work — name the modules, define responsibilities, set dependency direction, identify seams. Use when starting a new multi-module system or service from scratch, when defining topology before code lands, or when the user mentions "system architecture", "module boundaries"…

ai-agent-lead/skills

Skill Claude CodeCodex

Multi-round TDD orchestration. Use when delivering a feature larger than one TDD slice — typically 5-15 acceptance criteria across multiple packages — by dispatching Builder sub-agents per round, with the parent maintaining state and verifying. Triggered when the user mentions "drive the sub-agent team", "multi-round…

ai-agent-lead/skills

Skill Claude CodeCodex

Test-driven development with the red-green-refactor loop. Use when implementing a feature, fixing a bug, changing core logic, or when the user mentions "TDD", "test-first", "red-green-refactor", or "integration tests". Skip for trivial UI glue, config changes, or pure docs edits.

ai-agent-lead/skills

Skill Claude CodeCodex

Pre-tag smoke test against real third-party APIs. Use after prod-ready is clean, before tagging vN.0 — the gate that catches wire-shape mismatches that fakes accept but real upstreams reject. Triggered when the user mentions "smoke test", "real API", "live verify", "before tag", or "end-to-end against actual ". Pairs…

ai-agent-lead/skills

Skill Claude CodeCodex

User-invoked utility — pulls the agent up an abstraction layer when the user is lost in unfamiliar code. Produces a map of relevant modules, callers, and seams in docs/CONTEXT.md vocabulary. Use when the user says "I'm lost", "zoom out", "give me higher-level context", "I don't know this area", "what depends on what…