magnus919_agent-skills/technical-project-management/evals/samples/with-skill-team.md

Use one shared page and your existing work board. You do not need a dedicated PM to make decisions and unfinished work visible.

Start with this copyable page. Treat the launch date as a sales target, not an agreed delivery promise until scope and available time support it.

Migration agreement	Current entry
Outcome	Customer migration; specify the customer, data/services moving, and why
Included / excluded	Not yet accepted; list both before promising a date
Successful completion	Draft: agreed data reconciles, required customer workflows pass, and a named customer representative accepts the result
Launch target	Sales wish; record date, source, and consequence of missing it
Delivery forecast	Unknown until scope, dependencies, and part-time availability are checked
Scope/date authority	Name the person who can approve tradeoffs; currently unconfirmed
Acceptance authority	Name the customer representative who can accept the result; currently unconfirmed
Coordinator	One engineer volunteers to keep this page current; this does not give them scope or architecture authority
Next milestone	Agreed migration scope, acceptance checks, and a capacity-based first forecast

For the first pass, each engineer adds their sustainable hours or available work blocks for the next two weeks, absences, and other obligations. Four part-time engineers are not four full-time people. Identify customer access, data samples, and any specialist or vendor dependency that could hold up the work.

Keep the board to Ready → Doing → Waiting → Done. Each item needs an agreed owner, a small concrete result, and a check that proves it is done. Start with one active item per available engineer; show blockers and their next action in Waiting. Do not fill everyone’s calendar with speculative work before the migration scope is accepted.

Add this decision log underneath the agreement:

Date	Question	Decision or pending choice	Who can decide	Reason / evidence	Revisit trigger
Today	What is the migration scope?	Pending: draft included/excluded list	Scope authority—confirm name	Current scope is unaccepted	Before date commitment
Today	Is sales' launch date feasible?	Unknown	Scope/date authority—confirm name	Scope and availability missing	First forecast prepared

Record a decision when it happens, with a link to the relevant discussion. A proposed choice remains pending until the right person agrees. Changes to accepted scope should show their date/capacity impact before being accepted.

Use one weekly asynchronous update: finished and checked; next result; blocker or decision needed. Only schedule a short discussion when a written decision is stuck; no daily status meeting is necessary. The coordinator gathers unresolved choices for the person who can decide them.

For your first week, propose volunteers to draft the scope and acceptance checks, gather availability, and confirm the customer's acceptance contact. Get their agreement to those responsibilities. By the end of that week, review the shared page asynchronously with the scope/date authority: approve the scope, revise it, or explicitly leave the date uncommitted. Then plan one small migration rehearsal with clear checks, recovery steps, and authorization before touching customer production data.

This setup is enough once everyone can find the accepted scope, next milestone, current blockers, and decisions. Revisit it if work repeatedly waits on the same person or the weekly update fails to surface a material change.