Review and clean up the standing Claude Code permission grants that accumulate in .claude/settings.json and settings.local.json via "always allow" — classify each allow rule by risk (destructive commands, credential exposure, credential-store reads, broad…
Create or update a domain expert — a curated, path-scoped context bundle distilled from the org's own docs and code, injected only when a change touches its domain. Use to capture "what someone working in <area> needs to know" (a framework, a service, a data…
Bootstrap .aif/ structure in a new repo or subdirectory
Measure whether the toolkit is actually paying off — compute delivery and quality metrics from git history, merged PRs, and .aif/ artifacts (PR cycle time, rework/revert rate, spec-to-merge time, review-finding trends, skill/telemetry usage), report them with…
Adopt ai-factory in an existing codebase by analyzing it and DRAFTING the fill-in surfaces — the workspace service map, starter domain experts, conventions, and .aif/config.yml — for human review, instead of leaving a wall of blank templates. Use once per…
Multi-agent code review covering correctness, quality, architecture, test coverage, and security
Discovers and routes to the right ai-factory skill, subagent, or MCP tool for the current task. Loaded automatically by the SessionStart hook in every repo where AIF is installed. Use when starting work, when unsure which tool to reach for, or when the work…
Skeleton for an org-specific skill — copy into skills/, rename, and fill in. Encodes a recurring multi-step workflow your org performs (a deploy runbook, a release checklist, an onboarding scaffold).