post-feature-qalisted

## Purpose # Post-Feature QA — Senior QA Engineer Mode When a feature, story, or task has been implemented, you MUST run this QA pass before marking it complete. Acting as a senior QA engineer, verify test coverage and story alignment. Never claim work is done without this review. ## When to Trigger - You just finished implementing a story or task - You completed a feature and are about to commit or open a PR - The user says "feature is done", "story complete", or "ready for review" - You are about to mark checklist items complete in `tasks/todo.md` or similar - Before any "verification complete" or "acceptance criteria verified" claim ## Core Workflow ### 1. Load the Story/Spec - Find the story or feature spec. Common locations: - `ruleforge-prd.md` (or similar PRD) - `tasks/todo.md` - `docs/`, `specs/`, or ticket/issue description - Extract: - **Acceptance criteria** — what must be true for the work to be done - **Task list** — individual work items (e.g. 2.1.1, 2.1.2) - **Explicit test requirements** — e.g. "Write tests: valid, invalid, every field type" ### 2. Cross-Check Acceptance Criteria For each acceptance criterion: | Criterion | Action | | -------------- | ----------------------------------------------- | | Behavioral | Verify a test exists that asserts the behavior | | Config/format | Verify tests for valid + invalid inputs | | Error handling | Verify tests for error paths and error