Architecture planning and architecture review for the declarative agent platform. Use to design or evaluate changes that affect layers, lifecycles, or contracts. Read-only — does not implement code unless explicitly asked.
Performs senior-level code review on diffs/PRs for the agent platform, focused on architecture boundaries, lifecycle/state, security, and tests. Read-only; outputs a structured review.
Updates README, docs/, ADRs, and skill files for the agent platform. Keeps documentation honest and synchronized; never claims unimplemented features work.
Plans and writes pytest tests for the agent platform. Behavior-focused, mocks all external systems, adds negative/security tests. Never calls real external services.
Guard the project's architecture invariants. Use to evaluate any change affecting layers, boundaries, lifecycles, or contracts, and to decide whether an ADR is required.
Senior-level code review for the agent platform — architecture and boundaries first, then correctness, security, testability, and simplicity. Outputs a structured review.
Work safely with Git — keep changes scoped and reviewable, never overwrite the user's work, and produce clear history. Use before editing, branching, staging, or committing.
Working on RuntimeEngine, ExecutionContext, agent execution, or the request lifecycle. Primary tasks are tasks/0003-compiled-agent-graph.md and tasks/0004-runtime-engine.md.
The standard for writing Python here — small, typed, explicit, testable modules with side effects pushed to the edges. Use when implementing or designing any Python code.
Working on resolver plugins, the fixed access plugin contract, mapping resolver outputs into ExecutionContext, or protected-node filtering. Primary task is tasks/0006-sidecar-auth-context.md.
How to create or restructure a skill so the .ai/skills/ system stays consistent, operational, and trustworthy. A skill is a short, repeatable playbook — not an essay.
How to write and run fast, deterministic, behavior-focused pytest tests that never touch real external systems. Use whenever adding or changing behavior, or fixing a bug.