create-project

Create Project

Create a new project folder under docs/projects/ with a scaffolded proposal template.

When to Use

• User has a new idea they want to formalize into a proposal
• An investigation has concluded and the next step is a proposal
• The generate-proposal skill needs a project folder to write into
• Any work that warrants structured tracking (proposal → plan → sessions)

Workflow

Step 1: Determine Project Name

If a project name was provided as an argument, use it. Otherwise ask the user.

The name should be:

• kebab-case (lowercase, hyphens between words)
• Descriptive but concise (2-4 words)
• No date prefix — dates are tracked in document metadata and git history

Good: oauth-upgrade, milkdown-editor, search-enhancement

Bad: 2026-02-09-new-feature, project1, stuff

Step 2: Verify It Doesn't Already Exist

Check that docs/projects/<name>/ doesn't already exist. If it does, inform the user and ask how to proceed (use existing, choose different name, etc.).

Step 3: Create Project Folder Structure

Create the project folder and copy the proposal template:

docs/projects/<name>/
  proposal.md    — Scaffolded from TEMPLATES/PROPOSAL.template.md

Read docs/projects/TEMPLATES/PROPOSAL.template.md and use it as the starting point for proposal.md. Fill in what you can:

• Date: Today's date
• Status: Draft
• Project name in the title

Leave all other template sections as-is for the user to fill in.

Step 4: Link to Investigation (if applicable)

If the user mentions an investigation or provides one as context:

• Add it to the proposal's Related Documents section
• Use the path format: ../../investigations/<investigation-file>.md

Step 5: Confirm Creation

Tell the user:

• Project folder created at docs/projects/<name>/
• Proposal scaffolded with template
• Remind them of next steps:
  • Fill in the proposal (problem statement, proposed solution, scope)
  • When ready, use /project-docs:generate-dev-plan <name> to generate a plan

Important Constraints

• Don't create plan.md or sessions/ yet — Those come later when implementation begins
• Don't fill in proposal content beyond template defaults — The user or the generate-proposal skill handles that
• Check conventions at docs/projects/README.md if unsure about structure