Quick User Manual

Badge: GTT-Method V2.1 · Practical guide

Core Statement

You define the intent. GTT-Method protects the intent. AI accelerates implementation.

The Golden Rule

AI may analyze, propose and execute; authority over governed decisions remains human. GTT-Method may intentionally introduce friction into rapid development to guide users toward compliance with the project's standards, rules and governance requirements.

1. The Complete Flow

GTT-Method makes governance part of the normal workflow, so users do not have to manually manage every governance artifact.

YOU define → delegate → review → accept/reject → AGENT analyzes → implements what is allowed → proposes when needed → GTT-Method records decisions → updates context → protects what was approved

Routine implementation: delegate. Governed decision change: Change Request → Proposal → human review → acceptance → ADR/context.

2. First Use: Bootstrap

Prepare the design

Keep an initial design document in the project root with the vision, objective, main functionality, architecture, technology stack, constraints and known decisions. It does not need to be perfect, but it must clearly represent what you want to build.

Incorporate GTT-Method

Give the ADE: https://github.com/GTT-Community/gtt-bootstrap

Ask: ``` Clone/incorporate GTT-Method Bootstrap into this project. Inspect the project and use my initial design document as the source for performing the GTT-Method Bootstrap. Do not invent decisions; if information is missing, ask me. ```

3. The Two Confirmations

A. Does this design represent what I want to build?

If not, correct the design and review it again. If yes, explicitly confirm it.

B. Did GTT-Method correctly represent my solution?

Review the vision, architecture, stack, principles, constraints and glossary. Correct anything that is wrong before freezing.

These are different decisions and both matter.

4. Review the Workspace and Freeze

After Bootstrap you will find files such as AGENTS.md, CHANGE-REQUEST.md, SOURCE-BRIEF.* and a gtt-method/ directory containing context, ADRs, proposals and scripts.

Quick architecture map: `gtt-method/context/stack.md`

Freeze: `gtt-method/scripts/gtt-method-freeze.sh`

5. Normal Development: Delegate

Implement this functionality according to the governed GTT-Method
context. Do not change architectural decisions.

A Change Request is not needed for a bug fix, unit test, already-defined endpoint, refactor without a governed decision change or logging improvement.

6. When to Use CHANGE-REQUEST.md

Use it when changing a governed decision: database, cloud platform, framework, architectural pattern, integration, constraint, security or deployment decision, or when introducing a major component.

7. What Not to Do

• Do not directly edit frozen governed context.
• Do not create copies to bypass protection.
• Do not disable the guardrails.
• Do not create a Proposal for every line of code.
• Do not accept a Proposal without reading it.

Quick Checklist

• I prepared or defined the initial design.
• I ran Bootstrap and confirmed the design.
• I reviewed and confirmed the generated context.
• I ran Freeze and checked the protection.
• I delegate routine work without changing decisions.
• I use CHANGE-REQUEST.md for governed changes.
• I review and decide every Proposal.
• I keep ADRs, context and the architecture map consistent.

Quick Reference

Remember: define the intent, confirm the context, make the decisions, delegate implementation and review the result. Human First. AI Accelerated.