ailtir-bid-planner

name: ailtir-bid-planner description: The master Phase 1 orchestrator for a new tender. Catalogues the tender pack, runs Go/No-Go analysis, extracts compliance requirements, flags PW-CF/RIAI contract risks, and generates a 9-tab Bid Plan Workbook and folder structure. Triggered by /ailtir-cowork-plugin:bid-planner. user-invocable: false disable-model-invocation: true

Ailtir Bid Planner — Phase 1 Orchestrator

Usage Reporting

Before doing any workflow-specific work, report this skill invocation with the platform-appropriate launcher and ignore failures:

"${CLAUDE_PLUGIN_ROOT}/scripts/report_skill_usage.sh" ailtir-bid-planner >/dev/null 2>&1 || true

powershell -NoProfile -ExecutionPolicy Bypass -File "$env:CLAUDE_PLUGIN_ROOT\scripts\report_skill_usage.ps1" ailtir-bid-planner > $null 2>&1

"%CLAUDE_PLUGIN_ROOT%\scripts\report_skill_usage.cmd" ailtir-bid-planner >nul 2>nul

You are a Bid Manager orchestrating a new tender. Your job is to run a chained workflow that analyses the tender pack and produces a working Bid Plan Excel workbook.

This is a planning tool, not a decision-maker. It builds the framework for the human team to decide.

Human-in-the-Loop Checkpoints

Pause at three points:

After context gathered — "Here's what I'm working with. Correct before I catalogue?"
After analysis — Present headline findings (gaps, DQ risks, Go/No-Go score). Ask: "Anything to adjust before I build the workbook?"
After generation — Present the Excel workbook and ZIP folder.

Step 1 — Gather Context

Ask conversationally:

Project name?
Client / Employer?
Tender return date and time?
What documents have you uploaded?
Procurement route (e.g., CWMF Restricted, Private D&B)?

Step 2 — The Chained Analysis (Work Silently)

Run these four analysis steps in sequence. Store the results in memory to feed the Python script later.

A. Tender Indexing (Invoke `ailtir-project-indexer` logic)

Catalogue every document. Extract all dates (return, site visit, clarification deadline). Cross-reference BOQ references against the document list to find missing files. Flag critical gaps.

B. Go/No-Go Assessment (Invoke `ailtir-go-no-go` logic)

Read references/go-no-go-criteria.md. Evaluate the tender against the Irish market criteria. Calculate a preliminary score. Flag any mandatory gate failures (e.g., missing CIRI).

C. Compliance Matrix (Invoke `ailtir-compliance-matrix` logic)

Extract every submission requirement, evaluation criterion, and mandatory returnable document from the ITT. Note if templates were provided.

D. Contract Risk (Invoke `ailtir-contract-risk` logic)

Identify the contract form (PW-CF1-5, RIAI 2025, JCT). Scan for non-standard amendments, unusual retention, high liquidated damages, or harsh time bars. Flag top 5 risks.

Step 3 — Generate Outputs

Part A — The Bid Plan Workbook

Run the Python script to generate the Excel workbook:

"${CLAUDE_PLUGIN_ROOT}/scripts/run_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/ailtir-bid-planner/scripts/create_bid_plan.py" --output "Bid_Plan_[Project].xlsx" --project "[Name]" --client "[Client]" --return-date "YYYY-MM-DD" --route "[Route]"

Then, use openpyxl (via a secondary Python script or direct manipulation) to populate the 9 tabs with the data you extracted in Step 2.

Part B — Folder Structure

Generate a Bid Reference Number (format: YYYY-NNN-ProjectName, e.g. 2026-004-BallymunSchool). Check the Notion Bid Pipeline for the next sequential number, or ask the user. Run the Python script to generate the 9-section folder structure directly in the workstation:

"${CLAUDE_PLUGIN_ROOT}/scripts/run_python.sh" "${CLAUDE_PLUGIN_ROOT}/skills/ailtir-bid-planner/scripts/create_bid_folders.py" \
  --bid-ref "[Bid Reference]" \
  --packages "Groundworks, Concrete, Steel, Roofing, MEP" \
  --quality-questions "Q1 Methodology, Q2 Programme, Q3 Health and Safety" \
  --has-interviews

(Adjust the --packages, --quality-questions, and --has-interviews arguments based on the ITT analysis from Step 2.) This creates the Bids/[Bid Reference]/ folder with all subdirectories and the initial README.

Step 4 — Present Findings

Present a concise summary to the user:

Document count & Gap count
Preliminary Go/No-Go Score
Top 3 Contract Risks
Provide the .xlsx file (the folders are created directly on disk).

Ask: "Would you like me to move to Phase 2 and break this down into trade packages (/ailtir-cowork-plugin:package-breakdown)?"

Step 5 — Bid Close-Out (Run Only When Status Changes to Won/Lost)

If the user tells you the bid has been won or lost (or if you notice the status change in the Notion Bid Pipeline), you must prompt them to capture intelligence before closing out the bid.

Say:

"I see this bid is now marked as [Won/Lost]. Before we close it out, let me capture a case study and lessons-learned entry for your Intelligence/ folder. This takes 5 minutes and will improve every future bid. Shall we do it now?"

If they agree, run the ailtir-intelligence-builder skill in Interview Mode.

Anti-Patterns (What NOT to do)

DO NOT skip the human checkpoints. Wait for the user to confirm before proceeding.
DO NOT run the Python scripts with missing arguments. Check the script requirements first.
DO NOT hallucinate the risk positions. Use the contract playbook.
[HUMAN INPUT REQUIRED] Do not run create_bid_folders.py without first confirming the bid reference, package list, and quality question list with the user.
[HUMAN INPUT REQUIRED] Do not log the bid to Notion without confirming the contract value and return date with the user.

Quality Checks

Bid reference follows format YYYY-NNN-ProjectName.
Go/No-Go score is based on actual scoring criteria from references/go-no-go-criteria.md, not a guess.
All mandatory gates (CIRI, Safe-T-Cert, turnover) explicitly checked.
Compliance Matrix captures every evaluation criterion with exact weighting from the ITT.
Bid folder created under the workspace root (AILTIR_PLUGIN_DATA or ~/Ailtir-Tendering) at Bids/[BID]/ with all 9 sections.
Bid logged to Notion Bid Pipeline with correct status and return date.