Cursor rule Cursor
AIDocxWorkFlow — 9-stage modular test-case generation pipeline.
2 1mo ago A 4,099 tokens
original MIT
Cursor rule Cursor
A set of project-wide rules for making decisions across the AIDocxWorkFlow stages. It defines where module information, stage instructions, skills, and project assets belong.
2 1mo ago A 13,646 tokens
original MIT
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.
2 1mo 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.
2 1mo 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.
2 1mo 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.
2 1mo 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.
2 1mo 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.
2 1mo ago A 22 tokens
original MIT
Cursor rule Cursor
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.
2 1mo 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.
2 1mo 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.
2 1mo ago A 21 tokens
original MIT
Cursor rule Cursor
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.
2 1mo ago A 20 tokens
original MIT
Cursor rule Cursor
触åÂÂæ¹å¼Âï¼Â/aidocx-s6-test-cases æÂÂç²Âè´´ S5 testpoints.json.
2 1mo ago A 98 tokens
original MIT
Cursor rule Cursor
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.
2 1mo ago A 19 tokens
original MIT
Cursor rule Cursor
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.
2 1mo ago A 19 tokens
original MIT
Skill Claude CodeCodexCursor
A tool for importing test-execution feedback and review results from Excel, CSV, or JSON files, standardizing the data, and saving it in a feedback-logs folder. Test-execution feedback records what happened when test cases were run.
2 1mo ago A 69 tokens
original MIT
Skill Claude CodeCodexCursor
A Chinese-language workflow stage that turns answered requirement questions into a final requirements document and an exit decision. It is used between an initial review and the next stage, where requirements are broken into implementation work.
2 1mo ago A 94 tokens
original MIT
Skill Claude CodeCodexCursor
A Chinese-language workflow stage for reviewing software requirements and checking whether important details are complete before development. It produces review documents, test coverage, acceptance checks, and a list of questions needing decisions.
2 1mo ago A 173 tokens
original MIT
Skill Claude CodeCodexCursor
A seven-step iteration-planning workflow for turning a software backlog into a development schedule. An iteration is a fixed period of work, and a backlog is the list of planned tasks.
2 1mo ago A 168 tokens
original MIT
Skill Claude CodeCodexCursor
A requirements-breakdown workflow for turning an approved product request into five levels: release, large feature, user story, requirement object, and smallest function.
2 1mo ago A 203 tokens
original MIT
Skill Claude CodeCodexCursor
A workflow step that turns a list of software features and user stories into page descriptions, interface elements, interaction states, and Mermaid flow diagrams. Mermaid is a text format for drawing diagrams.
2 1mo ago A 131 tokens
original MIT
Skill Claude CodeCodexCursor
A workflow stage that creates business flowcharts, interaction timelines, error decision trees, and risk lists from a project backlog and screen prototypes. A backlog is a structured list of planned work, while a prototype is an early version of the user interface.
2 1mo ago A 217 tokens
original MIT
Skill Claude CodeCodexCursor
A test-point generator for turning a software backlog into detailed checks. It follows project rules for naming requirements and functions consistently.
2 1mo ago A 139 tokens
original MIT
Skill Claude CodeCodexCursor
A test-case generator for AIDocxWorkFlow. Test cases are detailed checks that describe how to verify a requirement or feature, and it derives them from earlier test points, business flows, and module templates.
2 1mo ago A 130 tokens
original MIT