SR Method EN
Create a project from scratch
SR path from an uncoded idea to a Codex-ready project.
Create a project from scratch
This path starts from an idea that has not been coded yet. The priority is not to generate code quickly, but to produce a base that Codex can use.
What the user does
- Create a ChatGPT or Claude project dedicated to the product.
- Describe the intent without freezing the solution too early.
- Ask the AI to challenge the idea, competitors, open-source building blocks and risks.
- Validate V0, exclusions and critical business rules.
- Produce a Codex Project Pack.
Recommended steps
- Create a dedicated discovery space.
- Describe product intent.
- Ask for analysis of blind spots, risks, competitors, alternatives and open-source building blocks.
- Formalize Product Discovery.
- Identify domain expertise areas.
- Generate the Codex Project Pack.
- Create the GitHub repository.
- Install the SR Method from the official repository.
- Ask Codex to restate its understanding and propose first lots.
- Validate the first lot before any code.
Prompt for additional documents
Which documents should we produce before handing this project to Codex?
I want a folder usable by a Codex developer: brief, PRD, functional specs, technical architecture, data model, API, UX, security, test strategy, roadmap, initial lots, bootstrap prompt, domain map and domain skills plan.
Also propose additional documents required by the domain: regulation, security, RAG, runtime agents, integrations, existing migration, mobile/offline or specialized UX.Condition before code
Codex should start development only when:
- V0 scope is clear;
- exclusions are explicit;
- critical business rules are documented;
- first lots are validated;
- the user has validated the lot to execute.