All-In Project Lite

Problem

Mid-stage projects often develop state drift: docs, vault, source, branches, and tests no longer match. Agents can also mistake a passing diagnostic for approval to merge, push, or delete. All-In-project-skill-lite is a routing entry that first selects the right phase skill from current project evidence instead of executing a long-running task. It separates empty-repo initialization, legacy onboarding, requirement evaluation, bug fixing, code review, branch merging, multi-person coordination, and Goal监工 paths, reducing context bloat and unauthorized actions.

• Project state drift: docs, vault, source, branches, and tests become inconsistent
• Agent overreach: diagnostics or review passing are mistaken for merge, push, or delete approval
• Context bloat: long-running tasks, repo-wide scans, and raw logs are pulled back into the main Agent

How It Works

The main Agent stays single-threaded and minimal-context by default, indexes evidence first, then explains status, risk, and the recommended route. Clear states map to sub skills: empty directory to 项目初始化, existing code without scaffolding to 遗留项目接入, known defects to Bug修复, explicit change sets to 代码审查, and precise source/target branches to 分支合并. Multi-person mode is not auto-enabled by multiple branches alone; ownership, progress, dependencies, and owners must be confirmed.

Goal监工 is an explicit bounded executor: at startup it confirms actions, objects, scope, and prohibitions once, then continues inside that contract. New branches, files, versions, or external systems trigger a full stop and escalation. Sub-Agents are limited to a three-layer concurrent structure, preventing long logs and repo-wide scans from being pushed back into the main context.

Boundaries

It covers single-repo project operations and controlled collaboration, not CI/CD, production deployment, multi-repo coordination, or unattended product decisions. It also does not treat review passing or local merge success as approval for push, branch deletion, or release. Best for engineers who need auditable authorization, explicit phase gates, and bounded context.