Plan G: AI Coding Workflow (Requirements to Delivery)
Clarify requirements → technical plan → scaffold → incremental coding → test & debug → review & commit
- Time
- 1-4 hours / feature
- Cost
- Medium
- Difficulty
- Advanced
Best for
Steps
Clarify requirements
10-20 minChatGPT / Claude + you
Turn a vague requirement into clear acceptance criteria: goal, inputs/outputs, edge cases, and what NOT to build. Let the model ask the gaps you missed — this decides how much you rework.
💡Write 'when X happens, then Y' acceptance cases so the AI and you are on the same page.
Technical plan
10-20 minClaude / ChatGPT
Decide stack and architecture (language, framework, data structures, interfaces) first, with the model comparing options and trade-offs. Settle the plan before writing code.
💡Ask for the simplest runnable MVP first, then expand — steadier than designing everything up front.
Scaffold and skeleton
10-30 minCursor / Claude Code
Initialize the project, directory structure, dependencies and base config until the code runs. Use templates or agent scaffolding to cut manual labor.
💡git init early and commit in small steps so anything can roll back.
Incremental coding
1-2 hoursCursor / Claude Code / Copilot
Implement in small steps — finish one feature/module and verify it before moving on. Let coding agents (Claude Code / Cursor Composer) edit and run autonomously, so problems trace to a specific step.
💡Commit every verifiable unit; generating one giant feature at once is how big hidden bugs happen.
Test and debug
30-60 minTest framework + AI
Write unit tests for critical logic, manually verify edge and error paths, and feed error logs to the model for diagnosis. Let AI write tests, run them and fix regressions.
💡Describe exactly how to reproduce before asking the model — hit rate jumps; test empty, huge and invalid inputs separately.
Review and commit
20-30 minCode Review / review agent
Self-review the diff, run an AI security/correctness/performance pass, fix findings, and write a clear PR description (what changed, why, how tested).
💡Include test results and reproduction steps in the PR; reviews pass faster and rollbacks are easy.
Tools involved
Pitfalls to avoid
Coding before clarifying requirements
Generating one giant feature at once
Shipping without running tests
Stale libraries / guessed APIs
Related Workflows
Plan AX: Context Engineering — Feed the Right Context, Get It Right the First Time
Document project memory → spec first → give enough relevant files → iterative feedback → verify & commit
- Time:
- 1-3 hours / task
- Cost:
- Low
- Difficulty:
- Advanced
Plan AY: From Vibe Prototype to Viable Product — Pre-Launch Polish Checklist
Lock down requirements → make it testable → error handling → performance → maintainability → documentation
- Time:
- 0.5-2 days
- Cost:
- Medium
- Difficulty:
- Advanced
Plan AZ: AI Coding Security & Testing Checkup — Mandatory Before Shipping
Input validation → secret management → dependency audit → automated tests → review checklist
- Time:
- 1-2 hours / delivery
- Cost:
- Low
- Difficulty:
- Advanced