MAGA

MAGA

A great way for a non-coder to build an app

You make the product decisions. MAGA turns them into working, inspectable software.

Start building View on GitHub
  1. 01 You decide

    Define the outcome and what matters.

  2. 02 MAGA leads

    MAGA routes the work and sets the plan.

  3. 03 Codex builds

    Codex builds and checks the code.

  4. 04 You accept

    Inspect the result and accept it.

Product judgment stays with you. Why not be the boss?

Direct without restraint.
Accept with judgment.

Built for product thinkers

First-time builders

Bring the problem and the expectation.

Product designers

Bring the experience and the trade-offs.

Product leaders

Bring the goals and the decision boundaries.

One Project Lead. The whole build.

Describe what you want to build. MAGA works out what to learn or make next, then brings you a result to inspect.

  1. 01Agree on the outcome
  2. 02Decide what comes next
  3. 03Build a small working version
  4. 04Return to product judgment

Illustrative requests

One request. Two ways forward.

Choose a situation to compare possible pitfalls in an unstructured AI request with MAGA's intended workflow. These are examples, not measured results.

You say

I want to make a place for people who share a hobby to hang out, post things, and chat.

AI without an agreed process

You get an answer, but the product never takes shape.

  1. 01

    Start drawing screens from the first sentence.

  2. 02

    Split sign-up, posting, and the timeline into separate requests.

  3. 03

    Come back later and explain the background and decisions again.

Let MAGA lead

You get a usable first version and a clear next step.

  1. 01

    Define who it is for, what it solves, and where the first version stops.

  2. 02

    Connect one complete first journey.

  3. 03

    Build the smallest usable result.

  4. 04

    When you come back, pick up from the current progress.

What you get

  • Product boundary
  • Usable first version
  • Next step

Inside MAGA

One entry. Specialist work on demand.

You work in Codex with MAGA as your Project Lead. It turns your request into a concrete next step, gives Codex the project information and methods it needs, and returns the result for your acceptance.

  1. 01
    You speak product

    Users, problems, experience, constraints, and priorities.

  2. 02
    MAGA decides what comes next

    Clarify, research, prototype, implement, diagnose, or review.

  3. 03
    Codex builds a working version

    Only the context and skills this work actually needs.

  4. 04
    You inspect the result

    A working result, preview, test, or diagnosis.

  5. 05
    You accept

    Accept, adjust, or choose the next loop.

Product judgment continues the loop

Open another task when the work needs it.

With your project task-creation policy confirmed, MAGA can open named tasks within the approved work and worker limit. Otherwise, it asks before creating one. New scope and publishing still need your approval.

  • Research
  • Prototype
  • Delivery
  • Diagnosis
  • Review
  • Release readiness
Evidence

How MAGA divides the work.

A quick answer stays in Project Lead; a separate task is used when it helps finish the work.

  1. Keep it here

    A quick clarification stays with the Project Lead.

  2. Ask a read-only helper

    A short question can go to up to two temporary helpers. They inspect and report; they do not write or widen the work.

  3. Open a named work task

    A change, durable result, or independent acceptance gets its own approved task.

Project continuity

Resume with the decisions already made.

When project context has not been organized, you need to reconstruct it. MAGA prepares that context for the next task.

Without prepared context

Start by explaining the project again.

  1. 01

    Past decisions are mixed into a long conversation.

  2. 02

    You first decide what still applies before useful work can resume.

With MAGA

Continue from the last accepted state.

  1. 01

    Project Lead starts from the last accepted direction.

  2. 02

    It does not add permission or new work on its own; you choose whether to continue.

.ai-workflow Come back and pick up where you left off.

When you return, you can check the goal, progress, decisions, changes, and results before continuing. An optional Goal can keep an approved objective moving within its agreed budget; it grants no additional permission.

  • Goal
  • Progress
  • Who does what
  • Next steps
  • Choices
  • Checks
  • Small working steps
  • Authority never expands itself
  • Risky actions return to you
  • Codex owns code. You own direction.

Set up MAGA. Start the product.

Set up the plugin first, then describe your product in its Project Lead task.

  1. 01Setup MAGA
  2. 02Start the product

Setup MAGA

Open an empty project folder in Codex and paste this request.

Set up this project with the MAGA plugin from https://github.com/thevenomsnake/MAGA. Limit changes and downloads to this folder, the Codex plugin area, and any environment changes you explain first; do not sign in to GitHub, change account or repository settings, or push. Initialize it against `docs/public-surface-contract.md`, create or restore this project's Project Lead task, and report its exact name.

If you cannot find the named Project Lead task, ask Codex to run MAGA recovery and report its exact task name.

Read the beginner guide

Start the product

Open the named Project Lead task MAGA created or restored, then send a real product description. Do not start an arbitrary task.

I want to make a place for people who share a hobby to hang out, post things, and chat.