Using Sepo

Use this section when you want to understand what Sepo can do after it is installed.

The docs use three terms consistently:

• Workflows are GitHub workflow files in .github/workflows/. They define triggers, jobs, permissions, and dispatch boundaries. See Supported workflows.
• Agent actions are route-level behaviors such as answer, implement, fix-pr, and review. They are selected by mention, label, approval, or workflow dispatch, and are implemented through workflow wiring plus prompts. See Agent actions.
• Internal actions are shared composite GitHub Actions in .github/actions/. They scaffold the runtime, resolve GitHub auth, and run agent tasks for workflows. See Internal actions.

Documentation model

These pages are hand-written for now. The desired long-term pattern is to keep small agent-doc metadata blocks near the YAML workflows, composite actions, and prompt files, then render this section from that metadata.

Until that renderer exists:

• Supported workflows is the canonical place for .github/workflows/* trigger and route details.
• Agent actions is the canonical place for route behavior, prompt consumption, session policy, and generated-doc metadata conventions.
• Internal actions is the canonical place for .github/actions/* details.

Avoid duplicating action details in setup or architecture pages. Those pages should explain user-facing behavior and link here for workflow and action details.