Cursor rule Cursor
AIDocxWorkFlow — 9-stage modular test-case generation pipeline.
not rated 2 2mo ago A 4,099 tokens
original MIT
2Stars on the repository
36Mods indexed here, across every type
2mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown
Cursor rule Cursor
A set of audit rules for documents produced by an automated goal loop. It checks names, references, structured IDs, test mappings, and consistency between positive and negative test scenarios.
not rated 2 2mo ago A 1,007 tokens
original MIT
Cursor rule Cursor
A rule for checking compliance risks in the requirements-review stage of a game project. It covers areas such as age limits, spending restrictions, prize probabilities, sensitive words, privacy, advertising, and game-licence requirements.
not rated 2 2mo ago A 3,655 tokens
original MIT
Cursor rule Cursor
A method for estimating software testing work from a requirements document and any clarified details. It breaks the work into areas, testing types, time estimates, risks, blockers, and delivery milestones.
not rated 2 2mo ago A 4,721 tokens
original MIT
Cursor rule Cursor
A clarification and approval stage between requirements review and detailed breakdown. People decide how to resolve open questions, and the results are saved in an exit-permission file.
not rated 2 2mo ago A 26 tokens
original MIT
Cursor rule Cursor
A requirements-review stage that checks an attached .docx, .md, or .txt file before reviewing it. It produces a review or a failure report when the file is missing, unreadable, or too short.
not rated 2 2mo ago A 19 tokens
original MIT
Cursor rule Cursor
An optional planning stage in the AIDocxWorkFlow process for organizing an iteration, meaning a planned period of development. It reviews a backlog, collects project details, and creates a schedule for people, work hours, and dates.
not rated 2 2mo ago A 22 tokens
original MIT
Cursor rule Cursor needs its repo
A requirements-breakdown stage that divides a business request into Epics, Stories, requirement objects, and testable feature points. An Epic is a large area of work, while a Story describes a smaller user-facing function.
not rated 2 2mo ago A 36 tokens
original MIT
Cursor rule Cursor
A workflow stage that turns a requirements backlog into text-based page prototypes and a Mermaid diagram showing how pages connect. Each prototype lists interface elements, layouts, state changes, and test reference IDs.
not rated 2 2mo ago A 19 tokens
original MIT
Cursor rule Cursor
A workflow rule set for exporting flowcharts from approved product requirements and prototypes. It checks that required backlog and design files exist before the flowchart stage begins.
not rated 2 2mo ago A 21 tokens
original MIT
Cursor rule Cursor needs its repo
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
not rated 2 2mo ago A 20 tokens
original MIT
Cursor rule Cursor
触åÂÂæ¹å¼Âï¼Â/aidocx-s6-test-cases æÂÂç²Âè´´ S5 testpoints.json.
not rated 2 2mo ago A 98 tokens
original MIT
Cursor rule Cursor needs its repo
A standalone review stage for checking generated software test cases against earlier requirement, workflow, coverage, and omission records. It is part of a larger process whose materials and names are partly documented in Chinese.
not rated 2 2mo ago A 19 tokens
original MIT
Cursor rule Cursor needs its repo
A quality-review and self-improvement procedure for an eight-stage document workflow. It analyzes earlier test cases, business flows, review reports, and feedback logs before producing improvement work.
not rated 2 2mo ago A 19 tokens
original MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: