forge

You can automate GitHub issue management by orchestrating build loops that route to plan, build, or sync phases based on your open issues. This enforces deterministic control flow and handles API budget checks automatically.

A deterministic orchestration session routes tasks to sub-skills based on GitHub state, ensuring consistent execution. It validates project markers, manages the build loop, and writes status to a temporary directory to track progress.

To recover an automation build loop after a crash or rate limit, the orchestration session gracefully resumes by verifying authentication, checking API budgets, and reading previous status from temporary state files.

Yes, you can use GitHub state to trigger planning when no issues exist. The orchestration logic automatically routes to the plan phase if issues are absent, or to the build phase when issues are open and ready.

Yes, you need GitHub authentication to orchestrate build sessions. The orchestration performs authentication verifications and API budget checks at the start of the session to ensure secure and uninterrupted automation.