create-project-management-artifactlisted

# Create an impactful project-management artifact Make it easy for a reader to understand the project's position and act on it. Impact means clearer understanding and decisions, not visual decoration or an unsupported promise of better project performance. Preserve the user's requested audience, artifact type, reporting convention, scope, and output format. For an unspecified shareable visual artifact, create static HTML. Do not replace an explicitly requested email, spreadsheet, document, or slide deck with HTML. Use suitable available format tools or explain a capability limitation. Work locally without requiring an account or connection. ## Choose the artifact by its job Identify the audience, their decision or action, the relevant time horizon, and authorized source material. Ask only for missing information that materially changes the result; an explicitly requested draft can proceed with visible unknowns. Do not turn intake into a long form. Read [artifact patterns](references/artifact-patterns.md) and choose the smallest pattern that serves the requested job: | Reader's question | Useful artifact | | --- | --- | | What are we doing, why, and what is outside scope? | Project brief | | What changed, what is next, and where is help needed? | Weekly/project update | | What must happen before what, and what dates are credible? | Milestone and dependency plan | | What threatens delivery or is already blocking it? | Risk, issue, and dependency brief | | What was decided