What problem does it solve? Setting up a repository for autonomous, TDD-based development requires creating consistent configuration files for testing, linting, architecture, domain vocabulary, and issue tracking. Doing this manually is error-prone and often leaves gaps that break downstream automation. ## Core Features & Use Cases - Auto-Detection of Tech Stack: Scans composer.json, package.json, Cargo.toml, go.mod, and other manifest files to detect language, framework, test runner, and linter. - Interactive Configuration: Asks structured questions about test commands, parallel execution, architectural patterns, coverage requirements, and issue tracker choice (GitHub via gh CLI or local Markdown). - Config File Generation: Creates .farseer/ config files (testing.md, code-standards.md, architecture.md, domain.md, issue-tracker.md, issue-labels.md) plus an Agent Skills block in CLAUDE.md or AGENTS.md. - Use Case: After cloning a Laravel project, run the setup once to detect Pest and Pint, record an 80% coverage requirement, choose GitHub Issues as the tracker, and scaffold all configuration so planning and orchestration skills work immediately. ## Quick Start Ask the assistant to set up this repository for Farseer autonomous development and answer the interactive configuration questions.