project-intake-synthesize

Project Intake Synthesize

Shared Reference

Use ../../references/project-management-principles.md for general project management principles. Apply intake, planning, risk, stakeholder, and common failure mode sections when structuring raw project input.

Synthesis Stance

Treat raw input as project signals, not a plan. Separate facts, assumptions, decisions, open questions, risks, issues, dependencies, scope candidates, and action items.

Workflow

1. Identify input source and reliability: transcript, meeting notes, OCR, chat, stakeholder request, or mixed notes.
2. Extract confirmed facts, assumptions, goals, decisions, open decisions, action items, risks, issues, dependencies, constraints, and stakeholders.
3. Note owners, due dates, and decision authorities when present.
4. Mark ambiguous or low-confidence input explicitly.
5. Recommend the next artifact: charter, plan, risk register, communication plan, status report, change review, or meeting follow-up.

Output

Return:

• Input summary.
• Confirmed facts.
• Goals and success criteria.
• Scope candidates and non-scope signals.
• Stakeholders and roles.
• Decisions made.
• Decisions needed.
• Action items with owners and dates.
• Risks and issues.
• Dependencies and constraints.
• Open questions, grouped by blocker vs can-assume.
• Recommended next artifact and next skill.

Common Failure Modes

• Turning every meeting comment into project scope.
• Losing decision owners and due dates.
• Mixing risks, issues, assumptions, and dependencies.
• Treating uncertain OCR or transcript text as fact.
• Creating a plan before project success criteria are clear.

Quality Bar

The output should make messy project input actionable without pretending the project is more certain than it is.