# Project kickoff workflow

Use this pattern when starting a substantial task. A strong kickoff reduces rework by making the objective, authority, boundaries, and definition of done explicit.

## Prompt template

> **Outcome:** [what must exist at the end]  
> **Context:** [why it matters and who will use it]  
> **Inputs:** [files, links, examples, source of truth]  
> **Scope:** [included and excluded work]  
> **Constraints:** [time, style, compatibility, permissions]  
> **Acceptance criteria:** [how success will be checked]  
> **Process:** inspect first, propose a plan, execute in milestones, report blockers, validate, and summarize.

Use only the fields that clarify the work.

## Step 1: Inspect the current state

Ask Neo to review the relevant inputs before proposing changes. The inspection should identify missing access, conflicting sources, outdated material, and assumptions that affect the plan.

## Step 2: Align on the plan

A useful plan names deliverables, milestones, dependencies, review points, and validation. Check that it does not silently expand scope or rely on unavailable capabilities.

## Step 3: Set authority boundaries

State which actions Neo may take independently and which require approval. External publication, sending messages, deleting files, spending money, changing permissions, and production deployment should be explicit.

## Step 4: Execute in milestones

Break the project into reviewable outputs. For example:

1. inventory and gap analysis;
2. proposed structure;
3. first complete draft;
4. factual and editorial review;
5. final validation and delivery.

## Step 5: Close the project

Ask for:

- deliverables and locations;
- a summary of changes;
- validation performed and results;
- unresolved questions and assumptions;
- recommended next steps.

## Example kickoff

> Build an internal onboarding guide from the files in this workspace. The HR policy is authoritative; older slide decks are reference only. Preserve existing terminology, do not publish or delete anything, and flag policy conflicts. First return an inventory and outline. The final guide must include role-based checklists, working internal links, and an owner-review list.

This format gives Neo a clear basis for deciding when to ask, act, or stop.