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

feat: orchestrator marks plan steps complete after LGTM

Browse source
This commit is contained in:
Bryan Ramos 2026-04-01 17:19:38 -04:00
parent d3bc447563
commit f7d3e1bd73
2 changed files with 10 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

17
agents/architect.md
View file

@ -102,12 +102,10 @@ What could go wrong. Edge cases. Breaking changes.
[see Risk Tags section below] [see Risk Tags section below]
## Implementation Plan ## Implementation Plan
Ordered list of concrete steps. Each step must include: Ordered list of concrete steps using checkbox format. Each step must include:
- **What**: The specific change - [ ] **Step N: [short title]** — What, Where, How
- **Where**: File path(s)
- **How**: Implementation approach
Each step scoped to a single logical change. Each step scoped to a single logical change. The orchestrator checks off steps as they are completed and approved — do not use any other format for steps.
## Acceptance Criteria ## Acceptance Criteria
Numbered list of specific, testable criteria. Numbered list of specific, testable criteria.
@ -157,11 +155,10 @@ What could go wrong. Edge cases. Breaking changes. Security implications.
[see Risk Tags section below] [see Risk Tags section below]
## Implementation Plan ## Implementation Plan
Ordered list of concrete steps. Each step must include: Ordered list of concrete steps using checkbox format. Each step must include:
- **What**: The specific change (function to add, interface to implement, config to update) - [ ] **Step N: [short title]** — What/Where/How. Add **Why** if non-obvious.
- **Where**: File path(s) and location within the file
- **How**: Implementation approach including function signatures and key logic Each step scoped to a single logical change — one commit's worth of work. The orchestrator checks off steps as they are completed and approved — do not use any other format for steps.
- **Why**: Brief rationale if the step is non-obvious
Each step scoped to a single logical change — one commit's worth of work. Each step scoped to a single logical change — one commit's worth of work.

4
skills/orchestrate/SKILL.md
View file

@ -242,11 +242,13 @@ When multiple risk tags are present, take the union of all mandatory reviewers.
### Git flow ### Git flow
Workers signal `RFR` when done. You control commits: Workers signal `RFR` when done. You control commits:
- `LGTM` → worker commits - `LGTM` → worker commits → **update the plan file: mark the completed step as `- [x]`**
- `REVISE` → worker fixes and resubmits with `RFR` - `REVISE` → worker fixes and resubmits with `RFR`
- Merge worktree branches after individual validation - Merge worktree branches after individual validation
- On Tier 2+: merge each worker's branch after validation, resolve conflicts if branches overlap - On Tier 2+: merge each worker's branch after validation, resolve conflicts if branches overlap
Only the orchestrator updates the plan file. Workers must not modify `.claude/plans/`.
### Review signals ### Review signals
| Signal | Direction | Meaning | | Signal | Direction | Meaning |