magnus919_agent-skills/technical-project-management/templates/project-brief.md

Project brief

Project: [name] · As of: [date] · State: [proposed / authorized / paused / closed] Authoritative records: [links and versions]

Outcome and authority

• Why this project exists: [problem/outcome]
• Success and acceptance evidence: [observable criteria, evaluator]
• Sponsor / funding authority: [accepted role/person]
• Delivery coordinator: [accepted owner and delegated decisions]
• Technical, product, and risk decisions: [respective authorities]
• Scope included / excluded: [boundaries]
• Approval record or missing authorization: [source; do not infer approval]

Constraints and assumptions

Constraint	Hard or negotiable?	Source	Consequence / decision owner
[date, budget, quality, capacity, obligation]	[classification]	[evidence]	[effect]

Capacity: [availability by capability; operations, leave and part-time constraints] Dependencies: [link to existing plan and critical handoffs] Uncertainty: [known gaps, validation owner, next learning decision]

Working agreement

Selected approach and rationale: [link to approach decision if needed] Source of truth: [where scope, milestones, decisions and evidence live] Review rhythm: [smallest useful cadence; audience; decision purpose] Escalation triggers and authority: [agreed tolerances, not invented percentages] Next milestone: [acceptance evidence, forecast, commitment if accepted] Next action or decision: [owner acceptance or explicit gap; due/review trigger]