Expanded agents-architect skill from v1.0 (594 lines, 16 sections) to v1.2 (1616 lines, 28 sections) per AJ’s god-grade / zero-compromise / zero-flaws / zero-conflicts / zero-ambiguities / zero-redund

Decision

Expanded agents-architect skill from v1.0 (594 lines, 16 sections) to v1.2 (1616 lines, 28 sections) per AJ’s god-grade / zero-compromise / zero-flaws / zero-conflicts / zero-ambiguities / zero-redundancies mandate. Added §17 Agent Design Patterns Catalog (10 patterns with code), §18 Canonical Search Attributes Schema, §19 Temporal Recipes Cookbook (Worker Versioning, Patching, Signals, Schedules, Continue-as-New, Activity decomposition, Retry policies, Heartbeats), §20 Mission Control Wiring (4 Grafana dashboards with PromQL + Slack alert YAML + daily digest format + agentctl CLI surface), §21 Operational Runbooks (10 incident types end-to-end), §22 Cost Methodology (token tracking, pricing table, per-tenant aggregation, budget burn-down, anomaly detection), §23 Sandbox Invocation Pattern (gVisor + Firecracker + Cilium egress allowlist), §24 HITL Bridge Implementation (Slack button → Temporal Signal flow), §25 DR + Upgrade Procedures (backup schedule, full rebuild RTO=4h RPO=1h, patch/minor/major upgrade procedures), §26 Cross-Stack Dependency Map, §27 MCP Tool Surface (agent-fleet-mcp 9th Permanent MCP with 21-tool inventory). Also enhanced §2 with popularity data table and “why most popular/easiest/quality” property table; added Reading List (§4); added Phase Gate Acceptance Criteria (§6); added Risk Register table (§12). MEMORY.md cascade intact. Two references/ files (day-in-the-life.md, phase-gates.md) for progressive disclosure. AJ explicitly overrode the setup-curator 600-line guidance, citing god-grade-completeness > line-budget. Setup-curator was invoked retroactively (admitted lapse, logged for next session).

Rationale

AJ’s mandate explicitly requires zero-compromise capture of complete operational expertise. The original 594-line skill captured architecture and lifecycle but lacked: concrete design patterns with code, the canonical Search Attributes schema, the Temporal cookbook (Worker Versioning, Patching API, Signals, Schedules, Continue-as-New), full Mission Control wiring (4 Grafana dashboards with PromQL + Slack alerts + daily digest format), 10 operational runbooks, cost methodology with pricing table, sandbox invocation pattern, HITL bridge implementation, DR + upgrade procedures, cross-stack dependency map, and the agent-fleet-mcp tool surface. Without these, future sessions would lack god-grade operational capability and would have to re-derive recipes. Per Law 9 (Cohesive Integration) and Law 10 (Full Capability), the skill MUST encode all expertise inline. Per AJ’s feedback_quality_over_size.md clarification: compounding intelligence > bulk, but “compounding” requires that intelligence to actually be present. The 600-line cap from setup-curator is guidance not law (the only hard cliff is MEMORY.md’s 200-line truncation). Progressive disclosure via references/ retains for narrative depth (day-in-the-life walkthrough, phase-gates day-by-day plan) but the operational core stays inline because it must be auto-loaded on every agent-related trigger. Net result: future sessions auto-load 1616 lines of god-grade agent-fleet expertise the moment any agent-related keyword fires. Decision is partially_reversible (skill content can be pruned later if it proves to bloat context) but the directional commitment to comprehensive coverage IS the AJ-approved posture.

Alternatives Rejected

Outcome

Pending