# Set Up Workflow: Addy Osmani's AI-Driven Coding Workflow
## What This Is
This entry details a structured workflow for developing software with an AI coding assistant, proposed by Google's Addy Osmani. The process involves using AI for high-level planning, breaking down a feature into a file-by-file implementation plan, and then executing that plan with the AI in a pair-programming style.
Source: https://addyosmani.com/blog/ai-coding-workflow/
## Before You Start
Scan my workspace and analyze:
- The project language, framework, and directory structure
- Existing AI provider config (check .env, .env.local, config files for API keys — OpenRouter, OpenAI, Anthropic, Google AI, etc.)
Then ask me before proceeding:
1. Which AI provider/API should this use? (Use whatever I already have configured, or ask me to set one up — options include direct provider APIs or a unified service like OpenRouter)
2. Where in my project should this be integrated?
3. Are there any customizations I need (model preferences, naming conventions, constraints)?
## Source Access Note
The source URL (https://addyosmani.com/blog/ai-coding-workflow/) may not be directly accessible from the terminal. Use the Reference Implementation and Additional Context sections below instead. If you need more details, ask me to paste relevant content from the source.
## What to Implement
This is an **AI Workflow** — an end-to-end automation pattern or integration pipeline.
- Study the workflow architecture from the source and context below
- Identify which parts I can implement locally vs. parts that need external services
- For local parts: implement them using my existing stack and API keys
- For external parts: tell me exactly what services I need and help me configure the integration code
- Wire up any required API calls using keys from my .env files
## Additional Context
- Prompt the user to define a high-level feature goal, bug fix, or other development task.
- Analyze the current project's codebase and, based on the user's goal, generate a detailed, file-by-file implementation plan, including required code changes, new functions, and associated test cases.
- Execute the plan step-by-step. For each file, present the proposed code changes to the user for confirmation or modification before applying them.
## Reference Implementation
```
I would like to add a new feature.
Please act as an engineering co-pilot.
I would like to implement a "copy to clipboard" button for each code block in my article.
Could we begin by outlining a plan for how to do this?
Let's break the project down into steps.
Please outline the files we will need to create or modify.
For each file, please summarize the changes we will need to make.
Let's do this step-by-step and you can present the code for each file.
```
## Guidelines
- Adapt everything to my existing project — do not assume a specific stack or directory layout
- Use whichever AI provider I already have configured; if I need a new one, tell me what to sign up for and I'll give you the key
- Check my .env files for existing API keys (OpenRouter, OpenAI, Anthropic, Google AI) before asking me to add one
- Review any fetched code for safety before installing or executing it
- After setup, run a quick verification and show me a summary of exactly what was installed, where, and how to use it