{
 "schema": "aiblocks-page/1",
 "id": "weekly-project-delay-evidence-assistant",
 "type": "agent",
 "name": "Project delay test reviewer",
 "summary": "Compare new task times with the original baseline. Get delay patterns and a keep, revise or wait recommendation for the current test.",
 "headline": "Project delay test reviewer",
 "subhead": "Share dated task updates, original estimates, completed work and the current improvement test. It separates waiting from active time and compares similar work under the same definitions. You get a delay brief and proposed next step. Thin evidence keeps the test unchanged; a small sample does not establish why the delay happened.",
 "job": {
  "id": "manage-projects",
  "name": "Plan projects and team capacity"
 },
 "level": "intermediate",
 "thinking": "high",
 "tested": true,
 "updated": "2026-11-03",
 "first_published": "2026-10-22",
 "inputs": [
  {
   "type": "question",
   "required": true,
   "label": "Question",
   "what": "the problem, decision or piece of work you want help with, and what a good outcome looks like"
  },
  {
   "type": "plan",
   "required": false,
   "label": "Plan",
   "what": "a dated plan: what to do, in what order, with a decision rule for each step"
  },
  {
   "type": "dataset",
   "required": true,
   "label": "Dataset",
   "what": "data files to process or analyse, such as a CSV or JSON export, logs, lab or sensor files, with their format and where they came from"
  }
 ],
 "outputs": [
  {
   "type": "audit_report",
   "required": true,
   "label": "Audit report",
   "what": "findings with evidence, severity, missing inputs and next actions"
  },
  {
   "type": "plan",
   "required": true,
   "label": "Plan",
   "what": "a dated plan: what to do, in what order, with a decision rule for each step"
  },
  {
   "type": "document",
   "required": true,
   "label": "Document",
   "what": "a finished document, such as a Word file, a PDF or a page of notes"
  }
 ],
 "you_give": [
  "Dated task updates with task ID, stage, start date, wait time or wait dates, and finish date (from your project tool export, a spreadsheet or status notes)",
  "The original estimate for each task",
  "The actual finish date for each completed task",
  "The fix you are testing: what changed, the date it started and the review date",
  "How far a stage's waiting time may move before it counts as a new pattern (optional; the agent proposes a rule if you give none)",
  "Last review's record (optional, from the second week on)"
 ],
 "you_get": [
  "A delay trend brief: waiting time and working time by stage, against the baseline",
  "A list of new delay patterns, or a clear note that there is no new pattern this week",
  "A keep, revise or stop call on the fix, with the sample size behind it",
  "A note on shared dependencies when they moved",
  "MISSING lines for stages with no timing, and a record for the next week"
 ],
 "use_when": [
  "You tried a change, such as a faster review step, and want to know after a few weeks if it helped.",
  "Tasks keep finishing later than estimated and you cannot say which stage holds them up.",
  "A key dependency moved and several projects may slip together.",
  "You review work every week and want the trend, not a fresh guess."
 ],
 "skip_when": [
  "One project with no finished tasks yet. There is no baseline to compare. Use the Recurring work delay reviewer workflow for a first pass.",
  "Tasks with no dates. Add start and finish dates first. Without them the agent can only ask for them.",
  "Only shared dependencies or risks across projects changed. Use the Project risk portfolio planner on its own.",
  "You want a new finish date for one project. Use the Past-project timeline estimator."
 ],
 "output_sample": {
  "input": [
   "Dated task updates, with start, wait and finish dates",
   "Original estimates for each task",
   "Actual finish dates",
   "The fix you are testing and its start and review dates",
   "Your limit for a new pattern (optional)",
   "Last review's record (optional)"
  ],
  "prerequisites": [
   "An AI that can read pasted text or files, such as Claude, ChatGPT or Gemini",
   "The helper skills added, or the pack attached",
   "A baseline: at least one earlier set of finished tasks, or the first run builds one with you"
  ],
  "output": [
   {
    "name": "Trend by stage",
    "contains": "Waiting time and working time for each stage, against the baseline, with the number of tasks behind each figure."
   },
   {
    "name": "New patterns",
    "contains": "Any stage that moved past your limit, with the task IDs that show it. If none moved, it says so."
   },
   {
    "name": "Dependencies note",
    "contains": "Shared dependencies that moved and the projects they touch, from the Project risk and portfolio manager."
   },
   {
    "name": "Recommendation",
    "contains": "Keep, revise or stop for the fix you are testing, with the sample size and how much more evidence is needed."
   },
   {
    "name": "Improvement plan",
    "contains": "When a new pattern needs a change, one small test with an owner, a measured baseline, a review date and a success check."
   },
   {
    "name": "MISSING lines and CHECKS MISSED",
    "contains": "Stages with no timing, and every check that could not run, such as scripts that were read but not run."
   },
   {
    "name": "Record for the next review",
    "contains": "Task group, baseline definition, sample size, change tested, review date and evidence links."
   }
  ]
 },
 "output_shape": "DELAY REVIEW <date>, group <task group>\n<first baseline, or compared with <last review date>>\nFIX UNDER TEST: <change> | started <date> | review <date>\n\nTREND BY STAGE\n<stage> | waiting: baseline <x> now <y> | working: baseline <x> now <y> | sample <n tasks>\n\nNEW PATTERNS\n<stage> | what moved | rule used <yours, or ASSUMPTION> | evidence <task IDs>\nor: no new pattern this week\n\nDEPENDENCIES  <what moved and which projects it touches, or unchanged>\n\nRECOMMENDATION  <keep | revise | stop> | why | sample <n> | more evidence needed <what>\n\nMISSING  <stages or tasks with no timing>\nCHECKS MISSED  <one line each, or none>\nRECORD FOR NEXT REVIEW  <task group | baseline definition | sample size | change tested | review date | evidence links>",
 "how_to_use": [
  "Add the agent to Claude, ChatGPT or Gemini with its helpers, the Trace why work keeps missing deadlines workflow and the Project risk and portfolio manager. Or download the pack and attach it.",
  "Paste this week's task export (one row per task: ID, stage, start date, wait, finish date, estimate; dates as YYYY-MM-DD, with the timezone) and describe the fix you are testing. Say what a new pattern means to you, or let the agent propose a rule. From week two, paste last week's record.",
  "Remove staff names and other personal details from the export before you paste it. Task IDs and stage names are enough.",
  "Read the trend brief. Check the sample size before you believe any change. The first run only builds your baseline, so it gives no keep, revise or stop call yet.",
  "If the brief says the evidence is too thin, leave the fix as it is.",
  "Change your plan yourself if you agree. The agent changes nothing. After a \"stop\" call, you or the person who owns the fix decide what happens next.",
  "The Project risk and portfolio manager comes with Python scripts. In a chat-only tool the AI reads the numbers instead of running them, and says so under CHECKS MISSED."
 ],
 "checks": [
  "Comparable work uses the same definitions; a small sample does not prove a cause.",
  "Every factual claim, figure and date traces to a source or is clearly labeled as an assumption.",
  "The original source files stay intact, and revised files have distinct names or versions.",
  "Each required component check ran, or the run stopped and says which check could not pass.",
  "The summary names any work that could not be checked."
 ],
 "steps": [
  {
   "position": 1,
   "id": "trace-why-work-keeps-missing-deadlines",
   "name": "Recurring work delay reviewer",
   "summary": "Share repeated work steps, owners and timing records. Get likely delay points, a grounded timeline estimate and a small change to test.",
   "url": "https://useaiblocks.com/workflows/trace-why-work-keeps-missing-deadlines"
  },
  {
   "position": 2,
   "id": "project-risk-portfolio",
   "name": "Project risk portfolio planner",
   "summary": "Share project risks, scores, owners and resource needs. It compares exposure and workload, then drafts priorities and status for review.",
   "url": "https://useaiblocks.com/skills/project-risk-portfolio"
  }
 ],
 "next": [
  {
   "name": "Past-project timeline estimator",
   "url": "https://useaiblocks.com/prompts/outside-view-timeline-estimator",
   "why": "Decide what to do"
  },
  {
   "name": "Project risk portfolio planner",
   "url": "https://useaiblocks.com/skills/project-risk-portfolio",
   "why": "Project risk portfolio planner"
  }
 ],
 "source": null,
 "credits": [
  {
   "title": "Process bottleneck finder",
   "by": "Alireza Rezvani",
   "url": "https://github.com/alirezarezvani/claude-skills/tree/main/business-operations/skills/process-mapper",
   "used": "Component skill used as a separate, attributed dependency. This recipe adds original sequencing, handoff rules and acceptance checks. The component's own licence and source remain in its pack."
  },
  {
   "title": "Outside view timeline estimator",
   "by": "AI Blocks",
   "url": "https://useaiblocks.com/skills/outside-view-timeline-estimator",
   "used": "Component skill used as a separate, attributed dependency. This recipe adds original sequencing, handoff rules and acceptance checks. The component's own licence and source remain in its pack."
  },
  {
   "title": "Change rollout planner",
   "by": "Alireza Rezvani",
   "url": "https://github.com/alirezarezvani/claude-skills/tree/main/c-level-advisor/skills/change-management",
   "used": "Component skill used as a separate, attributed dependency. This recipe adds original sequencing, handoff rules and acceptance checks. The component's own licence and source remain in its pack."
  },
  {
   "title": "Project risk and portfolio manager",
   "by": "Alireza Rezvani",
   "url": "https://github.com/alirezarezvani/claude-skills/tree/main/project-management/skills/senior-pm",
   "used": "Component skill used as a separate, attributed dependency. This recipe adds original sequencing, handoff rules and acceptance checks. The component's own licence and source remain in its pack."
  }
 ],
 "files": [],
 "links": {
  "page": "https://useaiblocks.com/agents/weekly-project-delay-evidence-assistant",
  "markdown": "https://useaiblocks.com/agents/weekly-project-delay-evidence-assistant.md",
  "json": "https://useaiblocks.com/agents/weekly-project-delay-evidence-assistant.json",
  "instructions": "https://useaiblocks.com/skills/weekly-project-delay-evidence-assistant/SKILL.md",
  "api_item": "https://useaiblocks.com/api/v1/items/weekly-project-delay-evidence-assistant",
  "api_document": "https://useaiblocks.com/api/v1/documents/agent/weekly-project-delay-evidence-assistant",
  "mcp": "https://useaiblocks.com/mcp"
 }
}
