| name | source-command-start-project |
| description | Enforce the human-approved project-name gate before creating a new product, application, service, library, tool, repository, or implementing an idea. Use when starting new project work or when another workflow is about to generate a project. |
Start Project
Read AGENTS.md and docs/agent/START_PROJECT.md completely before taking any
project-creation action.
Required Process
- Inspect the request and any existing repository using read-only operations.
- Determine whether the human supplied an unambiguous project name or the
existing repository already establishes one.
- If no name is established, ask: What should the project be called?
- Immediately stop and wait. Do not write code, create files, initialize a
repository, generate an archive, or choose technical identifiers while the
name is unresolved.
- After the human supplies the name, record the approved display name and
derive technical identifiers according to
docs/agent/NAMING.md.
- Read the remaining guides selected by the task-routing table and continue
with the appropriate implementation or design workflow.
- When this repository is an external authority, report the exact revision
and routed guides actually read before implementation.
Output Contract
Before implementation, state the approved project name and the repository
revision used as engineering authority. If the name is missing, the only final
result of this workflow is the blocking name question; implementation has not
started.