Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Construction Project Commander — Scope, Tasks & Progress

    1

    Turn fragmented construction records into traceable scope, tasks, dependencies, change logs and progress reports.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Construction Project Commander — Scope, Tasks & Progress

    Construction Project Commander — Scope, Tasks & Progress

    Example session with this skill installed

    Illustrative project report: On 10 October, wall framing is reported complete in the site log. Electrical rough-in is due 12 October but depends on approved shop drawing S-14, still pending. Ceiling closure is planned 14 October after rough-in and inspection. Door package delivery is unconfirmed. No cost data or inspection results are supplied. Build a status report, dependency/action register and evidence questions without inventing completion percentages or approvals.

    • Read your context and instructions
    • Compiled the construction project commander

    Project command report

    Reporting date: 10 October, year and timezone unconfirmed. Project name and overall baseline are not supplied. Overall status: at-risk sequence requiring owner review; no completion percentage is calculated. Evidence confidence: limited to the supplied site-log summary.

    Scope and dependency register

    Work itemSupplied stateDependencyAction
    Wall framingReported completeVerification against approved scopeObtain signed/authorized completion evidence and relevant quality records
    Electrical rough-inDue 12 October; actual progress unknownApproved S-14 shop drawingConfirm review owner, issue status and required release; do not start from an assumed approval
    Ceiling closurePlanned 14 OctoberRough-in complete and required inspectionKeep closure conditional; obtain inspection evidence before confirming readiness
    Door packageDelivery unconfirmedVendor/procurement confirmationRequest acknowledged delivery date and effect on installation sequence

    Priority actions

    A1: Project manager confirms S-14 reviewer and response deadline needed to protect the 12 October rough-in plan. Approval authority is not assigned by this report.
    A2: Electrical lead confirms actual readiness and feasible duration after drawing approval. No revised duration is invented.
    A3: Responsible inspection coordinator confirms inspection requirements, booking and evidence. No inspection is recorded as passed.
    A4: Procurement lead seeks written door delivery confirmation and checks affected tasks. Owners are proposed roles pending confirmation, not invented named assignments.

    Delay and risk position

    The S-14 → rough-in → inspection → ceiling sequence creates a potential constraint. Actual float, critical path and revised finish date cannot be determined without the approved schedule, durations and calendars. Flag this chain for schedule review; do not label every task critical without evidence.

    Change and cost control

    No approved changes, budget, commitments or actual cost data were supplied. Cost status and earned-value metrics are unknown. Record any proposed resequencing or acceleration as a decision/change candidate, with scope, authority and cost implications reviewed before execution.

    Evidence questions

    What is the approved schedule revision? Which drawing/version governs S-14? What is the current review status? Which framing scope is complete? What inspection records are required? What vendor evidence supports door delivery? Who can authorize each decision?

    Next steps

    Confirm project identity and reporting year; obtain governing records; assign actual owners; update dependency, RFI/submittal, procurement and decision logs. Preserve supplied status separately from verified status. No drawing, inspection, schedule change or site instruction has been approved or issued.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Keep project controls connected

    Construction Project Commander helps owners, contractors, project managers and site teams organize supplied construction records into practical project controls. It follows approved requirements and evidence rather than inventing progress.

    Supported work

    • Scope and work breakdown structure.
    • Task owners, dependencies, schedule and delay review.
    • Procurement, RFIs, submittals and decision logs.
    • Changes, costs, risks and coordination registers.
    • Quality and safety escalation records, closeout and commissioning tracking.
    • Evidence-based progress summaries and executive reporting.

    Works from authorized contracts, schedules, minutes, site reports, photos and spreadsheets. Calculations and exports depend on available tools and reliable inputs. Photos establish only visible information; they cannot prove concealed work, structural adequacy or code compliance. Without connectors, it produces manual controls. Approvals and external system changes remain with authorized people.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scanned

    Verified clean 8 days ago

    • Passed all security checks, Safe to install

    Listed8 days ago

    What's inside

    Frequently Asked Questions