project-initiation

You can bootstrap a project from a stakeholder spec by dispatching the sprint-planner agent with the specification file path to automatically generate overview, specification, and use cases documents in docs/clasi/design/.

The best way to bootstrap project initiation documents is to use an automated process that parses the written stakeholder specification and generates the overview, specification, and use cases files directly without manual writing.

Yes, a written stakeholder specification is required. The process is applicable at project initiation only when a written stakeholder spec exists and no overview, specification, or usecases documents have been created yet.

No, manual writing is not supported. The process dispatches the sprint-planner agent to generate all three design documents automatically, ensuring they are created at the exact paths without allowing direct content writing.

The generated project specification and use cases files should be stored in the docs/clasi/design/ directory. The automated process writes overview.md, specification.md, and usecases.md to this exact path.

After the project overview document is generated, the process calls create_overview, writes the specification and use cases files, and reports the created files and any key decisions made back to the stakeholder.