9e08c3f99447cb65c477d943eca3ee2ff155e5bb
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]>
Description
No description provided
950 KiB
Languages
TypeScript
98%
CSS
1.7%
Dockerfile
0.2%