Stats
Actions
Tags
Produce only the red-flag report from an existing tender manifest
How this command is triggered — by the user, by Claude, or both
Slash command
/roof-replacement-review:roof-redflags <tender-manifest.json>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /roof-redflags Resolve the plugin root from `CLAUDE_PLUGIN_ROOT` or use: `/home/reggiechan/021-CRE-150/plugins/roof-replacement-review` Invoke the `roof-qualification-check` and `roof-technical-review` skills against the supplied manifest (re-evaluates gates and qualitative flags without rebuilding from PDFs), then run: ## Summary Report: - Count of bids by compliance status - Critical red flags by bidder - Cross-bid patterns (common exclusions, price spread alert, substitution convergence) - Recommended next actions (addendum, clarification request, rejection)
Resolve the plugin root from CLAUDE_PLUGIN_ROOT or use:
/home/reggiechan/021-CRE-150/plugins/roof-replacement-review
Invoke the roof-qualification-check and roof-technical-review skills against the supplied manifest (re-evaluates gates and qualitative flags without rebuilding from PDFs), then run:
python3 "$CLAUDE_PLUGIN_ROOT/scripts/redflags.py" \
--manifest "<tender-manifest.json>" \
--out "<tender-manifest-dir>/../redflag_report.md"
Report:
npx claudepluginhub reggiechan74/021-cre-150 --plugin roof-replacement-review