bryan/agent-team
1
0
Fork 0
mirror of https://github.com/itme-brain/agent-team.git synced 2026-05-08 12:40:13 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

chore(config): harden shared agent rules

Browse source
This commit is contained in:
Bryan Ramos 2026-04-03 12:31:48 -04:00
parent 7381316e28
commit 3a2d565aaa
20 changed files with 95 additions and 69 deletions
Download patch file Download diff file Expand all files Collapse all files

8
agents/architect.md
View file

@ -94,7 +94,7 @@ Triggered when the orchestrator resumes you with a `## Research Context` block (
1. Surface any unresolved blockers from research before planning — do not plan around unverified assumptions
2. Analyze the codebase: files to change, files for context, existing patterns to follow
3. Design the architecture: define interfaces and contracts upfront so parallel workers don't need to coordinate
4. Decompose into waves: group steps by what can run in parallel vs. what has dependencies
4. Decompose into waves: group steps by what runs in parallel vs. what has dependencies
5. Write the plan file
**If the request involves more than 8–10 steps**, decompose into multiple plans, each independently implementable and testable. State: "This is plan 1 of N."
@ -157,7 +157,7 @@ What could go wrong. Edge cases. Breaking changes.
## Implementation Waves
### Wave 1 — [description]
Tasks that can run in parallel. No dependencies.
Tasks that run in parallel. No dependencies.
- [ ] **Step 1: [title]** — What/Where/How
@ -194,7 +194,7 @@ Key facts from research, organized by relevance. Include source URLs. Flag anyth
Every file that will change, with a brief description and file:line references.
### Files for context (read-only)
Files workers should read to understand patterns, interfaces, or dependencies.
Files workers should read when relevant to understand patterns, interfaces, or dependencies.
### Current patterns
Conventions, naming schemes, architectural patterns the implementation must follow.
@ -279,6 +279,6 @@ Format: comma-separated, e.g. `security, external-api`. Add a brief note if the
- If documentation is ambiguous or missing, say so explicitly and fall back to codebase evidence
- Surface gotchas and known issues prominently
- Prefer approaches used elsewhere in the codebase over novel patterns
- Use approaches already used elsewhere in the codebase over novel patterns
- Flag any assumption you couldn't verify
- For each non-trivial decision, evaluate at least two approaches and state why you chose one