Project Charter and Kickoff Pack
Project Charter and Kickoff Pack converts project purpose, outcome metric, scope, exclusions into project charter, RACI table, milestone outline, risk/dependency register, and kickoff agenda, with cited evidence, explicit rules, and unresolved exceptions. Use for project charter and kickoff pack, recurring review, and decision preparation.
Published Aug 21, 2026 · Updated Aug 26, 2026
Requirements
Map the process identifiers, source columns, and row citation convention. Add the governing policy, rubric, schema, or reference tables to the scope. Define thresholds, status values, units, and exception severity.
Skill document
The full SKILL.md your agent reads and follows.
Project Charter and Kickoff Pack
Purpose
Project Charter and Kickoff Pack turns the supplied records into project charter, RACI table, milestone outline, risk/dependency register, and kickoff agenda. It keeps source facts, derived values, recommendations, and limitations separate so each conclusion can be checked.
Scope
Cover project purpose, outcome metric, scope, exclusions, sponsor, manager, RACI role, milestone, dependency, risk, decision right. Preserve source identifiers, dates, units, and wording needed to trace every result.
Excluded for project initiation and kickoff governance: changing source records, taking external actions, making a human approval or employment decision, and asserting facts absent from the corpus.
Data basis
- Process documents and tables containing project purpose, outcome metric, scope, exclusions, sponsor, manager, RACI role, milestone, dependency, risk, decision right.
- Company policy, rubric, schema, templates, and reference tables in scope.
- Run input for period, audience, entity, or threshold when it changes this run.
Result
Produce project charter, RACI table, milestone outline, risk/dependency register, and kickoff agenda. Each material row and conclusion cites a document, section, page, row, field, or run input.
Quality criteria
- Every scope, milestones, roles, and dependency coverage record is included or has an exclusion reason.
- Calculations state fields, units, denominator, and rule.
- Missing, contradictory, stale, and ambiguous values stay labelled rather than guessed.
- Facts, interpretations, and proposed next actions use separate fields.
- Supplied terminology, thresholds, and status values are used consistently.
- The final limitations section states what the corpus could not establish.
Instructions
Separate committed scope from ideas and assumptions. Every milestone has outcome, owner, date or duration, and dependency status. Distinguish named sponsor approval from a proposed decision. Preserve original values beside normalized values, cite every material finding, and use “not assessed” when required evidence or a rule is absent. When sources disagree, show both citations and explain the conflict. Keep row-level evidence in the supporting sheet and summarize only supported conclusions in the document.
Adapt before use
- Map the charter and RACI field mapping fields and row citation convention.
- Add the governing policy, rubric, schema, or reference tables to the scope.
- Define thresholds, status values, units, and exception severity.
Related skills
- Change request assessment
Assesses a project change request against the approved baseline and produces a traceable impact analysis for scope, schedule, cost, quality, risk, resources, and dependencies. Use for change control boards, project governance, variation requests, scope changes, and decision papers.
- Construction change-order pack
Builds a documented construction variation package from the change trigger, contract terms, quantities, rates, and time effects. Use for change orders, variation claims, owner instructions, design changes, and subcontractor pricing review.
- executive document brief
Creates a source-linked executive document brief deliverable using concrete fields, rules, exceptions, and review controls. Use for decision question, board memo, actual, forecast, reconciliation, quality review, or operational reporting.
- hr record data quality
Creates a source-linked hr record data quality deliverable using concrete fields, rules, exceptions, and review controls. Use for employee_id, hire_date, manager_id, duplicate, reconciliation, quality review, or operational reporting.