Bidding Super Master

Bidding documents often span multiple files, response rounds, scoring points, and disqualification conditions, making manual review error-prone. This skill separates the workflow into three stages: extracting requirements from tender or procurement files, checking bidder responses, and drafting a technical proposal based on the review baseline. It is useful for engineering and commercial teams that need consistent document cross-checking.

How It Works

• Stage 1: Parse tender or procurement files in the project directory, extract requirements, scoring points, and risks, and generate files under 审查输出/, including 评分响应矩阵.xlsx and 废标风险清单.xlsx.
• Stage 2: Use the Stage 1 output as the baseline to compare bidder response files, then generate Phase 2 review and detailed discrepancy reports.
• Stage 3: When required source materials are available, generate a proposal outline, write chapters, merge Word documents, and produce a technical proposal, CV/resume files, and a material reference list.

The skill does not hard-code business rules. It fetches extract, check, or write rules from the backend get_rule endpoint and can merge user-provided .md custom rules, with custom rules taking precedence on conflicts. It checks project directories, baseline files, and source materials before execution, and pauses when required inputs are missing rather than inventing content.

Boundaries

• It requires a local project directory and a configured backend environment, with BIDDING_BACKEND_BASE pointing to the rule service.
• Stages 2 and 3 depend on Stage 1; without 评分响应矩阵.xlsx and related baseline files, the workflow should stop.
• Stage 3 requires user-provided materials; missing project experience may use explicitly labeled example data only.
• Test mode is intended for development debugging and should not be used as the normal production path.