Project Create

When to Use

When creating a new project.

Inputs

• Department name (for example, Forge, Product, Technology)
• Project name (filesystem-friendly Title_Case_With_Underscores, without the department prefix)
• Owner (email)
• Brief description
• Human gate preference (optional; default applies when unspecified)

Naming Contract

• Project folder: {Department}/Projects/{Project_Name}/

• Work-product files: {Project_Name}_Phase.md, {Project_Name}_Vision.md, etc.

• Spawn agent for the project: { ..., department: "{Department}", project: "{Project_Name}" }

• Convo.project: {Department}/{Project_Name}

• Convo name: {phaseValue} - {Department} {Project_Name}

Human Gates

Ask the user which human gates they want after project creation. Available gate keys:

Gate	After Phase	Description
G1	Vision_Eval	User reviews and approves the Vision before Research begins
G2	Research	User reviews Research decisions before Spec begins
G3	Spec_Eval	User reviews and approves the Spec before Plan begins
G4	Plan_Eval	User reviews and approves Plans before Execute begins
G5	Execute_Eval	User reviews execution results after each Execute_Eval cycle
G6	Verify	User reviews verification results before Extract begins
G7	Extract_Eval	User reviews extraction completeness before Complete

Default gates: Vision_Eval, Research, Spec_Eval, Plan_Eval, Verify.

Record selected gates in {Project_Name}_Phase.md frontmatter as a top-level human_gates list. Use the default list when the user does not specify.

Context Boundary

No other project documents exist at this phase.

Procedure

1. Confirm Department, Project Name, owner, brief description, and human gate preference. If the user supplies a name without a department, qualify it from context or ask for the department.
2. Conflict check — Before creating any files, check active and archived project folders across all departments for the same Project_Name. If any match is found, stop and report the conflict to the user with department and active/archived location. Do not proceed with creation.
3. Create directory {Department}/Projects/{Project_Name}/.
4. Create {Project_Name}_Phase.md from Forge/Forge_Project/Skills/Project_Create/templates/Phase_Template.md:
   • Replace {Project_Name} with the actual Project Name
   • Replace {owner} with the provided owner
   • Replace dates with today
   • Set Phase: Create_Started
   • Set human_gates to the selected gates, or the default gates if unspecified
5. Create README.md:
   • YAML frontmatter with required fields
   • H1 with project title
   • Brief description
6. Create AGENTS.md:
   • YAML frontmatter with required fields
   • H1 with project title
   • Project description
   • Sections: Related Skills, Documents, Knowledge
7. Set all document statuses to draft.
8. To add sidebar entries use spawnAgent with { botGroup: "forge", botHandle: "page-manager" }.
9. Build, commit, push.

Rules

• Do not create a project whose canonical/display identifier is ambiguous across departments.
• Folder and file names use Project_Name; user-facing references use {Department}/{Project_Name}.
• File names are prefixed with the project name except README.md and AGENTS.md.
• Both README.md and AGENTS.md use the required frontmatter convention.
• Minimum viable project: README.md, AGENTS.md, and {Project_Name}_Phase.md.
• Templates for later phases live at Forge/Forge_Project/Skills/Project_Create/templates/.
• Lazy creation — No placeholder report files are created at project creation time. Each phase creates its report file lazily when that phase runs.
• Use the todos tool group for project gate/blocker routing; do not create or update retired flat-file queues.

Available Templates

Template	Created by phase
Phase_Template.md	Create
Vision_Template.md	Vision
Vision_Eval_Template.md	Vision_Eval
Research_Template.md	Research
Spec_Template.md	Spec
Spec_Eval_Template.md	Spec_Eval
Plan_Template.md	Plan
Plan_Eval_Template.md	Plan_Eval
Execute_State_Template.md	Execute
Execute_Eval_Template.md	Execute_Eval
Verification_Template.md	Verify
Extract_Eval_Template.md	Extract_Eval
Audit_Template.md	Audit
Learnings_Template.md	Create
Changelog_Template.md	Create
Runs_Template.md	Verify or generated when run metadata is available