generate-charter

generate-charter

Triggers

Russian: «сформируй устав», «подготовь устав проекта», «создай charter», «нужен устав проекта» English: "generate charter", "create project charter", "build charter", "draft project charter"

Language Detection

Determine the language of the user's request:

• If the request is in Russian → use templates with -ru suffix
• Otherwise → use templates with -en suffix

All output (headings, labels, comments, instructions) must match the detected language.

---

1. Inputs

Data	Required	Source	Notes
Project data	yes	chat or knowledge	Brief, free-form description, answers to questions, or unstructured notes. Agent extracts and structures independently
Stakeholder answers	no	chat or knowledge	Completed questionnaire or free-form answers. If absent — agent extracts from general project description
Project constraints	no	chat or knowledge	Budget, timeline, technical, organizational. If not provided separately — agent extracts from general description
Team composition	no	chat or knowledge	If provided — fill Section 5. If absent — keep only Sponsor and PM rows
Market context	no	chat or knowledge	Used to refine goal statement and risks

If required data is missing — request it (system-prompt-draft.md §3 p.2):

To generate a charter, I need project information in any format:
a ready brief, answers to questions, a free-form description, or a set of key points.
Minimum to start: project goal and at least one of: timeline, budget, scope.
Available data: [list what is present].
Missing for the charter: [specify].

---

2. Execution Steps

1. Check inputs. Verify that project data (in any form) is present. If missing → request using the template in §1. Do NOT generate a placeholder charter, template, or example — respond ONLY with the data request. If present → step 2.
2. Structure inputs. If data is free-form — extract and categorize: goal, scope, timeline, budget, team, constraints, risks. Note ambiguities and gaps; clarify with the user selectively. Do not ask for everything at once — request only what is strictly required for the charter. When computing dates from relative timelines ("12 weeks from April 7") — calculate exactly: start + N×7 days = end. Do not round.
3. Check for contradictions. If one parameter (budget, timeline, scope) appears with conflicting values across sources — do NOT choose a value independently. List the contradictions and ask the user which data is current. Exception: if the user explicitly clarifies outdated brief data in chat — treat the clarification as authoritative.
4. Read the template project-charter.md from project knowledge.
5. Extract data from sources. For each placeholder (Section 4) — find the value in inputs. Priority: explicit user data > brief > agent assumption.
6. Fill template sections following the rules in Section 3.
7. Validate the result using the checklist (Section 5).
8. Show the result in chat. Format (system-prompt-draft.md §3 p.4):
   • What was done: "Charter generated for project [name] based on: [list sources]."
   • Assumptions: list all (if any).
   • What is required: "Approve, provide comments, or reject."
   • Do not include system file paths. Use filename only: "Charter saved as project-charter.md".
9. Wait for user response (system-prompt-draft.md §3 p.5).
   • Approval → produce the final document.
   • Comments → revise and show updated version. After the 3rd iteration — ask: "Continue revising or finalize the current version?" (this is not a hard limit — user may request more iterations).
10. After approval:
    • Offer the user text to paste into log.md and project-state.md (system-prompt-draft.md §11).
    • Notify: "Charter approved. Next available task: generate-risk-register (initial risk register). Start?" (system-prompt-draft.md §7).