starting-new-project

name	starting-new-project
description	Plans and initializes a new software project through one-question-at-a-time discovery, current primary-source research, explicit recommendations and trade-offs, selected host and assistant profiles, an approved file manifest, and deterministic verification. Use for a new project, repository plan, scaffold, codebase initialization, or stack-selection request. Do not use to repair an established project, create unselected provider folders, or write files before the user approves both the plan and exact file list.
license	Apache-2.0
metadata	{"polymind.version":"2.0.0","polymind.tags":"project-planning,repository-scaffolding,portable,governance","polymind.risk":"writes-after-two-approvals"}

Starting a New Project

Guide a new project across two explicit boundaries: first research and recommendation, then optional scaffolding. Keep the user in control of both.

Phase A: discover, research, and recommend

1. Load discovery-questions.md. Ask exactly one targeted question per turn, reflect the answer briefly, and skip every dimension the user already answered. Use the fast exit when enough context is available.
2. Identify the required host, CI, and assistant profiles from user choices and repository evidence. Never select a provider merely because support might be useful later.
3. Research volatile stack, host, CI, and assistant facts using current primary sources. Record each material fact using : claim, source URL, , and applicability. Do not present a current-version claim from memory.