Shared hard rules enforced across all squad agents
中文简介正在准备中。当前显示原文说明。
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication. These were previously duplicated in every charter's Collaboration section (~300 bytes × 18 agents = ~5.4KB of redundant context). Now centralized here.
The coordinator's spawn prompt already instructs agents to read decisions.md and their history.md. This skill adds the patterns for WRITING decisions and requesting help.
Use the TEAM ROOT path provided in your spawn prompt. All .squad/ paths are relative to this root. If TEAM ROOT is not provided (rare), run git rev-parse --show-toplevel as fallback. Never assume CWD is the repo root.
After making a decision that affects other team members, write it to:
.squad/decisions/inbox/{your-name}-{brief-slug}.md
Format:
### {date}: {decision title}
**By:** {Your Name}
**What:** {the decision}
**Why:** {rationale}
If you need another team member's input, say so in your response. The coordinator will bring them in. Don't try to do work outside your domain.
If you have reviewer authority and reject work: the original author is locked out from revising that artifact. A different agent must own the revision. State who should revise in your rejection response.
.squad/decisions.md — always use the inbox drop-box还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Shared hard rules enforced across all squad agents
中文简介正在准备中。当前显示原文说明。
Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content.
中文简介正在准备中。当前显示原文说明。
Migrate API controller scope checks to framework-enforced authorization policies while preserving ownership checks.
中文简介正在准备中。当前显示原文说明。
Review API DTO implementations for contract/domain separation, mapping patterns, and REST compliance
中文简介正在准备中。当前显示原文说明。
Register shared claims transformation and hierarchical role policies in the API without breaking existing scope enforcement.
中文简介正在准备中。当前显示原文说明。
How to write comprehensive architectural proposals that drive alignment before code is written
中文简介正在准备中。当前显示原文说明。