Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/silenceinsect/aidocxworkflow/stage_s2_5_iterationgit clone --depth 1 https://github.com/SilenceInsect/AIDocxWorkFlowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/silenceinsect/aidocxworkflow/stage_s2_5_iteration)<a href="https://agentmods.dev/rules/silenceinsect/aidocxworkflow/stage_s2_5_iteration"><img src="https://agentmods.dev/badge/rules/silenceinsect/aidocxworkflow/stage_s2_5_iteration.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00022 | $0.03269 |
| Opus 5 | $0.00011 | $0.01635 |
| Sonnet 5 | $0.00004 | $0.00654 |
| Haiku 4.5 | $0.00002 | $0.00327 |
Grade A, and why
STAGE_S2_5_ITERATION scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIDocxWorkFlow S2.5 — 迭代规划
⚠️ 全流程模式默认跳过本阶段（opt-in）
- S2.5 迭代规划只解决"开发节奏/资源/排期"问题，对 S5 测试点、S6 用例的产出数量/质量无强关系。
- 全流程模式默认不执行 S2.5。如需包含：执行 S2 之前显式声明
AIDOCX_INCLUDE_S2_5=true（详见.cursor/rules/AIDocxWorkFlow.mdc顶部「编排开关」节）。- 独立调用方式不变：用户主动输入
/aidocx-s2-5-iteration或粘贴 S2 backlog 时，直接执行 S2.5（不受AIDOCX_INCLUDE_S2_5控制）。
独立阶段：可以单独调用。上游材料（S2 backlog）审查合格后开始，失败写失败报告。
Step 0 — 项目配置收集（强制前置，配置不全不得进入 7 步规划）
执行 S2.5 时，检测到项目配置不完整，必须主动询问用户，逐项确认。禁止自行假设默认值后跳过。
必须收集的配置参数
| 参数 | 说明 | 示例 |
|---|---|---|
| 项目名（req_name） | 需求名称 | 游戏道具商城系统 |
| 版本名（version） | 版本标识 | v1.0 |
| 排期开始日期 | 迭代第一天 | 2025-07-01 |
| 排期截止日期 | 迭代最后一天 | 2025-07-12 |
| 策划预估工时（h） | 产品策划阶段估算工时 | 40h |
| 前端预估工时（h） | 前端开发估算工时 | 80h |
| 后端预估工时（h） | 后端开发估算工时 | 120h |
| 测试预估工时（h） | 测试估算工时 | 60h |
| 团队规模 | 各角色人数 | 前端2人·后端3人·测试2人 |
| 迭代总工时（周） | 任务管线估算总时长 | 1.5周 |
快速迭代参考基准（1.5 周全流程）
迭代周期 1.5 周 ≈ 7.5 工作日 ≈ 60h/人
- 前端 2 人：共 120h
- 后端 3 人：共 180h
- 测试 2 人：共 120h
- 合计：420h
配置保存
收集完成后，必须将配置保存为 project_config.json 并写入输出目录。
阶段入口
触发方式：/aidocx-s2-5-iteration 或粘贴 S2 backlog
前置材料（必须全部满足）：
| 材料 | 来源 | 审查要求 |
|---|---|---|
| S2 backlog.md | workflow_assets/<req_name>/<version>/「S2 需求拆解」/backlog.md |
存在且含 Epic/Story/Task |
| S2 requirement_objects.md | workflow_assets/<req_name>/<version>/「S2 需求拆解」/requirement_objects.md |
存在且含需求对象 + 功能点（工时估算依据） |
| project_config.json | workflow_assets/<req_name>/<version>/「S2.5 迭代规划」/project_config.json |
存在且全部字段填写 |
材料缺失时：生成失败报告，停止 S2.5。
§1.4 LLM 必读材料（阶段前置）
开始 7 步规划前，必须先读取以下全部材料。
| # | 材料 | 路径 | 读取原因 |
|---|---|---|---|
| 1 | 8 模块总表 | .cursor/MODULES.md（§1 总表） |
迭代任务按模块前缀组织；负载均衡以模块为单位 |
| 2 | S2 backlog | workflow_assets/<req_name>/<version>/「S2 需求拆解」/backlog.md |
迭代规划的对象；所有 Story/FP 的优先级和工作量是规划基准 |
| 3 | 需求对象 | workflow_assets/<req_name>/<version>/「S2 需求拆解」/requirement_objects.json |
OBJ 层工作量估算更细 |
核心任务
将 S2 拆解好的任务转化为团队可执行的迭代计划，包含 7 步规划。
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 289 lines · 22 tokens per session scan A 13dc3540a8b5
STAGE_S2_5_ITERATION is a cursor rule published in the GitHub repository SilenceInsect/AIDocxWorkFlow (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 3,269 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).