AI agent team guide
AI Project Manager: Run Weekly Status and Risk Reviews
A source-linked project status and dependency register with explicit next decisions

An AI project manager should make the next project decision clearer, not make a stale plan look current. Use it to compare source records, explain milestone changes, surface dependency risks and prepare a short status brief. Keep accountable people in charge of assignments, scope and dates.
This playbook uses Finta's Project Manager with Capacity Planner, Meeting Follow-Through and Decision Journal Keeper. The intended return is a source-linked status register and a decision list. It is not a claim that Finta automatically synchronizes every project-management tool or takes over a human project manager's accountability.
Start with one project and one review cutoff
Bring the approved outcome, current milestone, authorized task list, latest decision notes and prior status report. Include dates and owners where they are actually recorded. Pasted or uploaded material is a valid starting point. Call it a supplied snapshot, not a live integration.
State the cutoff time for the review. A document updated last Thursday and a task board exported Monday may tell different stories. Preserve the source dates instead of silently choosing whichever makes the schedule appear healthier.
Build your four-agent project review team
| Agent template | Specific job | Reviewable output | Team |
|---|---|---|---|
Project ManagerLead agent | Compare current evidence with the prior plan and identify decisions due. | Status register, changed milestones, risks and unresolved questions. | Add to team |
Capacity PlannerSupporting agent | Review actual commitments and competing priorities. | Capacity assumptions and tradeoff options without invented availability. | Add to team |
Meeting Follow-ThroughSupporting agent | Reconcile explicit promises with existing tasks and newer updates. | Open commitments, proposed next actions and evidence of completion. | Add to team |
Decision Journal KeeperSupporting agent | Record the choices accepted at the review and when to revisit them. | A dated decision record with owner, rationale, assumptions and a review trigger. | Add to team |
Set up the team in your Finta account
- Import the templates individually. Open each linked marketplace profile and select Import agent. Review the template and complete its setup in your account.
- Brief each coworker. Run its Getting Started skill with the same objective and the specific source material that role needs. Supply approved documents or exports when needed.
- Keep the handoff explicit. Review one return before giving the accepted artifact, sources and open questions to the next agent. Importing templates does not by itself run this entire sequence.
- Choose what becomes recurring. Complete one useful manual pass first. Review any proposed routine and enable it only when its scope and inputs are right.
Build a register that another person can audit
Keep three different objects separate. A status describes the best-supported current state. A risk is a possible future problem with an observable trigger. A blocker is already preventing a named step. “At risk” is not a useful substitute for explaining what decision is needed.
Project review register
Project / accountable owner:
Outcome and acceptance criteria:
Review cutoff / source snapshot dates:
Deliverable:
Current state: done / in progress / blocked / not reviewed
Evidence link or note reference:
Last confirmed update:
Accepted owner, or proposed owner to confirm:
Next checkpoint and source for its date:
Dependency or decision needed:
Risk trigger / impact / proposed response:
Change from prior review:
Human decision / decision owner / review date:
Action actually completed and receipt, or nothing completed:
“Done” needs completion evidence matched to the acceptance criteria. A missing update remains not reviewed. It is not automatically progress, failure or permission to move somebody's deadline.
Run the review in five passes
- Confirm the scope. Have Project Manager restate the outcome, cutoff and source coverage. Resolve a different definition of done before discussing the schedule.
- Reconcile changes. Compare each active deliverable with the last accepted register. Require a source for a changed state, owner or checkpoint. Preserve disagreements for review.
- Review dependencies and capacity. Name the prerequisite, the affected work and the person who can decide. Ask Capacity Planner for options using actual commitments, not an invented percentage of availability.
- Close or reopen commitments. Ask Meeting Follow-Through to compare promises with authorized tasks and later evidence. Deduplicate proposed actions. Completion is a receipt, not an agent's optimistic summary.
- Publish a human-reviewed status brief. Lead with the decision due, then the changed facts, current blockers and next checkpoint. Ask Decision Journal Keeper to draft a dated record of the choices the owner actually accepts, with the reasons and review triggers. The owner approves distribution and any supported record changes separately.
Fictional example: a launch date with an unresolved dependency
This scenario is an original teaching example. A small team plans a customer onboarding pilot. The task export marks the checklist complete, but the latest review note says that the invitation copy is awaiting approval. No customer invitations have been sent.
| Evidence | Correct state | Next decision |
|---|---|---|
| The checklist document contains the agreed steps. | Checklist draft complete, approval state not yet confirmed. | Who confirms the customer-facing version? |
| The review note names an unresolved copy change. | Invitation preparation blocked on approval. | Accept the change or move the proposed pilot checkpoint. |
| A team member is assigned to two same-day launches. | Potential capacity conflict; availability not confirmed. | Ask the accountable owner to choose priority or another accepted owner. |
The brief should say, “Approval is needed before invitations can be prepared for release.” It should not say, “The pilot is launched,” or silently move the customer date. If the next review still lacks the approval, the register retains that unresolved dependency.
Copy the weekly status and risk prompt
Prepare a weekly status and risk review for [one project and desired outcome].
Use [authorized task snapshot], [approved brief], [reviewed meeting notes] and [prior register]. State each source date and the review cutoff.
For every deliverable return the evidenced state, source, last confirmed update, accepted owner, checkpoint and change from the prior review.
Separate risks, current blockers, assumptions and missing updates. Do not infer completion from silence.
Ask the capacity pass to compare actual commitments and the follow-through pass to reconcile accepted promises with existing tasks.
Ask Decision Journal Keeper to draft the record of decisions the accountable owner confirms, preserving the original reasons and review triggers.
Return an exceptions-first brief, a dependency register, the next human decisions and an accepted-decision record.
Do not reassign work, change dates, send updates, promise availability or enable routines.
Where the AI coworker fits
The Project Manager package is designed for a kickoff brief, status review and dependency/risk review. Finta Tasks and supplied documents provide context where authorized. The weekly routine is optional and stays off until enabled. If the input is a static export, establish who refreshes it; a schedule cannot make stale evidence current.
For the general planning foundations, start with the project management guide. For the writing principles behind the report, use the async status-update guide. Use this workflow when you need to reconcile inputs and run the review, rather than learn the general definition of project management.
Judge the review by decisions, not report length
Check whether the owner can name what changed, which dependency matters next and what decision is due. Track unresolved blockers and completed accepted actions separately. A cleaner register is an operating improvement, not proof of faster delivery or a completed milestone.
PMI's AI-in-project-management resources provide broader professional context. This Finta playbook does not replace professional judgment, certify a project or claim that an AI coworker holds a human qualification.