## Context Doc-intelligence identified converging signals from Teams and GitHub around first-run friction: - Teams users repeatedly confused about `--yolo` necessity ("Why is Squad asking me to edit every file?") - Issue #374: parent git repo initialization trap - PR #375: proposes `--yolo` in README Quick Start (awaiting review) - Multiple "Taking a long time" reports resolved by `--yolo` ## Suggested Scope 1. Merge PR #375 (`--yolo` in README Quick Start) 2. Update Squad init docs to warn about parent git repos (cross-ref #374) 3. Create a "Before You Start" checklist page: `--yolo`, init environment checks, recovery steps 4. Update CONTRIBUTING.md if needed for squad init setup pattern ## Source Doc-intelligence digest signal #4 (2026-03-13 scan). High confidence — multiple independent sources converge on the same friction points. --- *Created by Squad activity-aggregator from doc-intelligence signals*
Activity
docs: add session model, known limitations, repo anatomy, and FAQ pages
craigb commentedon Mar 14, 2026
📋 Triage note: Suggested labels:
squad,type:docs,priority:p1This consolidates multiple first-run friction signals (
--yoloconfusion, parent git repo traps, PR #375). High-confidence issue from doc-intelligence — multiple independent sources converge on the same UX friction points.Coordinates with PR #375 (awaiting review) and issue #374.
🤖 Triaged by Ralph (Work Monitor)
docs: add session model, known limitations, repo anatomy, and FAQ pages
test: human journey E2E tests - 7 real user scenarios, 39 assertions (g…