Project Creation Wizard

The wizard is the fastest way to build context that is actually usable for Guidance and AI.

Start modes before the wizard

When you create a project, TensorPM shows How would you like to start? with these modes:

• Empty Wizard

• From Prompt

• From Document

• Skip Wizard

Operational details:

• From Prompt uses your short project description to bootstrap context.

• From Document extracts context from one or more selected files.

• Skip Wizard creates an empty project and lets you fill context later.

The 11 wizard steps

1) Project description

Capture what the project is, why it exists, and core boundaries.

2) Project goal

Define the primary outcome in an objective way.

3) Project scope

State what is in scope and explicitly out of scope.

4) Success criteria

Add measurable criteria. These later feed coverage checks.

5) Timeframe

Set start/end dates or an initial delivery window.

6) Budget

Set budget constraints (financial and/or effort).

7) Main requirements

Build structured requirements with priority.

8) Technologies & methods

Document stack, methods, and implementation approach.

9) Milestones

Define milestone checkpoints with dates and descriptions.

10) Dependencies

Describe external constraints and delivery dependencies.

11) Risks

Track risks with impact and mitigation intent.

Structured table fields in wizard steps

Table-driven steps use specific columns:

• Main requirements: Requirement, Description, Priority

• Technologies/methods: Technology/Method, Description, Category

• Milestones: Milestone, Date, Description

• Risks: Risk, Impact, Mitigation

What "good input" looks like

• Write constraints, not marketing copy.

• Prefer measurable criteria over vague goals.

• Record unknowns explicitly.

• Keep scope boundaries sharp.

• Add risks early, not only when problems appear.

After finishing the wizard

Recommended sequence:

• Open Context and review each tab for completeness.

• Create initial Action Items linked to real requirements/milestones.

• Run Guidance Context and then Strategic.

• Use Quick Actions to fill execution gaps.

Common mistakes

• skipping scope exclusions

• missing dependencies

• writing requirements without priority

• storing risks in chat only instead of context tables

Next steps

• Understand connected views: Navigation & Views

• Execute work: Action Items

• Prioritize with context quality gates: Guidance