002-setup-project

Project scaffold generation creates a ready-to-run project structure from your requirements, producing ARCHITECTURE.md, tasks.json, CONTEXT.md, and ENV-SETUP.md. It applies to medium-to-large scope projects requiring disciplined task breakdown, traceability, and reproducible setup with verifiable success criteria.

Yes, you can generate architecture and task documentation by transforming a PRD or chat-derived requirements into structured files. This automated workflow produces ARCHITECTURE.md and tasks.json, enforcing verifiable success criteria and creating rich subagent prompts for project execution.

The best way to structure tasks for medium-to-large projects is using a reproducible setup pipeline that generates a tasks.json file with traceable breakdown. This enforces verifiable success criteria and produces rich subagent prompts to guide execution from architecture to implementation.

Yes, project scaffolding supports reproducible environment setup by generating ENV-SETUP.md alongside architecture and context documentation. It includes rich subagent briefing prompts to ensure agents have the necessary structured context for executing defined project tasks.

You need to generate a complete project scaffold with traceability when moving from ideation to action on medium-to-large scope projects. It is required when your project demands disciplined task breakdown, verifiable success criteria, and reproducible setup documentation to ensure structured execution.

A limitation of automating workflow from requirements to scaffold is that it targets medium-to-large scope projects needing disciplined task breakdown, meaning it may be excessive for simple tasks. It requires initial requirements to be defined prior to generating the architecture and task structure.