<!--
IndexTitle: AI Workflow
IndexDescription: Website page draft explaining practical AI-assisted work.
IndexType: Content
IndexStatus: Draft
LastEdited: 2026-05-30
-->

# AI Workflow

Give AI clear context and small reviewable tasks.

Artificial intelligence (AI) is most useful here when it works from clear context and produces small, reviewable changes.

Get Established On The Web treats AI as a practical collaborator. An AI agent is an assistant working from the repository files and instructions. The repository gives the agent planning files, prompts, and source content so it can help without guessing the whole project from scratch.

That is why the prepared foundation matters. Get Established Workspace gives AI an organized place to read the user's goals, audience, offer direction, positioning notes, page drafts, open questions, and next steps before it suggests changes.

In public language, this is an AI-ready workspace: a folder of organized files for building an online presence. In technical workflow language, the Get Established Repository is the source of truth that keeps those files, instructions, and changes reviewable.

## How To Work With AI

1. Give the agent the repository location and branch (the version of the repository being worked on).
2. Ask it to read `AGENTS.md` and the relevant planning files.
3. Give one focused task with clear boundaries.
4. Ask for plain Markdown output when planning or content is still forming.
5. Review the changed-file view before accepting the work.

If the agent asks for permission, pause long enough to check what access it needs and whether the request matches the task. A simple read of trusted repository files is different from a request to install software, change system settings, or push changes.

## Good AI Tasks

- Draft a first-pass page from existing planning notes.
- Improve clarity without changing the project direction.
- Create a short prompt for a repeated workflow.
- Summarize decisions after a planning pass.
- Build a small checklist from existing docs.
- Clarify a positioning direction after basic identity, audience, and offer discovery.

## Tasks To Avoid Early

- Building a full website before the page content exists.
- Adding frameworks before the project has chosen a publishing path.
- Replacing human-authored planning files without review.
- Generating large boilerplate that hides the important decisions.

## What The Repository Demonstrates

The repository itself shows how AI-assisted work can stay structured. Each planning file, prompt, and content draft gives future agents a clearer starting point and gives humans a source of truth they can review.

The same distinction matters for future outputs. The Get Established On The Web public website explains the method, the Get Established Workspace / Repository holds the organized source files, and a future user one-page business website is a separate output created only from approved user inputs.

## Useful Starting Points

- Use the reusable prompts to give agents focused tasks.
- Use the planning documents to keep work aligned with the project direction.
- Use the open questions file for non-blocking decisions that need human review later.
- Keep work local first, then commit and sync at useful milestones.

## Link Intent

- Point discovery work to `../../../Docs/Prompts/UserDiscoveryPrompt.md`.
- Point content review work to `../../../Docs/Prompts/ContentReviewPrompt.md`.
- Point ongoing agent work to `../../../Docs/Prompts/AgentSelfDirectedLoop.md`.
- Point permissions and sandbox context to `AgentPermissions.md`.
- Point workflow context to `GitHubWorkflow.md`.

## Draft Status

This page can later include example prompts and before-after task examples from repository history. Do not invent examples; use real repository milestones when they exist.
