autonomous-setup

# Autonomous Setup ## Principle From here on, **no questions to the user**. Every open decision is made autonomously and logged in `project/DECISIONS.md` as an ADR. Only exceptions: the escalation criteria from the autonomy contract in `project/BRIEF.md`. **No `AskUserQuestion` tool** (enforced): a reversible open decision → decide and log an ADR; an escalation criterion hit → stop with a decision memo. Never an interactive prompt. ## Precondition `project/BRIEF.md` exists with status APPROVED. Otherwise abort and request `project-onboarding`. ## Phases ### 1. Research (timeboxed, parallel) First read the global knowledge base (resolve: `$SKILLS_KNOWLEDGE_DIR` if set, otherwise the path in `<skills-dir>/_shared/knowledge.path` — written by install.sh; if neither resolves → skip) — documented learnings from earlier projects replace research and prevent repeat mistakes. Then parallel read-only subagents in one invocation block, one per question: - **Alternatives:** What already exists? What does it not do well enough? (confirms/sharpens the core contract) - **Tech options:** 2–3 stack candidates fitting the must-have outcomes, target environment, and cost frame — with trade-offs, not with a winner - **Risks:** legal, technical, and cost traps of the domain Results go to `project/log/<date>-research-<topic>.md`. Research findings that suggest new features go into `project/IDEAS.md` — **never** directly into scope. ### 2. Decide Determine stack, architecture cut, and proj...