Files
magnus919_agent-skills/technical-project-management/evals/samples/with-skill-expert.md
T
Magnus HedemarkandGitHub 22d141de75 feat: add research-grounded technical project management skill (#468)
* feat: add research-grounded technical project management skill

* test: retain isolated project coordination regression evidence
2026-09-04 23:56:40 -04:00

2.5 KiB

Decision for tomorrow: authorize a recovery investigation and choose which constraint can move. Day 20 is unsupported by the current integration logic.

The vendor forecast moved six working days, from needed-by day 12 to day 18. Ten working days after receipt puts integrated acceptance at day 28, eight days beyond the day-20 baseline, assuming the interface is usable immediately and those ten days include acceptance. Day 18 is unconfirmed, so day 28 is conditional, not a commitment.

There is also a pre-existing two-day inconsistency: day 12 + 10 = day 22. Meeting day 20 with unchanged integration requires usable receipt by day 10. Reconcile the baseline logic before attributing the full eight-day variance to this vendor change.

Option Consequence / evidence required
Retain full scope; move acceptance Plan around conditional day 28 or later. Confirm vendor handoff, integration capacity, and acceptance duration before committing. Sponsor approval required to change baseline.
Protect day 20 through recovery Requires receipt by day 10, or eight days of validated overlap/duration reduction against day-18 receipt. Technical lead and vendor must demonstrate feasibility; added people alone do not prove compression.
Deliver a reduced or staged outcome by day 20 Identify an independently acceptable slice and obtain acceptance-owner approval. Mocks may enable early work but cannot silently replace integrated acceptance. Date feasibility remains unproven.

Recommendation: retain day 20 as the historical baseline, report the day-28 conditional forecast now, and use full-scope date movement as the planning scenario while testing a genuinely acceptable staged outcome. Do not promise recovery tomorrow without evidence.

Before the review: TPM obtains the vendor's written forecast/commitment distinction, deliverable version, handoff evidence, and next confirmation time; integration lead reconciles the ten-day sequence with the baseline and identifies credible overlap. These are proposed assignments to confirm with the owners. If confirmation is absent tomorrow, explicitly report the missing commitment and request sponsor escalation to the vendor's accountable owner.

Sponsor ask: state whether full scope or day 20 takes priority, authorize the bounded recovery assessment, and name who can approve a scope/date change. Agree the next decision checkpoint tomorrow, tied to vendor confirmation and the integration lead's revised sequence; do not overwrite the baseline while these decisions are pending.