feat: add ba + pm agents to multi-agent dev workflow
Stakeholder should only need to state a business goal/priority, not pick between implementation options or break work into tasks themselves. `ba` turns a business ask into a concrete spec grounded in docs/asset-license-management.md, `pm` breaks that spec into an ordered, dependency-aware sequence of feature-implementer-sized tasks. Neither writes code or resolves business-rule ambiguity — that stays with the stakeholder. Also fixes code-reviewer.md/feature-implementer.md pointing at the old ../processes/asset-license-management.md path — the doc moved into docs/ inside this repo a while ago. Co-Authored-By: Claude Sonnet 5 <[email protected]>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
87e2cca019
commit
9e08c3f994
@@ -4,7 +4,7 @@ description: Review a finished diff/feature in asset-license-mgmt for correctnes
|
||||
tools: Read, Grep, Glob, Bash
|
||||
---
|
||||
|
||||
Review the diff against the domain rules in `../processes/asset-license-management.md`. Focus on:
|
||||
Review the diff against the domain rules in `docs/asset-license-management.md`. Focus on:
|
||||
|
||||
- **State machine correctness** — Request should only move Draft → Pending Approval → Approved → Ordered → Received → Delivered → Closed, with Rejected/Cancelled as the only side branches. Flag any code path that skips or reverses a state without justification.
|
||||
- **Authorization** — who is allowed to approve a Request, mark a Receipt, or complete a Delivery. Flag missing or client-side-only checks.
|
||||
|
||||
Reference in New Issue
Block a user