copilot-instructions.md (1864B)
1 # Copilot Coding Agent — Squad Instructions 2 3 You are working on a project that uses **Squad**, an AI team framework. When picking up issues autonomously, follow these guidelines. 4 5 ## Team Context 6 7 Before starting work on any issue: 8 9 1. Read `.squad/team.md` for the team roster, member roles, and your capability profile. 10 2. Read `.squad/routing.md` for work routing rules. 11 3. If the issue has a `squad:{member}` label, read that member's charter at `.squad/agents/{member}/charter.md` to understand their domain expertise and coding style — work in their voice. 12 13 ## Capability Self-Check 14 15 Before starting work, check your capability profile in `.squad/team.md` under the **Coding Agent → Capabilities** section. 16 17 - **🟢 Good fit** — proceed autonomously. 18 - **🟡 Needs review** — proceed, but note in the PR description that a squad member should review. 19 - **🔴 Not suitable** — do NOT start work. Instead, comment on the issue: 20 ``` 21 🤖 This issue doesn't match my capability profile (reason: {why}). Suggesting reassignment to a squad member. 22 ``` 23 24 ## Branch Naming 25 26 Use the squad branch convention: 27 ``` 28 squad/{issue-number}-{kebab-case-slug} 29 ``` 30 Example: `squad/42-fix-login-validation` 31 32 ## PR Guidelines 33 34 When opening a PR: 35 - Reference the issue: `Closes #{issue-number}` 36 - If the issue had a `squad:{member}` label, mention the member: `Working as {member} ({role})` 37 - If this is a 🟡 needs-review task, add to the PR description: `⚠️ This task was flagged as "needs review" — please have a squad member review before merging.` 38 - Follow any project conventions in `.squad/decisions.md` 39 40 ## Decisions 41 42 If you make a decision that affects other team members, write it to: 43 ``` 44 .squad/decisions/inbox/copilot-{brief-slug}.md 45 ``` 46 The Scribe will merge it into the shared decisions file.