Prompt file imported from parkerduff/devin-cli (.windsurf/workflows/create-session.md). Copyright stays with the author.

Create Devin Session Workflow

Name: create-session
Author: parkerduff

This workflow helps you create a well-structured Devin session using the CLI with proper context.

Prerequisites

Ensure you have authenticated with devin-cli auth
Have the repository URL or path ready
Know the specific task you want Devin to accomplish

Steps

Review Prompt Structure Guide I'll reference devin-session-guide.md for the official prompt structure and examples to ensure proper formatting.
Gather Context Following the guide structure, I'll collect:
- Overview: The task/goal you want Devin to accomplish
- Repository: Current repo will be auto-detected if applicable, or specify /
- Procedure details: Specific files, PRs, issues, or technical constraints
- Specifications: Success criteria and expected outcomes
- Advice: Preferred approaches, tools, or methodologies
- Forbidden Actions: What Devin should avoid
Auto-detect Repository (if needed) // turbo If working with the current repository, I'll run:
```
git remote get-url origin
```
To extract the owner/repository name automatically.
Create Structured Prompt Using the guide examples as reference, I'll construct a complete prompt with all sections:
- Overview: Clear goal statement
- What's Needed From User: "No user intervention required - complete end-to-end"
- Procedure: Step-by-step instructions with repository context
- Specifications: Success criteria and postconditions
- Advice and Pointers: Technical guidance based on task type
- Forbidden Actions: Security and quality constraints
Verify Prompt I'll show you the complete constructed prompt and ask for your approval before proceeding.
Execute Session Creation Once approved, I'll run the CLI command:
```
devin-cli create --prompt "[CONSTRUCTED_PROMPT]" --output table
```
With appropriate metadata like tags and title based on the task.

Example Command

devin-cli create \
  --prompt "$(cat your-prompt.txt)" \
  --tags "repository,development" \
  --title "Repository Analysis and Enhancement" \
  --idempotent

Repository Detection Process

When you indicate the session should run on the current repository, I will:

Check if we're in a git repository
Extract the remote origin URL
Parse the owner/repository name from the URL
Include this information in the session prompt as "Repository: owner/repo"

Tips

Devin can identify GitHub repositories using the owner/repository format
Keep the repository reference at the beginning of your procedure
Be specific about file paths and directory structures
Include any environment setup requirements
Specify the expected deliverables clearly
Test your prompt structure with the examples in the guide first

# Create Devin Session Workflow This workflow helps you create a well-structured Devin session using the CLI with proper context. ## Prerequisites 1. Ensure you have authenticated with `devin-cli auth` 2. Have the repository URL or path ready 3. Know the specific task you want Devin to accomplish ## Steps 1. **Review Prompt Structure Guide** I'll reference `devin-session-guide.md` for the official prompt structure and examples to ensure proper formatting. 2. **Gather Context** Following the guide structure, I'll collect: - **Overview**: The task/goal you want Devin to accomplish - **Repository**: Current repo will be auto-detected if applicable, or specify <owner>/<repo-name> - **Procedure details**: Specific files, PRs, issues, or technical constraints - **Specifications**: Success criteria and expected outcomes - **Advice**: Preferred approaches, tools, or methodologies - **Forbidden Actions**: What Devin should avoid 3. **Auto-detect Repository (if needed)** // turbo If working with the current repository, I'll run: ```bash git remote get-url origin ``` To extract the owner/repository name automatically. 4. **Create Structured Prompt** Using the guide examples as reference, I'll construct a complete prompt with all sections: - **Overview**: Clear goal statement - **What's Needed From User**: "No user intervention required - complete end-to-end" - **Procedure**: Step-by-step instructions with repository context - **Specifications**: Success criteria and postconditions - **Advice and Pointers**: Technical guidance based on task type - **Forbidden Actions**: Security and quality constraints 5. **Verify Prompt** I'll show you the complete constructed prompt and ask for your approval before proceeding. 6. **Execute Session Creation** Once approved, I'll run the CLI command: ```bash devin-cli create --prompt "[CONSTRUCTED_PROMPT]" --output table ``` With appropriate metadata like tags and title based on the task. ## Example Command ```bash devin-cli create \ --prompt "$(cat your-prompt.txt)" \ --tags "repository,development" \ --title "Repository Analysis and Enhancement" \ --idempotent ``` ## Repository Detection Process When you indicate the session should run on the current repository, I will: 1. Check if we're in a git repository 2. Extract the remote origin URL 3. Parse the owner/repository name from the URL 4. Include this information in the session prompt as "Repository: owner/repo" ## Tips - Devin can identify GitHub repositories using the owner/repository format - Keep the repository reference at the beginning of your procedure - Be specific about file paths and directory structures - Include any environment setup requirements - Specify the expected deliverables clearly - Test your prompt structure with the examples in the guide first

{ "prompt": "# Create Devin Session Workflow\n\nThis workflow helps you create a well-structured Devin session using the CLI with proper context.\n\n## Prerequisites\n1. Ensure you have authenticated with `devin-cli auth`\n2. Have the repository URL or path ready\n3. Know the specific task you want Devin to accomplish\n\n## Steps\n\n1. **Review Prompt Structure Guide**\n I'll reference `devin-session-guide.md` for the official prompt structure and examples to ensure proper formatting.\n\n2. **Gather Context**\n Following the guide structure, I'll collect:\n - **Overview**: The task/goal you want Devin to accomplish\n - **Repository**: Current repo will be auto-detected if applicable, or specify <owner>/<repo-name>\n - **Procedure details**: Specific files, PRs, issues, or technical constraints\n - **Specifications**: Success criteria and expected outcomes\n - **Advice**: Preferred approaches, tools, or methodologies\n - **Forbidden Actions**: What Devin should avoid\n\n3. **Auto-detect Repository (if needed)**\n // turbo\n If working with the current repository, I'll run:\n ```bash\n git remote get-url origin\n ```\n To extract the owner/repository name automatically.\n\n4. **Create Structured Prompt**\n Using the guide examples as reference, I'll construct a complete prompt with all sections:\n - **Overview**: Clear goal statement\n - **What's Needed From User**: \"No user intervention required - complete end-to-end\"\n - **Procedure**: Step-by-step instructions with repository context\n - **Specifications**: Success criteria and postconditions\n - **Advice and Pointers**: Technical guidance based on task type\n - **Forbidden Actions**: Security and quality constraints\n\n5. **Verify Prompt**\n I'll show you the complete constructed prompt and ask for your approval before proceeding.\n\n6. **Execute Session Creation**\n Once approved, I'll run the CLI command:\n ```bash\n devin-cli create --prompt \"[CONSTRUCTED_PROMPT]\" --output table\n ```\n \n With appropriate metadata like tags and title based on the task.\n\n## Example Command\n```bash\ndevin-cli create \\\n --prompt \"$(cat your-prompt.txt)\" \\\n --tags \"repository,development\" \\\n --title \"Repository Analysis and Enhancement\" \\\n --idempotent\n```\n\n## Repository Detection Process\nWhen you indicate the session should run on the current repository, I will:\n1. Check if we're in a git repository\n2. Extract the remote origin URL\n3. Parse the owner/repository name from the URL\n4. Include this information in the session prompt as \"Repository: owner/repo\"\n\n## Tips\n- Devin can identify GitHub repositories using the owner/repository format\n- Keep the repository reference at the beginning of your procedure\n- Be specific about file paths and directory structures\n- Include any environment setup requirements\n- Specify the expected deliverables clearly\n- Test your prompt structure with the examples in the guide first", "variables": [], "notes": "Create a Devin session with proper context and repository information", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/parkerduff/devin-cli", "path": ".windsurf/workflows/create-session.md", "ref": "4c02b03a80201c663b6b949886745c95f9f83552", "url": "https://github.com/parkerduff/devin-cli/blob/4c02b03a80201c663b6b949886745c95f9f83552/.windsurf/workflows/create-session.md", "key": "parkerduff/devin-cli/.windsurf/workflows/create-session.md" } } }

create-session

About

Create Devin Session Workflow

Prerequisites

Steps

Example Command

Repository Detection Process

Tips

Use it

Manifest

Reviews