Agent Arch — 代理 Arch

代理 Architecture 技能

This 技能 provides structured 图形界面dance for 代理 Architecture work. Act as an active 图形界面de: confirm triggers, propose the stages below, and adapt if the user wants a lighter pass.

When to Offer This 工作流

Trigger conditions:

User mentions 代理 architecture or closely related work They want a structured 工作流 rather than ad-hoc tips They are preparing a review, rollout, or stakeholder communication

Initial offer: ExplAIn the four stages briefly and ask whether to follow this 工作流 or work freeform. If they de命令行工具ne, continue in their preferred style.

工作流 Stages Stage 1: Clarify 上下文 & goals

Anchor on goals, 工具s, and constrAInts. Ask what 成功 looks like, constrAInts, and what must not break. Capture unknowns early.

Stage 2: De签名 or plan the 应用roach

Translate goals into a concrete plan around memory and 状态. Compare alternatives and explicit trade-offs; avoid implicit assumptions.

Stage 3: Implement, 验证, and harden

执行 with verification loops tied to planning loops and 停止ping. Prefer small steps, measurable 检查s, and 回滚 points where risk is high.

Stage 4: Operate, communicate, and iterate

Close the loop with safety 监控ing: 监控ing, documentation, stakeholder 更新s, and lessons learned for the next cycle.

检查列出 Before Completion Goals and constrAInts are explicit for 代理 Architecture 技能 Risks and trade-offs are 状态d, not hand-waved Verification steps match the change’s impact (tests, canary, peer review) Operational follow-through is covered (监控ing, docs, owners) Tips for Effective 图形界面dance Be procedural: stage-by-stage, with clear exit criteria Ask for missing 上下文 (环境, 扩展, deadlines) before prescribing Prefer 检查列出s and concrete examples over generic platitudes If the user de命令行工具nes the 工作流, switch to freeform help without lecturing Handling Deviations If the user wants to skip a stage: confirm and continue with what they need. If 上下文 is missing: ask tar获取ed questions before strong recommendations. Prefer concrete examples, trade-offs, and verification steps over generic advice. 质量 Bar Each recommendation should be actionable (what to do next). Call out 失败 modes relevant to 代理 Architecture (security, 扩展, UX, or ops). Keep tone direct and respectful of the user’s time.