objective: instantaneous project management by synchronizing ticket queues against agentic file search of consulting documentation and contract dates.

when documentation is missing, requirements are decomposed from code, user tickets, and available manuals.

why this workflow exists

project drift frequently comes from evidence mismatch: ticket claims, contract obligations, and real implementation state diverge.

this loop closes that gap by requiring every active ticket to map to source evidence and date-bound obligations.

core inputs

• ticket feed - juror/jira/linear task stream with status, owner, and due date
• contract surface - msa, sow, amendment, renewal, sla, and milestone dates
• delivery evidence - repository code, changelogs, runbooks, support manuals
• user signal - incidents, support tickets, and acceptance feedback

execution loop (daily)

1. ingest open tickets
2. run agentic file search for each ticket:
   - matching requirement text
   - matching contract clause or milestone
   - matching code path or manual section
3. score evidence confidence (high/medium/low)
4. detect date conflicts:
   - ticket due > contract milestone
   - missing owner for date-critical work
   - unresolved dependency blocking contracted delivery
5. produce sync board:
   - now: must ship in current window
   - next: scheduled and contract-aligned
   - risk: misaligned, under-specified, or date-broken
6. open remediation tickets automatically for all risk items

no-documentation fallback

if formal documentation is absent, the workflow does not stop.

requirements are reconstructed from implementation and user intent:

1. extract feature surfaces from code:
   rg -n "TODO|FIXME|feature|flag|endpoint|workflow" .
2. parse user tickets for expected outcomes and acceptance hints
3. mine manuals/help docs for promised behavior
4. infer provisional requirements:
   - actor
   - action
   - expected result
   - failure boundary
5. mark each inferred requirement as provisional until reviewed
6. attach inferred requirement ids back to tickets

contract date reconciliation rules

• rule 1 - contract milestone outranks ticket due date
• rule 2 - unlinked ticket cannot be marked delivery-ready
• rule 3 - low-confidence evidence requires owner sign-off
• rule 4 - no owner means no schedule commitment

minimal data contract

{
  "ticket_id": "J-142",
  "requirement_ref": "REQ-09",
  "contract_ref": "SOW-2.4",
  "contract_date": "2026-04-15",
  "evidence_paths": ["src/billing/renewal.ts", "manuals/billing.md"],
  "confidence": "medium",
  "status": "risk",
  "owner": "pm@company"
}

output artifacts

• sync report - ticket-to-contract alignment matrix
• risk queue - date violations and missing evidence
• reconstruction log - inferred requirements created from code/tickets/manuals
• next-action brief - top 5 actions that reduce contractual risk fastest

fast start prompt

Synchronize open tickets against repository evidence and contract dates.
For each ticket:
- map requirement_ref and contract_ref
- extract evidence paths
- classify confidence
- flag date conflicts
If documentation is missing, infer provisional requirements from code, user tickets, and manuals.
Return now/next/risk board plus remediation tickets.

bottom line

this workflow treats project management as a synchronization problem rather than a dashboard problem.

evidence-linked tickets plus contract-date reconciliation support predictable delivery.