project-setuplisted

# Project Setup Set up a software product from evidence, explicit decisions, and human approval gates. Support two modes: - `greenfield`: create a product and engineering foundation before implementation. - `existing`: scan and reconcile an existing repository without overwriting its conventions. Do not apply this skill to non-software projects. ## Start with classification Ask only questions that cannot be answered from local evidence. Establish: 1. Mode: `greenfield` or `existing`. 2. Product type: web app, SaaS, desktop, mobile, backend/API, developer tool, CLI, SDK/library, data/AI, browser extension, or hybrid. 3. Lifecycle: prototype, MVP, growth, mature, or legacy modernization. 4. Surfaces: UI clients, API, workers, integrations, deployment targets, and supported platforms. 5. Source of truth: local request, Notion, issue tracker, existing documents, or a combination. 6. Artifact language. 7. Delivery model: single-agent, dual-agent, or multi-agent. Read [references/classification-and-discovery.md](references/classification-and-discovery.md) when requirements are incomplete or product type is ambiguous. Persist the result in `docs/PROJECT_PROFILE.md`. Treat this classification as provisional until the user approves it. ## Choose the workflow ### Greenfield 1. Run focused discovery and identify assumptions. 2. Research unstable or high-cost decisions using primary sources. 3. Draft the project profile and Product Plan. 4. Add a conditional Design Spec only w