AGI Super Team

Solo Founder workflow

Turn one founder brief into a reviewable delivery trail.

The starter kit assigns planning to CEO, implementation to PE, and content drafting to CCO. The founder still owns product judgment, credentials, releases, and every external action.

Last reviewed: 2026-07-21 ยท Kit: solo-founder

Prerequisites

  • A reviewed checkout, Git, Node.js, and an isolated destination directory.
  • A brief with one user, one problem, a narrow deliverable, acceptance checks, and a deadline.
  • A human owner who can reject work and personally approve deployment, publishing, credentials, and spending.

This kit is most useful for a bounded product slice or decision memo. It is a poor fit for an undefined company strategy, unattended operations, or work that requires licensed professional judgment.

Preview and apply

git clone --depth 1 --branch main https://github.com/aAAaqwq/AGI-Super-Team.git
cd AGI-Super-Team
./install.sh --source "$PWD" --destination /path/to/review-workspace solo-founder
./install.sh --source "$PWD" --destination /path/to/review-workspace --apply solo-founder

Run the first installer command and stop. Confirm that it proposes only workspace-ceo, workspace-pe, and workspace-cco, plus their required local files. Apply only when those paths are correct and do not overlap an existing workspace.

Use a four-stage operating loop

  1. BriefGive CEO the customer, constraint, non-goals, acceptance checks, evidence gaps, and decisions reserved for the founder.
  2. BuildGive PE one approved slice and require tests or a runnable check before implementation is described as complete.
  3. ReviewChallenge unsupported claims, scope drift, security risk, missing edge cases, and any external action that lacks authorization.
  4. ReleaseRecord the revision, checks, limitations, and rollback procedure. The founder performs or explicitly authorizes the release.

A realistic evaluation brief

Outcome: Add a read-only onboarding checklist to the demo site.
User: First-time maintainer evaluating the repository locally.
Constraints: Static HTML/CSS only; no analytics; no deployment.
Evidence: One focused test, mobile screenshot, keyboard pass, diff check.
Non-goals: Authentication, billing, production claims, external posts.
Approval gate: Founder reviews the diff and runs every command.

Ask CEO to convert this into a decision memo, PE to propose a test-first change, and CCO to draft a release note that includes limitations. Compare the three artifacts for consistent scope rather than asking all roles to solve the same task independently.

Evidence to keep

Retain the original brief, role assignments, final diff, test output, known limitations, and rollback instructions. If the team recommends a new dependency, record its license, maintenance state, and why the existing stack cannot meet the requirement. A polished narrative without a runnable artifact is not a completed outcome.

Stop condition

Stop when the acceptance checks pass and the known limitations are documented. Do not expand the task merely because unused roles or tools are available.

Limitations

The three roles are instruction bundles, not accountable executives or independent legal entities. Mentor names are creative framing and do not imply affiliation. Results vary with model, context, permissions, and the quality of the brief. The kit does not independently deploy software, validate market demand, or make a release safe.

Rollback and uninstall

Use the preview record to identify the three new workspace directories. Archive any evaluation artifacts you need, then remove only those directories if they were newly created by this run. Existing persona and skill files are protected rather than overwritten; if the installer reports a conflict, resolve it manually instead of deleting the destination wholesale.