storkit: done 432_story_complete_setup_wizard_with_mcp_tools_and_agent_driven_file_generation
This commit is contained in:
-24
@@ -1,24 +0,0 @@
|
||||
---
|
||||
name: "QA agent reviews code changes against acceptance criteria"
|
||||
---
|
||||
|
||||
# Story 431: QA agent reviews code changes against acceptance criteria
|
||||
|
||||
## User Story
|
||||
|
||||
As a project owner, I want the QA agent to actually verify that the coder's implementation matches the story's acceptance criteria, so that incomplete or incorrect work is caught before merge.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] QA agent reads the story's acceptance criteria before reviewing code
|
||||
- [ ] QA agent reads the full diff against master to understand what changed
|
||||
- [ ] For each AC, QA agent verifies the code addresses it and explains how
|
||||
- [ ] QA agent flags incomplete implementations: todo!(), unimplemented!(), missing match arms, placeholder values
|
||||
- [ ] QA agent checks that new code has corresponding test coverage
|
||||
- [ ] QA agent produces a structured report: each AC with pass/fail and explanation
|
||||
- [ ] If any AC is not met, QA rejects the story with a clear reason so the coder can fix it
|
||||
- [ ] Deterministic gates (clippy, tests) still run as a prerequisite before the AC review
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
+1
@@ -1,5 +1,6 @@
|
||||
---
|
||||
name: "Complete setup wizard with MCP tools and agent-driven file generation"
|
||||
agent: "coder-opus"
|
||||
---
|
||||
|
||||
# Story 432: Complete setup wizard with MCP tools and agent-driven file generation
|
||||
Reference in New Issue
Block a user