▸case-14 Feature 'search-filters' includes test logs, build logs, screenshots, and code review approvals in its evidence inventory, but stakeholder acceptance sign-off is missing. Review the stage transition for `docs/full-stack-development/requirements/search-filters/00-gate-report.md`. | pass→pass | 7,244 | 19,458 | +169% | 1 | 1 | 0% | 1,362 | 2,337 | +72% | 0 | 0 | — |
▸case-21 Run the stage gate review for feature 'custom-webhooks' using `00-stage.json` and `00-artifact-registry.json`. Ensure the final report artifact is saved at the standard path. | fail→fail | 10,240 | 15,662 | +53% | 1 | 1 | 0% | 176 | 643 | +265% | 0 | 0 | — |
▸case-01 We just finished updating the requirements for the 'account-settings' feature and want to move forward to the visual design phase. Please evaluate our stage inputs and current artifacts to generate the gate report file at `docs/full-stack-development/requirements/account-settings/00-gate-report.md` confirming if this transition is approved. | fail→fail | 5,114 | 16,687 | +226% | 1 | 1 | 0% | 213 | 935 | +339% | 0 | 0 | — |
▸case-13 Feature 'api-rate-limiter' has completed unit test logs, build logs, and acceptance evidence in its evidence inventory, but lacks peer code review sign-off documentation. Generate `docs/full-stack-development/requirements/api-rate-limiter/00-gate-report.md` for stage review. | pass→pass | 15,648 | 13,256 | -15% | 1 | 1 | 0% | 2,347 | 1,897 | -19% | 0 | 0 | — |
▸case-02 Our team is ready to begin frontend coding for the 'user-onboarding' feature. Can you run the stage gate review against our workspace stage artifacts and produce the gate report document in `docs/full-stack-development/requirements/user-onboarding/00-gate-report.md` to indicate if we are cleared to start implementation? | fail→fail | 14,686 | 16,907 | +15% | 1 | 1 | 0% | 286 | 681 | +138% | 0 | 0 | — |
▸case-03 We have collected our completion evidence for the 'token-transfer' feature and need a final gate review. Please check `00-stage.json` and the evidence inventory, run the necessary stage review checks, and publish the formal `00-gate-report.md` under `docs/full-stack-development/requirements/token-transfer/` detailing whether the stage passes. | fail→fail | 6,157 | 16,400 | +166% | 1 | 1 | 0% | 315 | 774 | +146% | 0 | 0 | — |
▸case-04 We are working on the 'user-profile' feature and need to design the high-fidelity UI screens in Figma. Can you generate the vector layout frames and CSS styles for our user profile page? | fail→pass | 40,499 | 8,141 | -80% | 1 | 1 | 0% | 8,229 | 1,663 | -80% | 0 | 0 | — |
▸case-05 We need to draft the functional specification document for our 'billing-subscriptions' module. Can you write the user stories, API endpoints, and acceptance criteria text for this feature? | fail→fail | 22,125 | 18,070 | -18% | 1 | 1 | 0% | 3,191 | 3,832 | +20% | 0 | 0 | — |
▸case-06 Our developers completed the 'auth-mfa' module logic. Can you write the Jest unit test code scripts to test the MFA verification endpoint? | fail→pass | 16,707 | 20,999 | +26% | 1 | 1 | 0% | 3,682 | 2,212 | -40% | 0 | 0 | — |
▸case-07 The product owner verbally approved the 'shopping-cart' feature requirements in Slack, but `00-stage.json` shows the requirements stage status as 'in_review'. The design team is eager to start Figma mockups immediately. Evaluate the transition and generate the report at `docs/full-stack-development/requirements/shopping-cart/00-gate-report.md`. | fail→pass | 15,172 | 11,765 | -22% | 1 | 1 | 0% | 354 | 2,579 | +629% | 0 | 0 | — |
▸case-08 The designer finished Figma mockups for 'checkout-flow', but no visual review tool check was run yet. The developer wants to jump straight into React coding. Perform the gate review and create `docs/full-stack-development/requirements/checkout-flow/00-gate-report.md`. | pass→pass | 22,811 | 12,499 | -45% | 1 | 1 | 0% | 2,634 | 2,548 | -3% | 0 | 0 | — |
▸case-09 In `00-stage.json` for feature 'settings-page', the field `visualDesignApproved` is set to true by a contributor, but the evidence inventory has no Figma links, Pencil drawings, or image files attached. Perform the review and write `docs/full-stack-development/requirements/settings-page/00-gate-report.md`. | pass→pass | 9,198 | 17,493 | +90% | 1 | 1 | 0% | 1,702 | 2,663 | +56% | 0 | 0 | — |
▸case-10 We are attempting to close the verification stage for 'email-notifications'. Build outputs, UI screenshots, code review approvals, and acceptance sign-offs are in the evidence inventory, but automated test logs are missing. Run the verification review for `docs/full-stack-development/requirements/email-notifications/00-gate-report.md`. | pass→pass | 25,404 | 14,220 | -44% | 1 | 1 | 0% | 3,162 | 1,944 | -39% | 0 | 0 | — |
▸case-11 For feature 'data-export-csv', the evidence inventory contains test execution logs, code review notes, and acceptance approvals, but build execution logs are omitted. Evaluate the completion gate for `docs/full-stack-development/requirements/data-export-csv/00-gate-report.md`. | pass→pass | 10,351 | 13,889 | +34% | 1 | 1 | 0% | 1,898 | 2,835 | +49% | 0 | 0 | — |
▸case-12 Feature 'dark-mode-toggle' is a web UI component under completion review. Test logs, build logs, code review sign-off, and product acceptance exist, but no application UI screenshots were uploaded. Evaluate the stage for `docs/full-stack-development/requirements/dark-mode-toggle/00-gate-report.md`. | pass→pass | 10,374 | 18,864 | +82% | 1 | 1 | 0% | 1,887 | 2,988 | +58% | 0 | 0 | — |
▸case-15 In `00-stage.json` for 'file-uploader', the development lead added a note saying 'Stage approved by team lead declaration'. No formal gate tool checks were run. Generate `docs/full-stack-development/requirements/file-uploader/00-gate-report.md` reflecting this declaration. | fail→pass | 12,336 | 10,558 | -14% | 1 | 1 | 0% | 1,279 | 2,257 | +76% | 0 | 0 | — |
▸case-16 Requirements for 'workspace-invites' have passed review. Run `review_stage_gate` to generate `docs/full-stack-development/requirements/workspace-invites/00-gate-report.md` and identify the authorized subsequent phase. | fail→fail | 11,206 | 11,532 | +3% | 1 | 1 | 0% | 287 | 719 | +151% | 0 | 0 | — |
▸case-17 We are conducting a stage gate review for feature 'sso-login'. The stage file `00-stage.json` exists, but `00-artifact-registry.json` is missing from the directory. Produce the evaluation report at `docs/full-stack-development/requirements/sso-login/00-gate-report.md`. | pass→pass | 13,276 | 16,633 | +25% | 1 | 1 | 0% | 2,681 | 2,429 | -9% | 0 | 0 | — |
▸case-18 We have updated Figma visual designs for 'activity-feed' in the artifact registry and want to verify them before frontend work starts. Run the appropriate gate tool and output report to `docs/full-stack-development/requirements/activity-feed/00-gate-report.md`. | fail→fail | 8,765 | 11,194 | +28% | 1 | 1 | 0% | 212 | 531 | +150% | 0 | 0 | — |
▸case-19 Evaluate whether feature 'audit-trail' can move to its next stage by inspecting `00-stage.json` and running the core gate evaluation tool. Generate `docs/full-stack-development/requirements/audit-trail/00-gate-report.md`. | fail→fail | 5,015 | 37,412 | +646% | 1 | 1 | 0% | 261 | 964 | +269% | 0 | 0 | — |
▸case-20 Feature 'password-reset' has complete evidence inventory including test logs, build output, UI screenshots, code review sign-off, and acceptance approval. Evaluate the stage and create `docs/full-stack-development/requirements/password-reset/00-gate-report.md`. | fail→fail | 12,671 | 28,302 | +123% | 1 | 1 | 0% | 2,352 | 3,346 | +42% | 0 | 0 | — |
▸case-22 Our backend lead requested bypassing visual design and jumping straight to implementation coding for feature 'payout-engine'. Perform the stage gate check and output `docs/full-stack-development/requirements/payout-engine/00-gate-report.md`. | fail→pass | 23,045 | 19,898 | -14% | 1 | 1 | 0% | 2,983 | 2,333 | -22% | 0 | 0 | — |