Human-led feature workflow

Plan the outcome
before the code.

The Brief records the outcome, tasks.md records the implementation, and you decide when the feature is done.

Install ggez See the workflow

curl -fsSL https://raw.githubusercontent.com/varelycode/ggez/main/scripts/install.sh | sh

Python 3.9+ · macOS or Linux

ggez status

Feature friendly-cli

Current task TASK-3

Stage Implementation

Completed 2/4 (50%)

ONE TASK
AT A TIME

HUMANS
APPROVE

BriefTasksBuildReview

The whole workflow

From Brief
to acceptance.

Choose a stage to see what ggez records and where human approval is required.

Approval required Step 1 of 4

Name the slice and the outcome.

Create a blank Brief. You fill Slice and Outcome, add direct context, and approve the document before tasks begin.

ggez plan "friendly cli"

Editable source

Two files hold the feature.

brief.md records the outcome; tasks.md records the implementation. People and coding agents can read both.

brief.md

The outcome

01 Slice + Outcome
02 Direct context
03 Acceptance checks

Approved before tasks.

tasks.md

The implementation

□ TASK-1 · Pending
✓ TASK-2 · Pass
□ TASK-3 · Pending

Checked only when it passes.

Built-in boundaries

Approval has clear boundaries.

ggez separates Brief approval, task results, and final acceptance.

You write the outcome.

ggez creates a blank Brief. Slice and Outcome stay yours.

Context comes first.

Add one to five direct sources with a reason for each before tasks.

Pass has one meaning.

A task is checked exactly when its fixed Result is Pass.

You accept the outcome.

The feature is complete after every task passes and you check acceptance.

Live project history

What changed.

New entries appear here the next time the page is opened or refreshed.

Read CHANGELOG.md on GitHub

CHANGELOG.md Loading from GitHub…

Install

Install ggez.

Preview what init will add, apply it, then create a blank Brief.

Browse source on GitHub

install.sh